Thanks Corey, I will have a look into this ;)
Alfredo On Sunday, 28 December 2014, Corey Richardson <co...@octayn.net> wrote: > You need at least a 32-bit stdlib, but you can build with `cargo build --target i686-unknown-linux-gnu` and it will "Just Work" assuming you have the proper libs in $PREFIX/lib/rustlib/i686-unknown-linux-gnu. http://doc.rust-lang.org/src/rustc_back/target/mod.rs.html#330 has a list of the built-in targets, and http://doc.rust-lang.org/rustc_back/target/index.html has docs on how to create your own. > > On Sun, Dec 28, 2014 at 2:11 PM, Alfredo Di Napoli < alfredo.dinap...@gmail.com> wrote: >> >> Hello Rustacean, >> >> I’ll go straight to the point: I’m building a small FFI library which needs to be called >> from a C++ x86 project. I cannot change the arch of the latter (it’s Doom3, and relies on x86 arch entirely). >> Thus linker reject my Rust library as “file was built for x86_64 which is not the architecture being linked (i386)”. >> >> Thus my question: It’s possible (without rebuilding the toolchain) to instruct cargo to generate a x86 dylib? >> Something like (fantasy syntax): >> >> cargo build —arch-type=x86 >> >> Thanks in advance! >> Alfredo >> _______________________________________________ >> Rust-dev mailing list >> Rust-dev@mozilla.org >> https://mail.mozilla.org/listinfo/rust-dev >> > > > > -- > http://octayn.net/
_______________________________________________ Rust-dev mailing list Rust-dev@mozilla.org https://mail.mozilla.org/listinfo/rust-dev
