Standardize build process and staging for coreutils#140
Open
Standardize build process and staging for coreutils#140
Conversation
…sion for coreutils
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Closes #126
Standardizes the build pipeline and artifact staging for coreutils.
Fixed STAGE_DIR path to follow the build/coreutils/bin/coreutils/ convention in compile_coreutils.sh.
Added binary rename step inside the cwasm loop to copy each .cwasm output to a final staged binary with no extension, handling multiple binaries correctly.
Updated Makefile comment to reflect the correct output path.
Note: Full local build test was skipped due to disk space constraints on the dev server (3.6G free). The changes follow the identical pattern verified working in sed, grep, curl, and git (PRs #133 and #139).