Hello Aron,
Aron Bierbaum wrote:
> When trying to compile OpenSG 2.0 on windows I get the following
> error. It appears that these types are getting exported the same way
> as everything else, but I could be missing something. Does anyone have
> any ideas how to fix it? This is using the default osb loader,
> enable_new_osb_io=False.
ah well, I took the lazy road with that configuration option, the new
code is always compiled and linked, but only used if enable_new_osb_io=yes.
Gerrit committed r598 to fix unresolved symbols on win (thanks Gerrit!).
I think that should fix the problem you see.
Carsten
PS: Does someone know a way to make a linux system equally sensitive to
not explicitly/properly exported symbols as windows? That would allow me
to avoid this type of breakage in the future ;)
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Opensg-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-users
