[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: gEDA-user: building 20030901 geda released
- To: geda-user@seul.org
- Subject: Re: gEDA-user: building 20030901 geda released
- From: Ales Hvezda <ahvezda@seul.org>
- Date: Thu, 02 Oct 2003 22:40:22 -0400
- Delivered-to: archiver@seul.org
- Delivered-to: geda-user-outgoing@seul.org
- Delivered-to: geda-user@seul.org
- Delivery-date: Thu, 02 Oct 2003 22:40:36 -0400
- In-reply-to: Your message of "Mon, 08 Sep 2003 08:42:09 +0200." <91D80A67-E1C7-11D7-9D6A-003065D0A7C0@klebsch.de> ------
- Reply-to: geda-user@seul.org
- Sender: owner-geda-user@seul.org
Hi Mario,
[snip]
>> libstroke is a non-gEDA/gaf specific library, so I don't search
>> for it in any user accessable directories. In the ./configure script
>> I assume that it is installed as a system library. Perhaps this is a
>> bug.
>
>It depends on how you define 'system library'. IMHO you should not
>assume, that it is installed in /lib or /usr/lib and give the user an
>option to specify additional locations, where to look for this library.
You are, of course, correct. The ./configure scripts should
have a mechanism to find libs in non-standard places. All the other
librarys either use a *config script or pkg-config.
[snip]
>> As you discovered this is the right way to get libraries into
>> the search path for the ./configure script.
>
>Although this may work with every autoconfigure generates ./configure,
>it iseems a bit ncommon to me, having build autoconfig controlled
>projects for almost a decade.
Foo. I couldn't bluff my way out of this one. :) On
that note, I have added a --with-stroke=directory command line flag
to ./configure so that now every library can be install in $prefix and
nothing needs to be installed in any system library.
-Ales