building: Support arbitrarily large files in onefile mode. #4640
Conversation
This file contains 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
This has the advantage that hints on the processing of the data can be given.
Previously, the maximum file size in CArchive was 2 GB, otherwise the size value could not be stored. This was also not very beneficial, because the bootloader allocates the size of the file in memory during unpacking, which is a huge amount of data at once. Now files larger than 512 MiB are divided into several archive entries and thus unpacked to one file in several steps.
|
The attempt was a bit hasty: If files become larger than 2GB, the offset in the TOC becomes larger than |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Previously, the maximum file size in CArchive was 2 GB, otherwise
the size value could not be stored. This was also not very
beneficial, because the bootloader allocates the size of the file
in memory during unpacking, which is a huge amount of data at once.
Now files larger than 512 MiB are divided into several archive entries
and thus unpacked to one file in several steps.
fixes #3939