GLFW respect GLFW_NO_API flag #12907
Merged
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
|
Thank you for submitting a pull request! If this is your first PR, make sure to add yourself to AUTHORS. |
kripken
requested changes
Dec 1, 2020
bfierz
force-pushed
the
feature/glfw-respect-no-client-api-flag
branch
from
e7db924 to
8a3de69
Compare
kripken
approved these changes
Dec 4, 2020
…ext (e.g. for usage with WebGPU)
bfierz
force-pushed
the
feature/glfw-respect-no-client-api-flag
branch
from
8a3de69 to
dfce118
Compare
|
Perfect. Thank you. |
kripken
reviewed
Dec 7, 2020
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.
In order to support the combined use of GLFW and WebGPU, GLFW should not assign anything to the Emscripten modules context variable. GLFW supports not creating any OpenGL context using the windows attribute GLFW_CLIENT_API.