pravic / winapi-kmd-rs Goto Github PK

I've changed my default build target to x86_64-sys-windows-msvc and opted to use the x86_64 nightly rust using rustup, however the target appears to be attempting to link with 32 bit msvcrt:
note: msvcrt.lib(chkstk.obj) : fatal error LNK1112: module machine type 'X86' conflicts with target machine type 'x64'
I can see in my output that it's using the correct version of rustc as well as the x64 msvc toolchain, it's just attempting to link to the wrong version of msvcrt.lib.
Any ideas? Thanks for your help.

I can't compile the project with latest nightly toolchain. And I'm newbie to rust, have no idea how to get this to work.
error like:
E:\prj\rust\kmd-env-rs\km\examples\01.minimal>cargo build --release
Compiling core v0.0.0 (file:///E:/prj/rust/kmd-env-rs/libcore)
error[E0557]: feature has been removed
--> E:\prj\rust\kmd-env-rs\libcore\lib.rs:77:12
|
77 | #![feature(reflect)]
| ^^^^^^^

rust-lang/rust#33553

This eliminates .def file usage, enables LTO. But requires 2016-05-21 or later nightly rustc.

Update: it is available since Rust 1.11.

The link to Four-F is somewhat dangerous because its hosting JavaScript injection code that is attempting to exploit people's browsers. Just an FYI that you might want to add a note of caution.

Is ReactOS with gcc supported?

Forgive me if the solution is obvious, I'm still very new to Rust and Cargo, but for some reason when following the steps to build the minimal example in the readme, Cargo is not picking up the targets defined in the .cargo directory pulled in from kmd-env-rs.

Any thoughts on resolving this? Thanks!

I see in Cargo.toml that license is set to "MIT" but I don't see a LICENSE file anywhere in the repo or headers on any of the source/example files. Would it be possible to get these added?

If a function returns any value for Status other than the variants you have defined, it will result in undefined behavior. This is one of the big reasons I moved away from Rust enums for winapi.

Are they implemented yet?

I've noticed a few places with hard-coded paths to the DDK path and sub-directories (such as the target json files). The readme could use a few notes on which files need to be changed to set that path to your local installation path.

Please let us know when can we have an ARM64 version for Windows on ARM OS. We can help you test We have Windows on Rasberry Pi setup. Please pursue it we at Windows on Rasberry Pi community will be glad to extend support in testing your drivers and tools for ARM64.