The build macro redirects to pre-packaged Windows APIs
#1338
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
kennykerr
changed the title
build macro redirects to pre-packages Windows APIsbuild macro redirects to pre-packaged Windows APIs
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.
The
buildmacro generates bindings for desired APIs from metadata. The need for this macro is substantially reduced with the introduction of pre-packaged APIs in 0.22 but is still useful if you have a 3rd party component. This update just ensures that any references to Windows APIs from such non-Windows APIs redirect to thewindowscrate rather than generating entirely new bindings for the Windows API.The
build_legacymacro has been added temporarily to provide the old behavior but this macro will eventually be removed.