On 17 Jul 2001 20:19:56 -0400, Brian S. Julin wrote:
>
> On 16 Jul 2001, Thayne Harbaugh wrote:
>
> > Has anyone tested this since I "fixed" it ?
>
> It compiled and installed. LibGGI still complained a bit after ./configure
> but I guess a warning there is ok, since anyone using this should know
> what they are doing.
What were the complaints?
> Would be nice if the demos would run against the
> uninstalled software, but that is probably not worth the effort needed to
> achieve.
This is because there isn't a mechanism for handling the config files
that are usually found in /etc/ggi - like libgii.conf and libggi.conf.
libgg doesn't know where to find the config files when they are in build
trees plus the files are built to point to the system directories and
not the build directories. It would be nice if libgg could use a
LIBGG_PATH environment variable to search for config files. The only
thing to add would be to write the config files one way when software is
built and another way when software is installed.
Seems very worth having if you care at all about testing both
compilation _and_ execution without installing over the top of your
stable software.
PS - I tested running out of compile trees:
All libgii and libggi files were uninstalled
libggi was built using --with-uninst-gii=DIR
libgii.conf and libggi.conf were put into /etc/ggi
.root and .include entries were fixed to point to build dirs and all
other entries were changed to point to their appropriate subdirectories
in the build trees.
Demos were run and all libraries (libgg.so, libgii.so, libggi.so plus
all dlopened libs) were automaticly found (libtool is so cool).
I really think this feature is worth adding - but not before the
release. Think of this: You want to run GGI 2.0 stable, but be able to
build and fully test GGI 2.1 development without clobbering your stable
install.
> --
> Brian
--
Thayne Harbaugh
