-
-
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
Fix dwFlags on CreateProcessW calls #54591
Conversation
This is the right fix according to the official docs. Will make sure and test. |
Built & tested, seems to work fine. Funnily enough, I don't actually seem to get a console window with current master though? Not sure why. Anyway, this is correct, the current code doesn't work. Edit: does the additional console window without this only show up in release exports? May be the case the otherwise existing default console window gets inherited. Will check. |
Thanks! |
@mhilbrunner It's deeper than that though. This doesn't fix all the problems related to command prompts showing up (for me at least), it fixes only the flag passing that was wrong. The main problem when trying to launch an executable from godot (I'm building a game launcher) is that OS.execute will always pass a non-null Line 230 in 4d96d37
This makes the process execute with godot/platform/windows/os_windows.cpp Line 424 in 4d96d37
instead of CreateProcessW + Win32 pipe functions.
I had to comment this whole block and start using a custom built template to get rid of that command prompt as I'm not interested in the output, only the exit codes. godot/platform/windows/os_windows.cpp Lines 416 to 442 in 4d96d37
|
Command prompt is still being shown when calling
os.execute
on Windows. The previous flags always results in 0 because flags should be merged with an OR operator.Bugsquad edit: May help with #52242.