[Python-Dev] Static builds on Windows (original) (raw)
"Martin v. Löwis" martin at v.loewis.de
Thu Jul 29 20:40:48 CEST 2004
- Previous message: [Python-Dev] Static builds on Windows
- Next message: [Python-Dev] Static builds on Windows
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Nick Coghlan wrote:
If there was going to be both the ability to create a static lib and a dynamic lib, it would seem to make more sense to have the project for the dynamic lib project simply incorporate the static lib, and export the relevant symbols.
Does that actually work? Doesn't the compiler generate different code depending on whether the code is going to be in a static vs. dynamic library?
If you can provide a patch to the project files which makes it happen for the VC7 projects, I would be very much in favour of including it (provided it can be demonstrated that it does actually work, and does not cause much overhead beyond the additional static library that is going to be generated).
Also, there is the issue of what C runtime to chose: should that be the static CRT, or a dynmaic one? Clearly, for the DLL, we need the dynamic CRT, but for the static python.lib, we might need a static CRT instead.
If the issue is only about repackaging the object files with an invocation of lib.exe - we could write a Python script that traverses the x86-temp-release directories, collecting all the object files and building a library from them.
Regards, Martin
- Previous message: [Python-Dev] Static builds on Windows
- Next message: [Python-Dev] Static builds on Windows
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]