Annoying build system problems

[David Faure]

On Friday 18 February 2005 19:04, Stephan Kulow wrote:
> On Friday 18 February 2005 17:43, Hans Meine wrote:
> 
> > I wonder if this is intended.  Applicable fixes that come to my mind right
> > now would include making "prepend-path=true" the default, or (seems cleaner
> > to me) to change the list of paths in the calls to KDE_FIND_PATH to be
> > either empty or only include  [${prefix}/bin ${exec_prefix}/bin].  (Both
> > solutions assume that paths like /usr/bin are in $PATH anyhow, which is
> > reasonable IMHO.)  Wouldn't this make sense?
> >
> I fixed it for quite some already and wonder myself why we did this strange
> prepend-path=false default. But I'm true afraid to change that now. So better
> fix the missing places.

Because I, too, was afraid to make a change that would affect every KDE_FIND_PATH
call, when I added the "prepend" option in order to find the right kde-config
(acinclude.m4.in 2.445). But of course I see no reason why path shouldn't be prepended
in all cases.

-- 
David Faure, faure at kde.org, sponsored by Trolltech to work on KDE,
Konqueror (http://www.konqueror.org), and KOffice (http://www.koffice.org).