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

make: add install and release-install goals #1890

Merged
merged 3 commits into from
Dec 11, 2023

Conversation

guggero
Copy link
Collaborator

@guggero guggero commented Sep 27, 2022

To simplify building the release-grade (stripped and
reproducible) binaries from source, we add the install and
release-install make goals. Running either of the commands will create
binaries in the $GOPATH/bin directories.
The main difference between the two goals is that the release-install
will not contain any local paths and no debug information.

@coveralls
Copy link

coveralls commented Sep 27, 2022

Pull Request Test Coverage Report for Build 7164900054

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage increased (+0.006%) to 56.047%

Totals Coverage Status
Change from base Build 7147733675: 0.006%
Covered Lines: 27966
Relevant Lines: 49897

💛 - Coveralls

Copy link
Collaborator

@sputn1ck sputn1ck left a comment

Choose a reason for hiding this comment

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

LTGM tACK! 🚀

@@ -40,3 +40,10 @@ coverage.txt
btcec/coverage.txt
btcutil/coverage.txt
btcutil/psbt/coverage.txt

# Binaries produced by "make build"
/addblock
Copy link
Member

Choose a reason for hiding this comment

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

Is the path here right? Why /addblock and not just addblock?

Copy link
Collaborator

@sputn1ck sputn1ck Feb 22, 2023

Choose a reason for hiding this comment

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

AFAIK /addblock will match any file or directory that is located in the root directory of the repository, while addblock will match any file or directory in any directory within the repository. It will match both files and directories with that name, meaning it would patternmatch more than just the generated binaries. (if they wouldn't have been comitted already)

Copy link
Member

@Roasbeef Roasbeef left a comment

Choose a reason for hiding this comment

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

LGTM 🐊

Just needs a rebase!

Copy link
Member

@jcvernaleo jcvernaleo left a comment

Choose a reason for hiding this comment

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

Yep, rebase and good to go.

The use of the GO111MODULE environment variable doesn't have any effect
anymore and hasn't for a couple of versions. The default was set to "on"
a while back, so we can remove that variable everywhere.
To simplify building the release-grade (stripped and
reproducible) binaries from source, we add the install and
release-install make goals. Running either of the commands will create
binaries in the $GOPATH/bin directories.
The main difference between the two goals is that the release-install
will not contain any local paths and no debug information.
@guggero
Copy link
Collaborator Author

guggero commented Dec 11, 2023

Rebased.

@jcvernaleo jcvernaleo merged commit 4f72645 into btcsuite:master Dec 11, 2023
3 checks passed
@guggero guggero deleted the build-improvements branch December 11, 2023 14:17
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.

5 participants