gEDA-dev: Building gEDA

[Peter Clifton]

On Fri, 2006-07-28 at 11:02 -0400, Stuart Brorson wrote:
> > Small issues with the build:: libgeda must be installed under /usr/
> > whatever before the rest will compile. This is a pain, and could
> > probably be improved.
> 
> Umm, actually it doesn't.  You just need to set the $LD_LIBRARY_PATH.
> If you just say "make", then the Makefile tells you what to do.
> Below find the spew from "make" which I get.  Note that I generally
> build in an arbitrary directory and install into /usr/local/geda.
> However, you can install anywhere.
> 
> Stuart

I've been doing that for all my local compiles. What I'm now trying to
do, is compile with a prefix of /usr/, but _install_ into a build root
somewhere else. 

Is it OK to set the LD_LIBRARY_PATH etc.. to "built_root/lib", then
finish compiling gschem, gattrib etc...?

If the build picks up libgeda's .pc file from the build-root, it will
get -L... -I... compile flags which point to /usr/... not the build root
IIRC.

For the moment, I have given up and just installed libgeda directly
in /usr/.. as well as my build-root directory. Whilst this would mess up
any existing libgeda on the system, this is only a sacrificial build
environment anyway.

Am I doing this in a stupid way?

As a side note, I was surprised to find that CVS is required gschem to
autogen.sh correctly.. If I'm building on a system without CVS, it can't
fetch it's "intl" directory. What exactly is it fetching at this point?

Peter