Re: FOO_LIBS

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Gavin Smith writes:
> On Mon, Sep 30, 2013 at 8:56 AM, Harlan Stenn <stenn@xxxxxxx> wrote:
> > I've got a situation where I want to track specific libraries that are
> > needed for building specific programs.  Sometimes this is for things
> > like openssl and sometimes it's network stuf or thread stuff, where I
> > know which programs need it and which ones don't.
> >
> > Originally I let configure put all of the libraries in the LIBS
> > variable, but I got a lot of pushback from folks with embedded systems
> > and similar targets where the extra libraries were taking up too much
> > space.
> >
> > So I started putting specific libraries in different variables so I
> > could control when they get linked to an executable.
>>
> Could you use a "--with" flag using AC_ARG_WITH and run AC_CHECK_LIB
> only if the library was enabled?

That's not the problem.

The problem is that:

- we think we cannot put all libraries in LIBS.  Therefore...

- we put certain libraries in FOO_LIBS which is then not "seen" by the
  rest of the "configure" process, so any functions that we search for
  that could/should be found in FOO_LIBS are not found because configure
  searches only LIBS.

So I think I need a way to tell AC_CHECK_FUNCS that it should check LIBS
and FOO_LIBS and any other "separated" library sets that I come up
with.

H

_______________________________________________
Autoconf mailing list
Autoconf@xxxxxxx
https://lists.gnu.org/mailman/listinfo/autoconf




[Index of Archives]     [GCC Help]     [Kernel Discussion]     [RPM Discussion]     [Red Hat Development]     [Yosemite News]     [Linux USB]     [Samba]

  Powered by Linux