-
-
Notifications
You must be signed in to change notification settings - Fork 4
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
Fix binary artifacts for Mac #21
Conversation
.circleci/config.yml
Outdated
@@ -135,7 +134,7 @@ jobs: | |||
name: Build binary | |||
command: | | |||
source /Users/$(whoami)/.bashrc | |||
GOARCH=arm64 go build -tags "fts5" -o pod-babashka-go-sqlite3 main.go | |||
go build -tags "fts5" -o pod-babashka-go-sqlite3 main.go |
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.
Maybe be explicit about the environment here and keep GOARCH?
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.
Same as the other comment, thought to keep the var set only where its needed and only vary the instance types.
.circleci/config.yml
Outdated
@@ -50,10 +50,6 @@ jobs: | |||
command: curl -L https://git.io/vQhTU | bash | |||
- run: | |||
name: Build binary | |||
environment: |
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.
Why is this removed?
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.
I should add the CGO_ENABLED one, but the GOARCH and GOOS felt like another point of change apart from the instance type its running on. Felt better to remove since we have dedicated instances; would be better to keep if we cross compiled for all in a single instance.
@lispyclouds I made some comments but maybe you can't see them so I'm posting it as screenshot here as well. ![]() ![]() It seems that the only changes needed are to the test build script + test? E.g. why is CGO removed from the linux aarch build? |
Answered them, adding the CGO back but want to know of what you think of my reasons for removing the others. |
@lispyclouds I think we should only change something if we are solving a problem. Just changing the test binary name solves the problem so I'd only change that. |
Why are we even building a separate test binary? |
IIRC it was to aid in local testing, to not build separately too. The commit was from you: f7f8ab2 |
only the file changes are there now. we could use the binary built in the prev step for the tests but for arm macs, its going to run the amd binary and not sure if rosetta is setup? or if thats a comprehensive test or not with CGO etc |
Installing rosetta is very simple:
Since rosetta wasn't a problem before, why was a separate test binary used before? I don't get the reason for that still. |
Yeah I think we can avoid the test build but like I said before, I think you added it in the shape you had it in your local test setup in f7f8ab2 |
Alright. Thanks for hunting the bug down! I'll just merge this and make a release tomorrow. |
Addresses #19