[Top][All Lists]

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

Re: configure option naming convention

From: Ralf Wildenhues
Subject: Re: configure option naming convention
Date: Fri, 16 Sep 2005 17:40:24 +0200
User-agent: Mutt/1.4.1i

Hi Lars,

* Lars J. Aas wrote on Fri, Sep 16, 2005 at 04:48:36PM CEST:
> I'm wondering if there is a convention already for this or not.
> I am linking static libraries on windows (msvc++).  Not involving
> libtool or anything ready-made from autoconf/automake for that matter.
> Anyways, I can either just ball together just the object files for
> the library, or I can link the archive and pull in external
> dependencies at the same time.  Doing the latter, I don't need to
> do it when I link the static library into the executable.

Not to hijack your question, but: how do you do this?

If the semantics of doing this are compatible with Libtool library
dependencies, we could make use of this in our upcoming MSVC support..

> So what I'm looking for is an option name for letting the
> configurer specify when to use delayed linking of other static
> libraries, and to be able to do it on a library-for-library basis.
> Anybody set up options for anything like this before, and if so,
> how did you name them (and access the info inside the configure script
> in case there's already a system for it)?

Can't help you much there, sorry.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]