Bundle ecs-go binaries with ECS, so --turbo works out of the box - #85
Merged
Merged
Conversation
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
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.
Running
vendor/bin/ecs --turboin a project without ecs-go ended with a bare shell error:Now the ecs-go binary ships with ECS:
mainfor linux/darwin × amd64/arm64 intobin/turbo/(stripped, ~3.7 MB each)EcsGoBinaryLocatorpicks the one matching the current OS and arch, restoring the executable bit if archive extraction dropped itECS_TURBO_BIN→ bundled →vendor/bin/ecs-go→ PATHsyscall.SYS_IOCTL),--turbofails with a clear error instead of the shell one