Nobody has volunteered to provide static builds so far, though many people want to test them. It's really bad because it may delay the release - I don't think we can make the final release after less than a week of static prerelease testing. Anyone?
On Mon, 1 Nov 2004, bulia byak wrote:
Nobody has volunteered to provide static builds so far, though many people want to test them. It's really bad because it may delay the release - I don't think we can make the final release after less than a week of static prerelease testing. Anyone?
Is this for Linux? I could probably do some builds. Any clues? Is it just ./configure --disable-shared, or something?
Cheers
Carl
On Mon, Nov 01, 2004 at 02:11:31PM +0000, Carl Hetherington wrote:
Is it just ./configure --disable-shared, or something?
I believe that doesn't work. I believe that just controls whether to build shared libraries rather than whether to link against shared or static libs.
For the libraries where we use pkg-config, someone suggested changing one's .pc file to use the libfoo.a file instead of -lfoo.
For the libraries that are named explicitly in Makefile.am, you can similarly change -lfoo to /usr/lib/libfoo.a.
pjrm.
Peter Moulder wrote:
On Mon, Nov 01, 2004 at 02:11:31PM +0000, Carl Hetherington wrote:
Is it just ./configure --disable-shared, or something?
I believe that doesn't work. I believe that just controls whether to build shared libraries rather than whether to link against shared or static libs.
For the libraries where we use pkg-config, someone suggested changing one's .pc file to use the libfoo.a file instead of -lfoo.
For the libraries that are named explicitly in Makefile.am, you can similarly change -lfoo to /usr/lib/libfoo.a.
pjrm.
I think that will work. Also, if one builds libsigc++ gccpp, gtkmm, glibmm, etc from source, --enable-static is usually necessary. (and --disable-shared helps, too)
Bob
participants (4)
-
Bob Jamison -
bulia byak -
Carl Hetherington -
Peter Moulder