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

Building one tool after another reduces temporary build space required dramatically #43

Open
CodingMarkus opened this issue Dec 30, 2021 · 1 comment

Comments

@CodingMarkus
Copy link

Currently the script is like this:

  • Download everything
  • Extract everything
  • Patch everything
  • Build everything

Yet if you were implementing #42, there are situations were it would make sense to organize the script as follows:

  • Download just the Freetype archive
  • Unpack the Freetype archive
  • Delete the Freetype archive
  • Download the Freetype patches
  • Apply the Freetype patches
  • Delete the Freetype patches
  • Build Freetype
  • Install Freetype
  • Delete the Freetype source folder

And now continue that loop again once for the other two tools.

How would that make a difference? When the script is running inside a virtual file system (VM, Docker, macOS Diskimage, etc.) these grow dynamically but they have a hard time shrinking again. Organizing the build process as suggested above results in way smaller virtual disk images in the end, as a lot less temporary space will be needed during the build process. It also makes it possible to run your scrips on machines with very little disk space available that currently would run out of space when running your script.

@chrissimpkins
Copy link
Member

Very open to PR's to change it! Fire away.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants