Repository navigation
docs: the 32-bit rows of openkal-platform 0.28.0 are served when a project states the platform - #939
Merged
Merged
Conversation
…oject states the platform; the built-in table keeps them planned
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.
Measured on mcpp 2026.11.15.1 in a clean xlings home:
mcpp run --target i686-linux-muslin a new project is refused as a planned row ("registered but not yet supported"); with[target.'cfg(os = "linux")'] platform = "openkal-platform@0.28.0"it builds and runs a static ELF 32-bit i386 program. The built-in platform does not serve a planned row (2026.11.14.1 serves one through a stated platform's targets).The comment of the 32-bit rows in
builtin.tomland the 2026.11.15.1 CHANGELOG entry said the engine's pin serves them; both now state the measured behaviour. No code changes.