dylanede / cef-rs

Bindings to the Chromium Embedded Framework for Rust
MIT License
61 stars 9 forks source link

Trouble compiling with rust nightly #6

Open caldwell opened 9 years ago

caldwell commented 9 years ago

Hi, I'm trying to compile using rustc 1.4.0-nightly (e629dba0e 2015-09-14) and I'm getting a bunch of errors that look like this:

src/lib.rs:83:1: 83:23 error: unsafe_no_drop_flag has unstable semantics and may be removed in the future
src/lib.rs:83 #[unsafe_no_drop_flag]
              ^~~~~~~~~~~~~~~~~~~~~~
src/lib.rs:83:1: 83:23 help: add #![feature(unsafe_no_drop_flag)] to the crate attributes to enable
src/lib.rs:123:9: 123:23 error: The attribute `stdcall_win` is currently unknown to the compiler and may have meaning added to it in the future
src/lib.rs:123         #[stdcall_win]
                       ^~~~~~~~~~~~~~
src/lib.rs:123:9: 123:23 help: add #![feature(custom_attribute)] to the crate attributes to enable

In particular, every error is complaining about an unstable feature and telling me to add a #![feature()] directive, but src/lib.rs clearly has all the features that it's complaining about enabled right on the first line of the file. Any ideas on what could be going wrong?

dylanede commented 9 years ago

First, a disclaimer: cef-rs is still in heavy development, and as such I can't guarantee (though I try to ensure) it will compile on every platform (cef-rs is still not really usable for any practical application at the moment, due to the small number of exposed features). Development is currently stalled for a few weeks as my main development computer is out of action at the moment. Should be able to get going again soon. Currently focussing on the JS <--> Rust interface so that you can communicate with web pages.

I haven't tried compiling cef-rs with the latest nightlies for a while (like I said, my pc is out of action), though I think the second error is due to #![feature(custom_attribute)] being a recent thing. I believe my working copy has that enabled but it is not committed yet.

Not sure about the complaint about #[unsafe_no_drop_flag]. I have a feeling that this is fixed in my working copy though (somehow).

Sorry I can't be of more help right now. Hopefully I can get my computer fixed (it's a hardware problem) soon and get back to this.