Message123523
| Author |
jonny |
| Recipients |
amaury.forgeotdarc, eric.araujo, jonny, loewis, rpetrov |
| Date |
2010年12月07日.06:54:22 |
| SpamBayes Score |
1.8881163e-09 |
| Marked as misclassified |
No |
| Message-id |
<1291704863.99.0.41478894947.issue10615@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
- Why is the generated pyconfig.h not good enough? Could we modify the ./configure script instead?
Probably setup.py needs to be extended; I did not have a deep look into the build system though
- the "empty.c" should remain empty... Why not use PC/WinMain.c instead?
It seems to be that MinGW does not support the wWinMain unicode entry point; the empty.c hack is just to show that it's actually linking
- why is a WinMain required when python.c is supposed to define a
main()?
Good question; probably just a question of linker flags; I will have a look if my time permits
- Is the final binary a console application or a Windows application?
A Console application; creating a GUI application is easily done with the "-mwindows" gcc flag, but then you will have no Python console when not using idle or similar |
|