Hello Marcus,

Marcus Lindblom wrote:
> Hi,
> 
> I'm upgrading our app to VC9 and also our OpenSG 1.8 snapshot from 
> 2007-11-30 to something more recent. It runs fine in release mode, but 
> fails in debug.
> 
> Now, I am doing some magic, so I suspect it's related to that, but I've 
> been fiddling with it for two weeks now and just wanted to check if 
> anyone else has any advice.
> 
> The main thing is that we compile our app with some more _SCL-defines 
> that OpenSG does by default. I've hacked these into Sconstruct:
> 
>          if _po.getOption('no_secure_stl'):
>              env.Append(CPPDEFINES=['_SECURE_SCL=0'])
>              env.Append(CPPDEFINES=['_SECURE_STL_THROWS=0'])
>              env.Append(CPPDEFINES=['_HAS_ITERATOR_DEBUGGING=0'])
>              env.Append(CPPDEFINES=['_SCL_SECURE_NO_WARNINGS'])
>              env.Append(CPPDEFINES=['_SCL_SECURE_NO_DEPRECATE'])
>              env.Append(CPPDEFINES=['_CRT_SECURE_NO_DEPRECATE'])
> 
> in all three places where vc8/9 is used, just to be consistent. The 
> scons-output confirms these being passed to the compiler.
> 
> It compiles just fine (both OpenSG itself and all our app code that uses 
> OpenSG) and works in release mode, but running in debug I get strange 
> errors, such as:
> 
>   * Counting the FieldContainerStore goes way past end(), 
> (stl-incompatibility?)
>   * Window->deactivate() complains about return address corruption (and 
> suggests different calling conventions).

that sounds very strange indeed. As I know very little about windows 
development and the peculiarities of the tools there, I can only take a 
stab in the dark: Do any of the above options change the ABI of the 
libraries and as a result you'd have to link against a different runtime?

> I believe this has to do with the defines and all, but I've managed to 
> recompile boost using those defines, and that works, so I wonder if 
> there's anything I might've forgotten/overlooked?

Did you use any of the boost libs that actually compile to a lib or only 
the header-only stuff. The latter would probably not be affected by a 
lib incompatibility.

        regards,
                Carsten


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Opensg-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-users

Reply via email to