Skip to content

Conversation

@Flamefire
Copy link
Collaborator

Instead of cloning the Boost main repository and later potentially many submodules (by depinst.py) we can cache the last checkout.

On any changes the checkout-and-pull should update it to the appropriate version.

Closes #240

@Flamefire Flamefire force-pushed the cache-boost branch 7 times, most recently from ee676cc to 5aa75a4 Compare November 26, 2024 13:24
@Flamefire
Copy link
Collaborator Author

@jeking3 This seems to work now. Can you take a look? You can copy that to your repo once this is merged as the change to the script is required because the b2 binary will also be cached and might not always work.

Instead of cloning the Boost main repository and later potentially many
submodules (by `depinst.py`) we can cache the last checkout.
On any changes the checkout-and-pull should update it to the appropriate
version.
When we copy the whole boost-root AFTER the build(s) it will contain
also build artefacts such as the bin.v2 folder.
When restoring that later B2 might skip parts of the build although it
should not.
Make a copy after the initial setup & bootstrap.
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.

Can we use GHA caching of the checked-out code and dependencies to reduce build burden?

2 participants