Andreas Beck wrote:
>
> > What I did, is to allow for a separate build directory, from which you
> > $call Berlin/configure, to set up a *local* build tree (Makefiles,
> > $generated headers, etc.),
>
> This does work with the GGI libs. Look at the buildall script. It does
> exactly this.
yeah, I know it builds in a separate directory. But doesn't it require
one part to be installed before the next can be linked ?
> > This means that, in order to run, I don't want to install anything.
> > Instead, I want to run with the binaries/libs/modules/resources in the
> > local environment.
>
> This is impossible due to the dynamic nature of LibGGI (the configfiles
> would need considerable tweaking as would the whole config reading stuff in
> order to find everything in the build tree which has a somewhat other layout
> than an installed version), but it is easily possible to set $prefix to
> something like $HOME/ggitest/installed and install there.
hmm, that would probably improve things quite considerably. I know what you
mean, locating the resources (modules, font files, etc.) is tricky. What I
did, is to provide a resource file that contains paths. This file is provided
to the berlin server at run time, so you can just generate one (with configure)
that is suitable for the temporary environment.
> I've done that on a couple of machines on which I am not root. No problem.
fine. You may write down your experience such that this could be added to the
INSTALL file (or a building FAQ, or whatever)
> > It appears that this is currently not possible with GGI. This is a problem
> > even for less demanding contexts, such as when I have a GGI version
> > installed, and I want to cvs checkout a new (unstable) version, and test
> > it, before I decide whether I want to install it.
>
> Should work. Please recheck, if the existing functionality satisfies your
> needs.
I'll do. Thanks for the tip.
