Re: [xml] Makefile, configure.js and DSP comments
- From: <oliverst online de>
- To: <xml gnome org>
- Cc: <eday obj-sys com>
- Subject: Re: [xml] Makefile, configure.js and DSP comments
- Date: Thu, 16 Oct 2003 15:42:01 +0200
- in the configure.js an additional kind of static build should be added
("dll" using LIBXML_STATIC_FOR_DLL)
I have fussed with Igor about this in the past. I think the LIBXML_STATIC
option is already causing a static library for DLL to be created (i.e. it
compiles with -MD option which causes the MSVCRT.dll to be included on
link). A true static library on Windows should be compiled with -ML or
-MT
to cause the static C run-time library to be linked in.
Is this what you are referring to in this option, or is there more to it?
No, I meant a third state of static. So you can choose between "no",
"normal static" and "static for DLL".
Because the library is different when being compiled only with
LIBXML_STATIC or with LIBXML_STATIC and LIBXML_STATIC_FOR_DLL. Not
having the latter may cause problems, when linking the static lib into a
DLL (see some earlier posts to the list).
But as Stéphane pointed out, you can't have LIBXML_STATIC_FOR_DLL
defined along with HAVE_COMPILER_TLS.
to sum it up
static
no - no defines
normal - LIBXML_STATIC
dll - LIBXML_STATIC and LIBXML_STATIC_FOR_DLL (warning if
HAVE_COMPILER_TLS is defined?)
Not sure, if it should be part of the configure.js or not, but it would
have helped a few weeks ago, if it jumped right into my face when I
looked at the configuraion ;)
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]