Re: Building static

• Subject: Re: Building static
• From: "Justin C. Walker" <email@hidden>
• Date: Mon, 9 Dec 2002 10:17:49 -0800

On Fri, 6 Dec 2002, Kevin Van Vechten wrote:

On Friday, December 6, 2002, at 05:58 PM, Justin C. Walker wrote:

I want to build an app that is dependent only on the dylibs that "come
with" Mac OS X, so Joe Random can just download this thing and run it
on his system without having to worry about finding/building the other
libraries that it (the app) uses.

A noble pursuit. =)

I have this building fine, but for one library. That library (gmp)
comes in both .dylib and .a forms. How can I force it to use the .a
version? As it stands, the app seems to have a predilection for the
.dylib. Just to make life more interesting, one of the other (static)
libraries depends on gmp. Does this mean I have to rebuild that
library first, in some different way than I've done so far?

I assume you're linking with the -lgmp flag. I'm not sure how to force
-l to use the static library, however, specifying an absolute path to
the static library works. So try /path/to/libgmp.a instead of -lgmp.
I doubt you'll need to rebuild the first library.

Unfortunately specifying the full path links the library as an object
which will no doubt make your binary [much] larger than it needs to be.
There are two ways to ensure -lgmp uses the .a library
1) remove the .dylib form. Then the link must use the .a as found
2) specify -static -lgmp

• Prev by Date: Re: /Library/Extensions folder supported?
• Next by Date: Re: /Library/Extensions folder supported?
• Previous by thread: Re: Building static
• Next by thread: Reading linux ext2fs on OS X
• Index(es):
  • Date
  • Thread