Hi,
Is the usage of the build.info files documented somewhere?
I'm having problem compiling OSGGLUTWindow win NVPerfSDK because
testOcclusionCulling needs NVPerfSDK (but OSGGLUTWindow doesn't).
I've added this to GLUTWindow's build.info file:
nvperfsdk_option = opts.GetOption("NVPerfSDK")
if nvperfsdk_option.isAvailable():
libs.append(nvperfsdk_option.library)
cpppath.append(nvperfsdk_option.incDir)
libpath.append(nvperfsdk_option.libDir)
which builds ok but it connects links all exe/libs that depends on
glutwindow with nvperfsdk, and there's only one test-exe that needs it,
so I feel it borders between overkill and plain wrong. ;)
Setting test_[cpp|lib]path works, but adding the lib to osg_test_libs
doesn't give the right results, AFAICS there's no plain 'test_libs'
variable. (It borked when I tried to use that.)
Just looking for directions.
Cheers,
/Marcus
-------------------------------------------------------------------------
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
