Re: [vrjuggler-devel] small bug fix: diff for cppdom-config

[Patrick H. <pa...@in...>]

On Fri, 2004-07-23 at 08:50 +0200, Raymond de Vries wrote:
> Hi,
>=20
> >>>Now I have another 1 which has to do with CppDOM: cppdom-config is not=
=20
> >>>found. Does anyone know how to handle this? As far as I can see I have=
=20
> >>>no cppdom-config...
> >>>     =20
> >>>
> >>You have found another bug.  It seems that the makefile for creating th=
e
> >>C++ dependency installation does not install cppdom-config.  You will
> >>probably have to download CppDOM 0.3.2 and build & install it yourself
> >>to get that script.  I have attached the version of the script that
> >>should have been included with the dependencies,
> >>   =20
> >>
> >
> >Okay, this time I actually remembered to attach the script, and I
> >included gmtl-config for good measure.  In looking at the script, I see
> >that there is a command-line option for telling the script to ignore its
> >preset prefix and use $CPPDOM_BASE_DIR.  It would be relatively easy to
> >change juggler/modules/vapor/configure.in so that it set
> >$CPPDOM_BASE_DIR artificially, thus eliminating the need for modifying
> >cppdom-config when the VR Juggler dependency tree is created.  gmtl-
> > =20
> >
> I send you a small patch in which I did it slightly different: instead=20
> of usng your hard-coded Juggler path, I just used $VJ_DEPS_DIR. Now=20
> there is no need for an extra env setting CPPDOM_BASE_DIR.

Well, this is fine for a local copy, but it isn't viable in the general
case.  Users of CppDOM by itself shouldn't be setting paths related to
VR Juggler.  Since cppdom-config offers some flexibility in what it uses
internally for its prefix, it is better for us to take advantage of it.
The change I made to juggler/modules/vapor/configure.in requires no
extra effort on the part of the user; the script takes care of setting
$CPPDOM_BASE_DIR temporarily.

At any rate, the changes I made to the VR Juggler build have propagated
to the anonymous CVS server, so you should do the following to get the
changes:

     1. Run 'cvs update' on at least juggler/external and juggler/
        modules/vapor
     2. Run autogen.sh in the top-level Juggler source tree.
     3. Run configure.pl again with the same arguments you used before.

I did a test where I built VR Juggler from scratch against a packaged
dependency tree, and it worked for me.  I am not 100% sure that some
local path did not sneak in, however, so if you have problems after
going through the above procedure, please let me know.

As far as the lib32 vs lib issue, I suggest that you rename the lib32
directory in the dependency tree to just plain "lib" or make a symbolic
link to the lib32 directory called "lib".  In retrospect, it was
probably a bad idea for us to install pre-compiled library binaries into
a directory that is not where they expect to be.  Not one of the third-
party dependencies that we package up for people actually uses the IRIX
lib32/lib64 naming convention, so it's probably not a good idea for us
to pretend that they do.

 -Patrick


--=20
Patrick L. Hartling                    | VP Engineering, Infiscape Corp.
PGP: http://tinyurl.com/2msw3          | http://www.infiscape.com/