Anders,

 

I have exactly the same problem. I get round it by doing two things.

1. Changing the collada build files (VC8 project file in my case) to
differentiate the collada release and debug build by library name not by
directory.

2. Changing the osg collada plugin build files (VC8 project file) link the
different names.

 

This is very unsatisfactory as I have to reset all the osg  stuff every time
cmake is run. I admit that the easiest way to do that is just to remove the
cmake files from the collada plugin directory.

 

But I can just about live with it.

 

Roger

 

  _____  

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Anders
Backman
Sent: 16 November 2007 17:46
To: OpenSceneGraph Users
Subject: [osg-users] Collada build again

 

Hi all.

I have a slight problem with the build of the collada plugin under windows.

The first is that its forced to be static, this I have reported earlier, so
there is a simple solution for that (the CMakeLIsts.txt is submitted to
Robert/osg-list/submission-list).

The other is that one have to select either debug/release version of the
library in cmakesetup.

This library is picked up and used for linking both release/debug version of
the dae plugin. 

This causes problems, as we are using the document created by the dae plugin
for reading physics from collada.

We are using debug and release libraries in our buildsystem to be able to
step through code etc... 

So what happens is that during the osg build, either debug OR release of
libcolladadom13 is selected.

Then we use libcolladadom13d.lib in our debug relases.
Because of how collada is constructed (global/static variable shared between
all instances of collada) it crasches if you mix debug/release. 

Ok, with all that said.
After investigating the cmakefiles of the dae plugin, I cant really make out
how to make it possible to use both debug as well as release when building
the plugin.

Currently the variable 

SET(TARGET_LIBRARIES_VARS COLLADA_LIBRARY)

is set, where COLLADA_LIBRARY Is the variable containing the full path to
the library file selected in cmakesetup.

Without some major refactoring, I dont see how to make it possible to use
the ordinary debug optimized procedure of linking to libraries.... 

Any ideas, thoughts?


-- 


________________________________________________________________
Anders Backman               Email:    [EMAIL PROTECTED]
HPC2N/VRlab                  Phone:    +46 (0)90-786 9936
Umea university              Cellular: +46 (0)70-392 64 67
S-901 87 UMEA SWEDEN         Fax:      +46 90-786 6126
                              http://www.cs.umu.se/~andersb 

_______________________________________________
osg-users mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Reply via email to