Hello all, I'm progressing with my mingw port. The current state is that I can build a Python DLL and EXE with only minimally babysitting the build process. This looks already pretty nice, doesn't it? Python 2.3a0 (#47, Mar 8 2002, 08:49:19) [GCC 2.95.3-6 (mingw special)] on mingw32_nt-5.11 Type "help", "copyright", "credits" or "license" for more information. >>> :-) The only "babysitting" needed is to add threadmodule.o, posixmodule.o and signalmodule.o to the MODULE_OBJS in the Makefile. Problem 1 is how to get rid of that? Anybody has an idea? Problem two is that even if I add these to the MODULE_OBJS, Modules/config.c isn't appropriately created. I currently haven't got any idea how to achieve this. To be honest, the part of the build process (Modules/makesetup and friends) which statically links modules to the Python interpreter puzzles me as a whole. It would be really nice if you could give me some tips. Gerhard
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4