Add version.h
defining WASI_LIBC_VERSION
#534
Draft
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.
This change re-imagines wasi-sdk#487 entirely in
wasi-libc
. Instead of generating aversion.h
header late--inwasi-sdk
--it is generated immediately whenwasi-libc
is built. This has the disadvantage that we don't know whatwasi-sdk
this will be used in... but almost: when releasingwasi-sdk
, we should be tagging thewasi-libc
repository. If we did that more faithfully (docs), this commit would generate:Using the magic of
git-describe
, if someone is usingwasi-libc
directly, they may see a version like:wasi-sdk-22-19-g5d3c5e9-dirty
. This should be read like:<wasi-sdk tag>-<# commits since tag>-<current commit>-<is the repository dirty?>
.