* libstdc++ static/shared linkage
@ 2002-09-16 9:34 Bill Jester
0 siblings, 0 replies; only message in thread
From: Bill Jester @ 2002-09-16 9:34 UTC (permalink / raw)
To: gcc-help
Is it possible to build shared C++ libraries using gcc 3.1 without
bringing any symbols in from libstdc++ but then link against the static
libstdc++ library at the final link step? We would prefer not to
distribute the gcc libs with our application so would like no external
dependencies on libgcc/libstdc++. If we build gcc with
--disable-shared, however, each .so we build becomes huge since it
brings so many symbols in from libstdc++.a.
If there is no way to do this, the only two options I see are linking
everything against the shared libstdc++.so and shipping it with the
application or linking everything against the static libstdc++.a and
living with the huge resulting .so's (which I can't imagine will speed
anything up at run-time). Is there any other way to achieve what we
want?
If you need any clarification/example code, please let me know.
Thanks in advance,
Bill
--
Bill Jester
Software Development Specialist
adapco
1516 E. Palm Valley Blvd.
Building B, Suite 1
Round Rock, Texas 78664
Phone: (512) 733-1070 x302
E-mail: jester@adapco.com
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2002-09-16 16:34 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-09-16 9:34 libstdc++ static/shared linkage Bill Jester
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).