Hi,
I intend to come up with a scheme for where we install files and some
infrastructure that should help users getting started with OpenSG (at
least on linux systems).
Unfortunately the wiki seems to be down right now, so I could not read
up on what was already discussed
(<http://opensg.vrsource.org/trac/wiki/Dev/PluginsPathes>). I'll just
list what I've come up with so far and hope for comments ;)
For prebuilt RPMs <prefix> := /usr/local
osg-config
<prefix>/bin
debug libs
<prefix>/lib/OpenSG/dbg
optimized libs
<prefix>/lib/OpenSG/opt
symbolic links in
<prefix>/lib/ to the libs in <prefix>/lib/OpenSG/opt
headers
<prefix>/include/OpenSG
doxygen documentation
<prefix>/share/OpenSG/doc
examples (source+binary)
<prefix>/share/OpenSG/examples
tutorials (source+binary)
<prefix>/share/OpenSG/tutorials
The examples and tutorials folders will contain an SConscript that
allows building binaries from the sources.
As for the RPMs I would like to build three:
OpenSG contains optimized libs and osg-config, depends on the
image libs (png, jpeg, etc).
OpenSG-dev contains debug libs, headers, examples and tuts depends
on OpenSG, scons, devel tools
OpenSG-doc contains the documentation, no dependency
Since I have not built RPMs before, there are some questions:
- are the package names (at least those for gcc, python, scons,...)
standardized between distributions ? In other words, does it make sense
to have dependencies in a non-distribution specific package ?
- can you recommend a guide on building RPMs (I haven't searched very
hard for one yet).
Comments ?
Thanks,
Carsten
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Opensg-core mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-core
