Sorry. Generally I have no problems linking (Debug executables) to Release
libraries. For example in the linker options I specify icuuc.lib or
icuucd.lib to link boost::regex to the ICU Debug or Release Library. Both
cases works well in Debugging. So the idea to force the debug python
libraries is a overkill.
Now, when using boost::python in _DEBUG then it is better to use python too
in _DEBUG or it's standard release version? I think it's better to use the
release version because else as you said you have to download and rebuild
the python library only because I want boost in _DEBUG.
Of course the best would be to modify boost::python so that we can choose if
to use python debug or release, even better if we can choose this at link
time like I do with other libraries.
IMHO...
-----Messaggio originale-----
Da: boost-users-bounces@lists.boost.org
[mailto:boost-users-bounces@lists.boost.org] Per conto di Markus Werle
Inviato: mercoledì 13 agosto 2008 8.22
A: boost-users@lists.boost.org
Oggetto: Re: [Boost-users] [python] partially resolved: the never
endingstoryof vc8/win32 linker settings desaster
Andrea Denzler
I think you can always choose which libraries to link with. If you don't want python.lib/dll then don't include it or add it to the ignore library list.
You completely missed the point.
I suggest you to add the linker option /VERBOSE:LIB
Of course I use /VERBOSE to find out what is going on. Markus _______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users