[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: configure option naming convention
From: |
Lars J. Aas |
Subject: |
Re: configure option naming convention |
Date: |
Mon, 19 Sep 2005 12:07:46 +0200 |
User-agent: |
Mutt/1.5.6i |
Ralf Wildenhues <address@hidden> wrote:
: 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?
I've attached a small demo archive. It's set up for Microsoft Visual
Studio .NET 2003, but I believe just changing the libpath path should
be enough to use it with Visual Studio 6.0. However, it looks like
I might have been confused about what happens when one static library
includes another static library on the link line. For some reason
I thought it only pulled in the code that was used from the target
library, but now I believe the whole library is just added to the
static library so it's essentially both static libraries as one.
Anyways, I will still need to do the above - bundle additional static
libraries into the static library I am building, and I'll need to find
an option name for it...
Lars J
linkdemo.tar.gz
Description: application/tar-gz