Hi Jan, On Sun, Jan 25, 2009 at 12:15 PM, Jan Ciger <[email protected]> wrote: > Do you mean adding 64 suffix to the lib name and stuffing all of them > into /usr/local/lib instead? I think that is a really poor idea - it > breaks the standard that the libraries for different architectures are > in different places and forces complicated library name mangling logic > on buildsystem writers if they have to support both 32 and 64 bit systems.
Yes this is what I mean, and I agree /usr/local/lib64 "should" be where such 64bit libraries should be installed. Almost all of other 3rd party libraries that I've built on my machine install into /usr/local/lib rather than /usr/local/lib64, I presume out of not knowing/caring about the /usr/local/lib64 convention for 64 bit libs, or it's a pragmatic decision based on problems with Linux distro's not including /usr/local/lib64 in there default search path. > That distros do not include /usr/local/lib64 in their search path > shouldn't be your concern and it shouldn't be worked around by a kludge > like this. Making the OSG compile, install and run out of the box with mods very much my concern. Linux is one of most commonly used platforms so making things as seamless as possible is important. If this means being pragmatic about things then I'm prepared to be. > A better solution is to make the cmake build produce a set of > packages for standard installation - e.g. rpms or debs which are the > most common format. Both of these formats allow running post-install > scripts, permitting modification of e.g. /etc/ld.so.conf or better > dropping a file to /etc/ld.so.conf.d that will add your chosen directory > to the search path. The completely best solution is to have the package > install itself directly under the /usr hierarchy - the /usr/lib64 dir is > for sure in the search path and installing there is fine, because the > package allows easy de-installation and upgrade. This does sound a possible solution, but.. it would require building of the packages and then installing, which is a two stage process rather than a single stage. It also requires CPack to support rpms and debians to be mature enough to do this. Perhaps another solution would be to have Cmake's install scripts add /usr/local/lib64 (or whatever the path is) to /etc/ld.so.conf automatically if it's not already there. Robert. Robert. _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
