-
Notifications
You must be signed in to change notification settings - Fork 222
Refactor handling env vars in CI build #455
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
alexcrichton
merged 2 commits into
WebAssembly:main
from
alexcrichton:refactor-env-vars
Jul 22, 2024
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,23 +1,11 @@ | ||
| FROM wasi-sdk-builder-base | ||
|
|
||
| # Install an extra C++ toolchain which can target arm64 linux. | ||
| RUN apt-get install -y g++-aarch64-linux-gnu | ||
|
|
||
| # Don't build a sysroot for this cross-compiled target since it would require a | ||
| # host compiler and the sysroot is otherwise already built on other CI builders. | ||
| ENV WASI_SDK_CI_SKIP_SYSROOT 1 | ||
|
|
||
| ENV WASI_SDK_CI_TOOLCHAIN_LLVM_CMAKE_ARGS \ | ||
| -DCMAKE_C_COMPILER=aarch64-linux-gnu-gcc \ | ||
| -DCMAKE_CXX_COMPILER=aarch64-linux-gnu-g++ \ | ||
| -DCMAKE_CROSSCOMPILING=True \ | ||
| -DCMAKE_CXX_FLAGS=-march=armv8-a \ | ||
| -DCMAKE_SYSTEM_PROCESSOR=arm64 \ | ||
| -DCMAKE_SYSTEM_NAME=Linux \ | ||
| -DLLVM_HOST_TRIPLE=aarch64-linux-gnu \ | ||
| -DRUST_TARGET=aarch64-unknown-linux-gnu | ||
|
|
||
| ENV WASI_SDK_CI_TOOLCHAIN_CMAKE_ARGS \ | ||
| -DWASI_SDK_ARTIFACT=arm64-linux \ | ||
| -DRUST_TARGET=aarch64-unknown-linux-gnu | ||
|
|
||
| # Configure Rust to use this new compiler for linking Rust executables. | ||
| ENV CARGO_TARGET_AARCH64_UNKNOWN_LINUX_GNU_LINKER aarch64-linux-gnu-gcc | ||
|
|
||
| # Note that `.github/workflows/main.yml` sets various bits and bobs of | ||
| # configuration and cmake flags that may get passed to the underlying build. For | ||
| # example LLVM is instructed to use the toolchain installed above. | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,4 +1,7 @@ | ||
| FROM wasi-sdk-builder-base | ||
|
|
||
| ENV WASI_SDK_CI_TOOLCHAIN_CMAKE_ARGS \ | ||
| -DWASI_SDK_ARTIFACT=x86_64-linux | ||
| # No extra configuration necessary for x86_64 over what `Dockerfile.common` | ||
| # already has. | ||
| # | ||
| # Note though that `.github/workflows/main.yml` still sets various bits and bobs | ||
| # of configuration and cmake flags that may get passed to the underlying build. |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If run in some local workflow, these
Dockerfiles no longer will produce the expected output (or perhaps even work?). How do you feel about pointing that (potential) user back tomain.ymlfor the properWASI_SDK_CI_*setup that is expected from them?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's right yeah, although that was also already sort of true for the Windows/macOS builds since they've also got configuration in CI that would have to be copied down loacally. I'll leave some notes in the containers though.