Very Computer

by **Michael Torri** » Tue, 21 Sep 1999 04:00:00

I'm trying to make a statically-linked program that uses GTK+. It seems
that my GTK libraries are all shared libraries, so when I do a GCC
-static, all the GTK functions come up as missing symbols. How do I get
a static executable out of the thing? Is there a way of getting a
static exe out of shared libraries, or do I have to have static versions
of the libraries as well? If so, is there a utility to convert a shared
library to a static one?

Thanks
Michael
caseih at hotmail dot com

by **Tom Leet** » Tue, 21 Sep 1999 04:00:00

> I'm trying to make a statically-linked program that uses GTK+. It seems
> that my GTK libraries are all shared libraries, so when I do a GCC
> -static, all the GTK functions come up as missing symbols. How do I get
> a static executable out of the thing? Is there a way of getting a
> static exe out of shared libraries, or do I have to have static versions
> of the libraries as well? If so, is there a utility to convert a shared
> library to a static one?

If you use RPMs, install the glib-devel gtk+-devel packages.

If tarballs, do:
$ ./configure --help
to discover the magic words for the build. It's usually
'--enable-static'.

Tom

by **Michael Torri** » Wed, 22 Sep 1999 04:00:00

When I build libraries, I always get a .so file, which is a shared library,
and a .a file, which I believe is generated by ar, and is simply an archive
of the .o files, is that right? Anyway, I'm just trying to understand
libraries and library creation.

Michael
caseih at hotmail dot com

> > I'm trying to make a statically-linked program that uses GTK+. It seems
> > that my GTK libraries are all shared libraries, so when I do a GCC
> > -static, all the GTK functions come up as missing symbols. How do I get
> > a static executable out of the thing? Is there a way of getting a
> > static exe out of shared libraries, or do I have to have static versions
> > of the libraries as well? If so, is there a utility to convert a shared
> > library to a static one?

> If you use RPMs, install the glib-devel gtk+-devel packages.

> If tarballs, do:
> $ ./configure --help
> to discover the magic words for the build. It's usually
> '--enable-static'.

> Tom

by **Elmo Reci** » Wed, 22 Sep 1999 04:00:00

> When I build libraries, I always get a .so file, which is a shared library,
> and a .a file, which I believe is generated by ar, and is simply an archive
> of the .o files, is that right? Anyway, I'm just trying to understand
> libraries and library creation.

.a files are the static libraries you need.

Elmo Recio
Homepage: http://polywog.navpoint.com/~elmo
Sociology/Philosophy student at Drexel Univ

"Hilary went to her death
because she couldnt think of anything to say
Everybody thought that she was boring
So they never listened anyway.
Nobody was really saying anything of interest
She fell asleep."
-Belle And Sebastian (If You're Feeling Sinister)

Very Computer

making statically-linked executable

making statically-linked executable

making statically-linked executable

making statically-linked executable

making statically-linked executable