-
-
Notifications
You must be signed in to change notification settings - Fork 21.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[4.0] Platform export refactoring #50771
[4.0] Platform export refactoring #50771
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The Android section looks good!
Needs a rebase, otherwise seems good to merge. |
67f60f0
to
253581f
Compare
Thanks! |
} else if (mode == EXPORT_MODE_GDNATIVE) { | ||
r_features->push_back("wasm32"); | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What's the reason to not just always have wasm32
as an export feature for the JavaScript platform?
Previous PR: #50467
Another approach at export refactoring proposal: godotengine/godot-proposals#2929 that was suggested there.
Allows to use
.cpp
files other thanexport.cpp
for platform's export template. Keeps current structure where export folder and it's code is kept with platform.export.cpp
files for each platform are also separated into more files for initial refactoring.Future PRs could bring more changes to exports to cleanup the code and make it easier to navigate.