Martin v. Löwis wrote:
Robin Becker wrote:
I don't think this forces the linker to load stuff from this module
although I can see that it might be dangerous depending on which obj
files are seen first.
I think you are wrong. In the object, there will be simply a linker
command line option encode
Robin Becker wrote:
I don't think this
forces the linker to load stuff from this module although I can see that
it might be dangerous depending on which obj files are seen first.
I think you are wrong. In the object, there will be simply a linker
command line option encoded; do "dumpbin /all foo.
Martin v. Löwis wrote:
Robin Becker wrote:
I thought that static .libs didn't make reference to the dll's they
need; isn't that done at load time?
Unfortunately, thanks to Microsoft's infinite wisdom, static libs
*do* reference DLLs. The C lib headers contain things like
#pragma lib("msvcrt.lib")
Robin Becker wrote:
I thought that static .libs didn't make reference to the dll's they
need; isn't that done at load time?
Unfortunately, thanks to Microsoft's infinite wisdom, static libs
*do* reference DLLs. The C lib headers contain things like
#pragma lib("msvcrt.lib") // or some such
The com
Robin Becker wrote:
I guess that it won't work if something malloc'ed from the MSC 6
runtime is free'd by the MSC 7.1 runtime.
I thought that static .libs didn't make reference to the dll's they
need; isn't that done at load time?
You're right, DLL-phobia made my thinking less than precise.
The o
Daniel Dittmar wrote:
Robin Becker wrote:
actually I want to build the PIL extension for 2.4 as pyd and include
various libraries eg zlib and jpeg. To avoid the missing dlls issue we
have done this in the past by incorporating the zlib/jpeg code using
static libraries for both zlib and jpeg.
It
Robin Becker wrote:
actually I want to build the PIL extension for 2.4 as pyd and include
various libraries eg zlib and jpeg. To avoid the missing dlls issue we
have done this in the past by incorporating the zlib/jpeg code using
static libraries for both zlib and jpeg.
It seems I can use the s
Daniel Dittmar wrote:
Robin Becker wrote:
Does anyone know if it is feasible to have static libraries for both
2.3 and 2.4 compatible extensions. I'm worrying about libjpeg etc in a
win32 environment.
Could you be a bit more specific:
do you want to create a binary python extension that is compa
Robin Becker wrote:
Does anyone know if it is feasible to have static libraries for both 2.3
and 2.4 compatible extensions. I'm worrying about libjpeg etc in a win32
environment.
Could you be a bit more specific:
do you want to create a binary python extension that is compatible with
both Python
Does anyone know if it is feasible to have static libraries for both 2.3 and 2.4
compatible extensions. I'm worrying about libjpeg etc in a win32 environment.
--
Robin Becker
--
http://mail.python.org/mailman/listinfo/python-list
10 matches
Mail list logo
