Skip to content

Conversation

@gottesmm
Copy link
Contributor

@gottesmm gottesmm commented Sep 1, 2021

Previously, we used SWIFT_INCLUDE_TESTS to control if we created build rules for
binaries just used to test as well as running the tests as well. In this commit,
I changed this behavior by adding an option called SWIFT_INCLUDE_TEST_BINARIES.
This will allow for the stage 1 swift build to build and install test binaries
into the just built toolchain for use by the stage 2 swift that builds the
stdlib.

…'t going to run the actual tests.

Previously, we used SWIFT_INCLUDE_TESTS to control if we created build rules for
binaries just used to test as well as running the tests as well. In this commit,
I changed this behavior by adding an option called SWIFT_INCLUDE_TEST_BINARIES.
This will allow for the stage 1 swift build to build and install test binaries
into the just built toolchain for use by the stage 2 swift that builds the
stdlib.
@gottesmm gottesmm requested a review from drexin September 1, 2021 23:33
@gottesmm
Copy link
Contributor Author

gottesmm commented Sep 1, 2021

@swift-ci smoke test

@gottesmm gottesmm merged commit b62c1dc into swiftlang:main Sep 2, 2021
@gottesmm gottesmm deleted the pr-1e3292b006649eb175a2cc6f5adc10705fe20425 branch September 2, 2021 19:24
MaxDesiatov pushed a commit that referenced this pull request Dec 7, 2021
…st tools (#40375)

Building the tests has been disabled when cross-compiling the toolchain almost from the beginning, but #39130 enabled building the test binaries by default again, so I had to locally disable building those tests when cross-compiling a standalone stdlib for Android.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants