Build venvlauncher.exe from PC/launcher.c

[naveen521kk]

Fixes #16

[naveen521kk]

these tests that are failing are broken on the mingw-v3.10.2 branch, so this PR didn't cause that. I think I'll just merge this. @lazka does this look good to you?

[lazka]

lgtm!

[lazka]

(note that on #85 mingw32 is failing for some reason, not sure if that is relevant for this)

[naveen521kk]

(note that on #85 mingw32 is failing for some reason, not sure if that is relevant for this)

Yeah, not sure why though. I'll just merge this and deploy it so that people can test.

[naveen521kk]

(note that on #85 mingw32 is failing for some reason, not sure if that is relevant for this)

Yeah, not sure why though. I'll just merge this and deploy it so that people can test.

I think we can't find it out here because the tests itself doesn't pass for the smoke tests to be run when installed. I think static linking on mingw32 is broken (maybe)? Should I make an issue in MINGW-packages repo about that?

[lazka]

Let's update the package so we can test it out

[naveen521kk]

I think static linking on mingw32 is broken (maybe)? Should I make an issue in MINGW-packages repo about that?

No, it isn't broken. Actually, the program executes outside of the virtual env without anything in PATH, so I think that error is only when the actual python interpreter is launched. I'm wondering why it happens only on mingw32 though.

[naveen521kk]

I think static linking on mingw32 is broken (maybe)? Should I make an issue in MINGW-packages repo about that?

No, it isn't broken. Actually, the program executes outside of the virtual env without anything in PATH, so I think that error is only when the actual python interpreter is launched. I'm wondering why it happens only on mingw32 though.

Also, this would mean this doesn't happen if python is installed in /mingw32/bin, since it should contain those GCC DLLs. Setting the launcher to debug mode (using PYLAUNCH_DEBUG env var), I could see this print

launcher build: 32bit
launcher executable: Console
File 'C:\dev\temp-test\mingw32\bin\.venv\bin\pyvenv.cfg' non-existent
Using venv configuration file 'C:\dev\temp-test\mingw32\bin\.venv\pyvenv.cfg'
Called with command line:
run_child: about to run 'C:/dev/temp-test/mingw32/bin\python.exe'
child process exit code: -1073741515

Though I'm still wondering how it works on mingw64.