> I'm not using windows for development (yet), so please take the
> following with a grain of salt.
> I believe we had this problem in the past and there are files in the
> source tree that explicitly instruct the linker that the symbols it is
> looking for are really present in the library even if it seemingly can
> not find them. It looks as if we have to add more symbols to those files
> (they are in e.g. Source/System/FieldContainer/lib.def.cl.net.sym).
> Unfortunately the format of these files seems to be different from what
> the linker prints in the error message, so I'm not sure what exactly has
> to be added - can someone with windows experience help out here, please?
>
> After having read MS's page on that error message
> (<http://msdn.microsoft.com/en-us/library/f6xx1b1z(vs.71).aspx>) I
> suspect that inlining might be the problem and the compiler does not
> properly honor the inline on the function definition, but insists on
> seeing it on the declaration.
> If I'm right a quick fix might be to add inline to the declaration of
> getValue and operator[] in OSGMField.h.
>
> Hope it helps,
> Carsten
Thanks for your reply!
I have downloaded the 26.06.08 daily build and the problem I have been facing
so far does not seem to exist anymore...
Anyway, thanks again for your interest!
Mark
_______________________________________________
Opensg-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-users
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Opensg-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-users
