Skip to content
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

[tailscale1.20] .github/workflows: add a static build for testing. #39

Merged
merged 1 commit into from
Feb 2, 2023

Conversation

danderson
Copy link
Member

Only x86 linux for now, to try out using a static toolchain.

Signed-off-by: David Anderson dave@natulte.net

Only x86 linux for now, to try out using a static toolchain.

Signed-off-by: David Anderson <dave@natulte.net>
- name: build
run: cd src && ./make.bash
env:
CGO_ENABLED: "0"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think just doing this will be too problematic on callers (casual developers in the tree ... we can't just force it back to true easily. We want to have the same magic behavior as not setting)

So I think we want to modify our Go tree as well.

But you can start with this and see.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I want this right now so I can try to update all our toolchain goop to use static builds and see if I can make it all work out. If it does, we can tweak the default behavior before rolling it out more, yeah.

@danderson danderson merged commit 26292c0 into tailscale.go1.20 Feb 2, 2023
@danderson danderson deleted the danderson/static-toolchain branch February 2, 2023 00:29
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