[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [PATCH] neon.m4

From: Garrett Rooney <rooneg_at_electricjellyfish.net>
Date: 2002-03-11 16:13:01 CET

On Sun, Mar 10, 2002 at 08:24:41PM -0500, Ben Collins wrote:
> On Sun, Mar 10, 2002 at 04:06:55PM -0800, Greg Stein wrote:
> > On Sun, Mar 10, 2002 at 06:41:43PM -0500, Garrett Rooney wrote:
> > >...
> > > I don't feet stronly about this one way or the other (I mean hell,
> > > it's just one little text file), but others seem to, and it doesn't
> > > seem like we lose anything by just using -lneon, and we gain the
> > > ability to be able to build when that file (for whatever reason) is
> > > not installed.
> >
> > .la files provide further dependencies for the application. Thus, we *do*
> > lose functionality by avoiding them.
> >
> > Instead, the patch should test for the .la. If it is present, then use it.
> > Otherwise, set up a -L and -l pair for linking.
>
> Actually, you don't need to special handle this. Libtool does it for
> you. Passing -lneon to a libtool link line is all you need to do
> (libtool will search for the .la itself).
>
> (from libtool)
>
> for searchdir in $newlib_search_path $lib_search_path $sys_lib_search_path $shlib_search_path; do
> # Search the libtool library
> lib="$searchdir/lib${name}.la"
> if test -f "$lib"; then
> found=yes
> break
> fi
> done

well, in light of this revelation, does anyone have a problem with me
checking this change in?

-garrett

-- 
garrett rooney                     Unix was not designed to stop you from 
rooneg@electricjellyfish.net       doing stupid things, because that would  
http://electricjellyfish.net/      stop you from doing clever things.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Mar 11 16:21:57 2002

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.