Re: gEDA-user: Building from sources

[sdb@xxxxxxxxxx (Stuart Brorson)]

> Thanks, Stuart.   Unfortunately, that did not work.
> 
> BTW, I was following the directions on Ales' page:  
> http://geda.seul.org/developer.html
> 
> To build the CVS version of gEDA/gaf, follow these instructions:
> 
>    1. You must have the following packages installed:
> 
>           * automake 1.7.x
>           * autoconf 2.57
>           * libtool 1.4.x
>           * pkg-config >= 0.15.x
>           * gettext 0.12.1
>           * guile 1.6.x
>           * gtk+ 1.2.x or 2.2.x
>           * LaTeX current
>           * latex2html current
>           * groff current
> 
>       It is pretty important to have all of the above programs (especially 
> automake, autoconf, libtool, gtk, and guile) installed in the same prefix 
> (like /usr or /usr/local). If you do not have them all installed in the same 
> prefix, then building and installing gEDA/gaf is much harder.
> 
>    2. You also need the various required packages listed on the download web 
> page. Mainly, glib/gtk and guile.
> 
>    3. Edit the toplevel Makefile to set the prefix to something other than the 
> default $HOME/geda if you so desire.
> 
>    4. Type: make and set all the required environment variables (PATH, 
> LD_LIBRARY_PATH, and PKG_CONFIG_PATH)
> 
>    5. And finally type: make install
> 
>    6. After this make finishes with NO errors, you should have a working 
> gEDA/gaf CVS build.


Well, the documentation needs updating then.  What you download from
CVS is the developer's package, and you need to run the autotools to
build configure.  The CVS distribution doesn't have configure built
yet.  The build proceeds like this:

1.  make reconfig  =>  this runs autogen in every directory in a
particular order. 

2.  make config  => this runs ./configure in every directory.

3.  make install  =>  this does "make && make install" every
directory.  The order in which you build the various packages is
important.  That's why Ales created a top level Makefile to manage the
process.  I belive the symbol files are created & installed first,
then libgeda.  Afterwards, gschem and gnetlist may be built.

> Just typing 'make' as in step four just gives you the list of targets.  Maybe 
> step four can be updated.
> 
> Stuart, when I ran 'make reconfig' everything was fine.  But 'make config' 
> errored out: 
> 
> checking for libgeda >= 20060123... Package libgeda was not found in the 
> pkg-config search path.
> Perhaps you should add the directory containing `libgeda.pc'
> to the PKG_CONFIG_PATH environment variable
> No package 'libgeda' found
> configure: error: Cannot find libgeda (or libgeda.pc), please install libgeda
> make: *** [gschem_config] Error 1
> 
> Which seems strange that it wants me to install the thing I am trying to 
> build.

Check your PKG_CONFIG_PATH variable.  Verify that it points to a
directory holding the file libgeda.pc. 

Also verify that you don't have an older version of libgeda (and
libgeda.pc) hangning around in the PKG_CONFIG_PATH before the new
libgeda.pc.  A common problem is that your PKG_CONFIG_PATH points to
the wrong, obsolete libgeda.pc.  That's one reason I always recommend
that you delete your old gEDA installation before trying to build a
new one.  Or at least move the directory it lives in off of any search
path.  

Another thought:  Do you have pkg-config installed?  What version?

Finally, if all this fails, nuke your source directory, re-download
geda-dev from CVS, and try again, starting from "make reconfig".  Make
sure your PKG_CONFIG_PATH is clean before trying again.

Stuart