autotools-rs
autotools-rs copied to clipboard
lu-zero
build.rs helper to configure and compile autotools and configure/make projects
Right now autotools-rs builds into `OUT_DIR` but also configures the installation prefix as `OUT_DIR`. That means the build files get mixed in with the installation artifacts. Not generally a huge...
I am replacing this code in my `build.rs` (which works fine): ```rust let out_dir = PathBuf::from(env::var("OUT_DIR").unwrap()); Command::new("./configure") .current_dir("ta-lib") .arg(format!("--prefix={}", out_dir.display())) .output() .expect("Failed to execute TA C library configure script"); Command::new("make")...
Made an attempt to document the changes I pushed and you merged recently. Also to give some context about the difference between Rust's (and this package's) interpretation of "host/target" and...
The `Config::build()` method automatically emits the cargo directive `cargo:root=`. Please provide a method to disable this behavior, e.g., `Config::emit_cargo_root(bool)`. The default `Config` instance would emit `cargo:root=` to make this change...
Hey, I tried running this on Windows (disclaimer I'm not a Windows guy). Installed `mingw-gcc, mingw-make, mingw-autotools` but `autoreconf` is not an executable on Windows (it is an perl file)...
I use simple `build.rs`: ```Rust extern crate autotools; fn main() { let dst = autotools::build("3rdparty/rsync-3.1.3"); println!( "rustc-env=RSYNC_BIN={}", dst.join("bin").join("rsync").display() ); } ``` and after adding such `build.rs` build becomes really slow,...
Write some test to make sure everything works: - [ ] Test options - [ ] Test autoreconf - [ ] Test env overrides
