Hello Andreas,
Andreas Halm wrote:
>> Gerrit gave the details, but just to make it clear: we *strongly* warn
>> against
>> copy-n-pasting to generate your FCs. Use the .fcd mechanism! That's is
>> a much,
>> much easier way, as there are just too many side dependencies that you
>> do not
>> want to mess with (like the list above), especially if things need to
>> be
>> extended or changed on the inside.
>
> One more thing about that. I tried to setup one easy fcd file and ran it
> through the fcd2code script, but the generated files contain lines like
>
> #include "OpenSG/OSGConfig.h"
> #include "OpenSG/OSGBaseTypes.h"
> #include "OpenSG/OSGNodeCore.h" // Parent
> #include "OpenSG/OSGInt32Fields.h" // Sstype type
> #include "OpenSG/OSGStringFields.h" // Ssid type
>
> How is this supposed to work? There is no OpenSG include path in the trunk
> and cmake does not generate one either.
your container is generated to be outside of the system (attribute
"systemcomponent" is false in the .fcd) and thus the includes are
written to work with an installed OpenSG. If you drop your containers
into the OpenSG tree they are part of OpenSG and "systemcomponent" needs
to be true. I'll clarify the fcd2code page.
Cheers,
Carsten
------------------------------------------------------------------------------
Are you an open source citizen? Join us for the Open Source Bridge conference!
Portland, OR, June 17-19. Two days of sessions, one day of unconference: $250.
Need another reason to go? 24-hour hacker lounge. Register today!
http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org
_______________________________________________
Opensg-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-users
