Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
We recently received a new laptop (a donation) with an architecture not compatible with amd64 builds. Fortunately, we can create compatible images with some small changes.
By default, the makefile will continue generating amd64 images. We can generate i386 images by running
make i386.Initially, this should be as simple as mentioning the desired architecture compatibility when calling
lb config. Unfortunately there were a few hitches:cachedirectory before a build solves this, but deleting the cache slows the build significantly. As a solution, I'm keeping architecture-specific cache directories, symlinked fromcache. The Live Build commands do not appear to allow us to customize the cache directory, hence the symlink.