[Top][All Lists]

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

Re: Building all static

From: Denis Vlasenko
Subject: Re: Building all static
Date: Tue, 2 Nov 2004 08:57:13 +0200
User-agent: KMail/1.5.4

On Tuesday 02 November 2004 06:39, Bill Moseley wrote:
> Sorry for the cross post, not sure which is the correct list.
> My project builds a library and then builds a binary and links to that
> library.  Someone has asked how to build a completely static binary.
> I have been through this before.  I have a post[1] from May where I
> discuss building our project statically.
> This has come up again and I'm wondering if I'm giving correct
> information on that post.
> I have a few questions:
> 1) The configure option --disable-shared works at linking our binary
> with our library statically, but still links the binary dynamically
> with other libraries.  I assume that's correct behavior.  What does
> the --enable-static option do (or suppose to do)?  It seems to have no
> effect when I use it.
> 2) Is there a "standard" way to run configure that should build a
> completely static binary?
> I know there's an -all-static flag for libtool.  Do I need to setup my
> special to allow building static via configure?

Does CFLAGS="-static" help?

reply via email to

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