Repository navigation
docs: fix existing-checkout import and low-memory build instructions - #18
Merged
Merged
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.
Problem
The installation guide first clones POSIM, then imports a manifest containing that existing checkout. With Ubuntu's vcstool 0.3.x,
--shallow --skip-existingraisesAttributeError: 'NoneType' object has no attribute 'startswith'on existing Git repositories.Also,
colcon --executor sequentialserializes packages but does not restrict compiler jobs within each package. A 4 GiB ARM64 build can still be killed for lack of memory.Changes
--shallowfrom the import command in both English and Korean guides; retain--skip-existing.MAKEFLAGS="-j1"andCMAKE_BUILD_PARALLEL_LEVEL=1. The former also prevents colcon's Makefile backend from adding its own parallel job count.Validation
This is a focused installation-instruction correction, not a claim that every supported platform has passed a new clean installation.