Re: [MSVC8] libxml2 and libiconv
Thiago Macieira schrieb:
Christian Ehrlicher wrote:
Apart from this, I currently stopped msvc compilation because you can't
do anything with the resulting apps (it crshes all over the time)
because we mix release and debug libs.
KDE has never had that problem because none of the systems we've supported
so far had a difference between release and debug builds.
Can you explain what is different and what we have to do in order to be
compliant?
Because MSVC is using two different msvcrt - libraries (one release and
one debug version) you can't mix debug and release libs without a crash
sooner or later. Qt introduced the debug-prefix ('d' or '_debug') to
work around this problem and we need this for kde too. I don't know any
other way to be sure to not mix the libs... :-(
Christian
signature.asc
Description: OpenPGP digital signature
___
Kde-buildsystem mailing list
Kde-buildsystem@kde.org
https://mail.kde.org/mailman/listinfo/kde-buildsystem
Re: [MSVC8] libxml2 and libiconv
Christian Ehrlicher wrote:
Because MSVC is using two different msvcrt - libraries (one release and
one debug version) you can't mix debug and release libs without a crash
sooner or later. Qt introduced the debug-prefix ('d' or '_debug') to
work around this problem and we need this for kde too. I don't know any
other way to be sure to not mix the libs... :-(
Ok, so we need to support that on Windows. I.e., if we're linking against
the debug Qt build, we generate debugging ('d') libraries.
On MacOS X, from what I hear, the frameworks have both libraries -- i.e.,
nothing + _debug. So it looks like we should support the same.
On all the other Unix, I'd rather we didn't introduce anything right now.
Switching libraries is very useful and I'd rather not have to rebuild my
whole KDE just because I want to debug something in kdecore or Qt.
--
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
thiago.macieira (AT) trolltech.com Trolltech AS
GPG: 0x6EF45358 | Sandakerveien 116,
E067 918B B660 DBD1 105C | NO-0402
966C 33F5 F005 6EF4 5358 | Oslo, Norway
pgp5kDRyDCLTy.pgp
Description: PGP signature
___
Kde-buildsystem mailing list
Kde-buildsystem@kde.org
https://mail.kde.org/mailman/listinfo/kde-buildsystem
Re: [MSVC8] libxml2 and libiconv
On 4/17/06, Thiago Macieira [EMAIL PROTECTED] wrote: On MacOS X, from what I hear, the frameworks have both libraries -- i.e., nothing + _debug. So it looks like we should support the same. Yes, but I believe when linking you only specify the main name of the framework. To have it use the debug version you set the DYLD_IMAGE_SUFFIX environment variable to _debug like this: DYLD_IMAGE_SUFFIX=_debug and that causes it to load the debug framework at runtime. It can also be enabled from within XCode. Ref: http://developer.apple.com/technotes/tn2004/tn2124.html#SECDEBUGLIB Cheers, Tanner -- Tanner Lovelace clubjuggler at gmail dot com http://wtl.wayfarer.org/ (fieldless) In fess two roundels in pale, a billet fesswise and an increscent, all sable. ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
Re: [MSVC8] libxml2 and libiconv
Christian Ehrlicher wrote: Apart from this, I currently stopped msvc compilation because you can't do anything with the resulting apps (it crshes all over the time) because we mix release and debug libs. KDE has never had that problem because none of the systems we've supported so far had a difference between release and debug builds. Can you explain what is different and what we have to do in order to be compliant? -- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org thiago.macieira (AT) trolltech.com Trolltech AS GPG: 0x6EF45358 | Sandakerveien 116, E067 918B B660 DBD1 105C | NO-0402 966C 33F5 F005 6EF4 5358 | Oslo, Norway pgpyu2A0gHMwF.pgp Description: PGP signature ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
Re: [MSVC8] libxml2 and libiconv
Michael Drüing wrote: for some reason I get an error each time something links to libxml2.lib, because libxml2.lib needs iconv.lib which is not linked in automatically. I think I remember someone mentioning here on the list that MSVC doesn't do this, so I think this should be fixed in the CMake files... Like, for example, checking if a test-program that links to libxml2.lib (or xml2.lib, whichever was detected) also needs to be explicitly linked to iconv.lib (or maybe libiconv.lib) And then libxml2.lib changes its dependencies in the future, how do we cope? This is the wrong question to ask. The right question is: in which *installed* file does libxml2.lib store its dependency information? Is it the lib itself? Does the linker automatically link to the dependencies? If not, how can we extract the information from it? -- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org thiago.macieira (AT) trolltech.com Trolltech AS GPG: 0x6EF45358 | Sandakerveien 116, E067 918B B660 DBD1 105C | NO-0402 966C 33F5 F005 6EF4 5358 | Oslo, Norway pgpSYNFkXqgRq.pgp Description: PGP signature ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
Re: [MSVC8] libxml2 and libiconv
Thiago Macieira schrieb: Michael Drüing wrote: for some reason I get an error each time something links to libxml2.lib, because libxml2.lib needs iconv.lib which is not linked in automatically. I think I remember someone mentioning here on the list that MSVC doesn't do this, so I think this should be fixed in the CMake files... Like, for example, checking if a test-program that links to libxml2.lib (or xml2.lib, whichever was detected) also needs to be explicitly linked to iconv.lib (or maybe libiconv.lib) And then libxml2.lib changes its dependencies in the future, how do we cope? This is the wrong question to ask. The right question is: in which *installed* file does libxml2.lib store its dependency information? Is it the lib itself? Does the linker automatically link to the dependencies? If not, how can we extract the information from it? Afaik the import lib *only* depends on it's shread lib and nothing more. So I think Michael is using a static libxml which is wrong. Apart from this, I currently stopped msvc compilation because you can't do anything with the resulting apps (it crshes all over the time) because we mix release and debug libs. Christian signature.asc Description: OpenPGP digital signature ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
