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

Disable building leap-dev.deb package by default #1448

Merged
merged 1 commit into from
Jul 26, 2023

Conversation

spoonincode
Copy link
Member

A leap-dev.deb package is currently generated alongside the leap.deb package when performing a make package (as our README suggests). This leap-dev.deb, similarly to the make dev-install target, contains the files required for "native contract unit testing" a.k.a. libtester. afaik we don’t document this leap-dev.deb, nor do we include it as part of leap’s release assets. Instead, it’s used for punting around libtester in various Antelope CI use cases so that leap doesn’t need to always be rebuilt; for example, eos-system-contracts CI uses leap-dev.deb for its unit tests so that it doesn’t need to build leap just to run the system contract unit tests.

Unfortunately adding boost to leap-dev.deb is increasing the time it takes to perform make package significantly: from 30 seconds to 7 minutes. If we leave the README instructions as make package, it’ll take some users longer to build the .deb packages than building the software!

Because the sole use case of leap-dev.deb is Antelope CI usage, disable building leap-dev.deb by default, and just enable it in leap’s CI.

@greg7mdp
Copy link
Contributor

@spoonincode do you want me to merge this commit, and then catchup the boost_submodule branch with main?

@spoonincode
Copy link
Member Author

Either way is/was fine with me; it's more of a "suggest changes" kind of PR that doesn't even require a review for you to decide to merge it in.

@greg7mdp greg7mdp merged commit a2209af into boost_submodule Jul 26, 2023
@greg7mdp greg7mdp deleted the no_leap-dev_default branch July 26, 2023 11: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.

3 participants