Hi,
On Fri, 2009-09-11 at 13:28 +0200, Johannes Brunen wrote:
> Hi,
>
> sorry but I did make some mistakes in my last mail that I have to correct:
>
> "Johannes Brunen" <[email protected]> schrieb
> im Newsbeitrag news:[email protected]...
> >
> > What I have generally in mind is to collect my extensions of OpenSG 2.0 in
> > a separate library controlled by the OpenSG cmake project.
>
> should be "by the OpenSG cmake build system"; only to be clear.
>
just a small comment, that is already possible in the following way:
add your libname to OSG_EXTRA_EXTERNAL_MOLDULES, eg.
SET(OSG_EXTRA_EXTERNAL_MODULES OSGMyLib)
after the configure run add you will have two new variables:
OSGBUILD_OSGMyLib and OSG_OSGMyLib_SOURCE_DIR
OSG_OSGMyLib_SOURCE_DIR should point to the directory with a
similar setup as all OpenSG libs, e.g a CMakeLists.txt that
includes the CMakeLists.Lib.OSGMyLib.txt. This directory does
not have to live in the OpenSG source tree.
The CMakeLists.Lib.OSGMyLib.txt is just a normal cmake file as
for every other OpenSG lib, e.g. you can copy one from the
OpenSG source tree and start from there.
kind regards,
gerrit
PS: Partially you can actually also build the external lib
outside OpenSG as its own project. But that is work in
progress.
PPS: Unfortunately IIRC there isn't an example right now.
But I want to reorganize my try so that the bigger
blocks move into an external lib/project.
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Opensg-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-users
