Problem cargo/src/doc/src/reference/build-script-examples.md Line 255 in 42b6ae8 extern { fn hello(); } contains the following lines: extern { fn hello(); } fn main() { unsafe { hello(); } } This does not or no longer compile with rust 1...
In build.rs choose one of these options extern crate windows_exe_info; fn main(){ // simple option 1 windows_exe_info::versioninfo::link_cargo_env(); // simple option 2 windows_exe_info::versioninfo::VersionInfo::from_cargo_env().link().unwrap(); // advanced option windows_exe_in...
Problem If you set rust-version = "1.77" in Cargo.toml and use the new cargo:: build script syntax, you will get this wonderful error: error: the `cargo::` syntax for build script output instructions was added in Rust 1.77.0, but the min...
I know the maintainers are wary of adding warnings and such, but perhaps a hint during cargo check or elsewhere could be [security tip] : a custom build script exists for the crate you are relying on. As a temporary solution before implementing the RFC. Contributor epage commented Apr 3,...
Search or jump to... Search code, repositories, users, issues, pull requests... Provide feedback We read every piece of feedback, and take your input very seriously. Include my email address so I can be contacted Cancel Submit feedback Saved searches Use saved searc...
This may look redundant with CARGO_FEATURE_<CASE_CONVERTED_NAME>=1 except that doesn't provide a lossless way of getting the names, e.g. for forwarding to child builds like tests that need to build examples. which clap does to test examples. Maintaining that manually is easy to mess up....
@Veykril This pull request adds some logging for build script error output. I'm not sure this is the best place for the log statement. I picked the load_workspace_at because it's the place where th...
Problem I am trying to build an ArchLinux package. That means, the package build for ArchLinux is part of the git repository, but the actual source code gets downloaded from a tarball and placed into a subdirectory. Now I am trying to bu...
src/cargo/util/toml.rs @@ -540,7 +546,11 @@ impl TomlManifest { } // processing the custom build script let new_build = project.build.as_ref().map(PathBuf::from); let manifest_file = util::important_paths::find_root_manifest_for_wd(None, &layout.root) ...
I use scripts/cargo.sh to develop locally but, Docker build uses docker/build.sh. It would be great to use one script for the cargo build and optimization.Activity Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment...