https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=1.68.2 2022-12-14T19:33:08+00:00 2022-12-14T19:33:08+00:00 Chris Wailes chriswailes@google.com 2022-09-26T22:50:56+00:00 urn:sha1:0fb426ace4ed07bc023863ebd8103ac49fba1283 This commit updates the CI definitions to use the most recent Android LTS NDK release: r25b. Changes since the last NDK used by Rust negate the need to generate "standalone toolchains" and newer NDKs can be used in-place. See https://developer.android.com/ndk/guides/other_build_systems#overview 2022-11-20T02:48:26+00:00 Alex Pinkus pinkus@amazon.com 2022-11-20T01:50:48+00:00 urn:sha1:6f1c7b24705d8e744ddea9b445cb70e0a0d328cb This reverts commit bf7f1ca316a249cf99d722d79a0db12fef687142. 2022-11-17T08:37:39+00:00 Pietro Albini pietro.albini@ferrous-systems.com 2022-11-03T14:01:39+00:00 urn:sha1:6d8160261ff3aee3b6eaacc37ac96cafff530980 2022-10-04T19:14:14+00:00 Chris Wailes chriswailes@google.com 2022-09-26T22:50:56+00:00 urn:sha1:bf7f1ca316a249cf99d722d79a0db12fef687142 This commit updates the CI definitions to use the most recent Android LTS NDK release: r25b. Changes since the last NDK used by Rust negate the need to generate "standalone toolchains" and newer NDKs can be used in-place. See https://developer.android.com/ndk/guides/other_build_systems#overview 2022-06-27T18:46:57+00:00 Daniel Paoliello danpao@microsoft.com 2022-06-23T20:05:42+00:00 urn:sha1:1fca2468420bb5ac2f6868bddc65e164dd05dbfb When attempting to build rustc with LLVM on Windows, I noticed that the CRT flag provided to the C and C++ Compilers was inconsistent: ``` "-DCMAKE_C_FLAGS=-nologo -MT -Brepro" "-DCMAKE_CXX_FLAGS=-nologo -MD -Brepro" ``` Since the bootstrapper also sets the various `LLVM_USE_CRT` variables, this resulted in cl.exe reporting a bunch of warnings: ``` cl : Command line warning D9025 : overriding '/MD' with '/MT' ``` The root cause for this is that `cc_detect::find` was creating a `cc::Build` twice, but didn't set `static_crt` the second time. It's possible that this what is also causing #81381 2022-04-15T14:51:09+00:00 Nikita Popov nikita.ppv@gmail.com 2022-04-15T14:51:09+00:00 urn:sha1:dcc3554c62d611ab5b9182f11a4954294832365b The ranlib specified for the target was never actually transferred into the builder configuration. In the dist-x86_64-linux build we ended up using ranlib instead of llvm-ranlib. 2022-03-05T14:31:22+00:00 bjorn3 bjorn3@users.noreply.github.com 2022-03-03T17:15:01+00:00 urn:sha1:e657da72aa4bd7ed5edda194b770903ea0cf1dd1 2022-03-05T14:31:22+00:00 bjorn3 bjorn3@users.noreply.github.com 2022-02-24T12:30:50+00:00 urn:sha1:0cfc3e101689d050432f600a35e953413b87147f The majority of the code is only used by either rustbuild or rustc_llvm's build script. Rust_build is compiled once for rustbuild and once for every stage. This means that the majority of the code in this crate is needlessly compiled multiple times. By moving only the code actually used by the respective crates to rustbuild and rustc_llvm's build script, this needless duplicate compilation is avoided. 2022-03-03T17:42:23+00:00 Jon Gjengset jongje@amazon.com 2022-03-01T00:40:08+00:00 urn:sha1:9c05f0b72c99cc91117282f7f267964824f187bf First, this reverts the `CFLAGS`/`CXXFLAGS` of #93918. Those flags are already read by `cc` and populated into `Build` earlier on in the process. We shouldn't be overriding that based on `CFLAGS`, since `cc` also respects overrides like `CFLAGS_{TARGET}` and `HOST_CFLAGS`, which we want to take into account. Second, this adds the same capability to specify target-specific versions of `LDFLAGS` as we have through `cc` for the `C*` flags: https://github.com/alexcrichton/cc-rs#external-configuration-via-environment-variables Note that this also necessitated an update to compiletest to treat CXXFLAGS separately from CFLAGS. 2020-10-19T14:37:04+00:00 Jonas Schievink jonasschievink@gmail.com 2020-10-14T12:27:49+00:00 urn:sha1:0558e6eb9337960a1415e037ae7a44e3aa947479 This allows us to use the C++ compiler configured via `CXX_target_triple` env vars