[swift-users] Linking errors with latest git versions...

Marc Neeley neeleym at ociweb.com
Mon Mar 26 08:05:54 CEST 2012

In executing swiften-config.exe -cflags I get the following:


c:\dev\tools\swift\Swiften\Config>swiften-config --cflags



/tools/swift/Swiften/Config/../.. /Ic:/dev/tools/swift/Swiften/Config/../..




xpat\src /Ic:\OpenSSL-Win32\include


Obviously the /D_ITERATOR_DEBUG_LEVEL=0 is set such that the conflict will
occur.  Is there a flag for SCons that I can use to set this to 2?





From: Marc Neeley [mailto:neeleym at ociweb.com] 
Sent: Sunday, March 25, 2012 7:00 PM
To: swift-users at swift.im
Subject: Linking errors with latest git versions...


I pulled down the latest Swift git repo content and built it. It claims
everything built ok and I got clean libs, etc.  When I built my project
using the new Swiften.lib I get a stream of linking errors that follow the
same pattern as shown below:


Swiften_Boost.lib(connection.obj) : error LNK2038: mismatch detected for
'_ITERATOR_DEBUG_LEVEL': value '0' doesn't match value '2' in


Of course MessageEngine.obj is my code and Swiften_Boost.lib is from the
build of the Swift source. This is occurring for Swiften.lib  as well. The
error above typically is an indicator that one is being built with release
in mind and the other in debug. My project is being built with Debug on and
I was building cleanly with a pull from Feb 9, 2012 just yesterday. Has
something changed in scons such that the debug version is not the default?
Is there a switch for scons to force a debug build of the Swift libs?




Marc Neeley

Principal Software Engineer

Object Computing, Inc.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: </lists/pipermail/swift-users/attachments/20120326/0e05932a/attachment.htm>

More information about the swift-users mailing list