Re: gEDA-user: Some (newbie?) problems GSpiceUI, PCB

[sdb@xxxxxxxxxx (Stuart Brorson)]

cd into the gspiceui source directory.  Then change the aclocal.m4 you
find in there (assuming it exists).  Then do "sh autogen.sh"
(assuming the file autogen.sh exists in the gspiceui directory).  Then
do "./configure && make && make install".

If aclocal.m4 or autogen.sh don't exist in the source directory, or
you don't have the autotools installed, then you're SOL, at least for
now ... 

Stuart


> 
> Op zo, 12-02-2006 te 09:29 -0500, schreef Stuart Brorson:
> > > P.S.: Did someone find a solution to the GSpiceUI build problem, 
> > > also an "undefined reference": 
> > > "undefined reference to `pango_x_get_context'"
> 
> Perhaps I should mention in advance that I tried to build the whole gEDA
> suite with the installer script from the CD ISO image. 
> Also, I'm not too proficient compiling applications, other than
> executing ./configure, make, and make install from a single source tree.
> 
> > A Google search turns up this:
> > 
> > add pango setting to aclocal.m4:
> > 
> >       WX_LIBS_ONLY="`$WX_CONFIG_WITH_ARGS --libs --unicode=no`"
> >       PANGO_LIBS="`pkg-config --libs pangox`"
> >       WX_LIBS="$PANGO_LIBS $WX_LIBS_ONLY "
> 
> In the geda-sources directory, I found no less than 18 aclocal.m4 files,
> all different - yet none of these seem to be directly related to
> gspiceui. Which one should I edit? Perhaps this one:
> geda-sources/gedagaf/geda-20060123/aclocal.m4?
> 
> > Indeed, I seem to recall that if you configure with the flag
> > --unicode=no, then things work.   But I could be wrong.  Give it a try
> > & let us know.  
> 
> Where should I invoke ./configure (and make, and make install) for
> building gspiceui? There's no configure file anywhere in the tree under
> gedas-sources/gspiceui/.
> 
> Or is there a way to manually invoke the installer script for the
> GSpiceUI source tree only, without having to sit through the  build of
> all applications?
> 
> The INSTALL file suggests to manually build anything that fails to build
> & install automatically, but nowhere is explained *how* one should
> manually build any given application, in the same way the installer
> script does it (so that the final application ends up in the
> geda-install directory).
> 
> 
> My apologies if these seem like beginner's questions to you, but I seem
> to be missing a link somewhere between what the automatic installer does
> and a subsequent manual install with a tweaked configuration. Also, I'm
> more of an electronics expert than a software guru ...
> 
> For all the rest, I'm quite impressed with everything, my compliments
> with an already very nice and useful electronics software suite  :-)
> 
> 
> Thanks again, with best regards,
> 
> Richard Rasker
> 
> 
>