Hi Robert,
El Viernes 23 Enero 2009ES 16:54:56 Robert Osfield escribió:
> I'm just reviewing these changes. I'm curious to how the existing
> (and modified by you) openscenegraph.pc/openthread.pc are used as
> input, and where the output file goes - is it simply built on install?
> I was expecting something like a openscenegraph.pc.in.
Existing *pc files were provided, but until now they weren't being populated
with the build actual installation values. I simply didn't rename them
because they weren't used so far (not being installed anywhere) so I thought
I could save the mess of having four files, when two of them aren't used in
fact. Although CMake doesn't require them to have any specific extension, I
can rename them to .pc.in if this makes more evident their use for others.
The filled files are generated at configure time, even before build time. I
chose to generate them in the binary tree at the same relative path that they
have on the source tree (packaging/pkgconfig).
When OSG is installed, those existing files of the binary tree are installed
(copied) to ${prefix}/lib${postfix}/pkgconfig, which is in the default path
for pkg-config according its manual (libdir/pkgconfig:datadir/pkgconfig)
> With the introduction of the CMake vars in the openscenegraph.pc it
> does strike me that it'd be logical to handle the version numbers this
> way as well as the install paths.
Good catch. It should be a matter of changing the version number with
@OPENSCENEGRAPH_VERSION@ and @openthreads_vers...@. However now I realize
that it would be better to populate openthreads.pc[.in] from
src/OpenThreads/CMakeLists.txt since OPENTHREADS_VERSION is only available
from there and is more coherent with respect to OT.
I will resubmit the files in short.
Regards,
Alberto
_______________________________________________
osg-submissions mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-submissions-openscenegraph.org
