From: Eljay Love-Jensen <eljay@adobe.com>
To: "Conklin, Larry" <Larry.Conklin@wiltel.com>, gcc-help@gcc.gnu.org
Subject: Re: static vs. dynamic libraries
Date: Tue, 11 May 2004 16:18:00 -0000 [thread overview]
Message-ID: <6.0.3.0.2.20040511110839.0202eec8@iplan-mn.corp.adobe.com> (raw)
In-Reply-To: <CFEF094FC6A7394EB95D5F7DE5421A640246C7B7@EXCHANGE2.ad.wcg.com>
Hi Larry,
This is a VERY platform (OS + GCC version) sensitive way to solve the
problem, as a target using GNU Make (I presume you know where the tabs go):
myfoo : foo.cpp
$(CXX) -o $@ $^ \
-nodefaultlibs \
-Wl,-Bstatic \
$(shell $(CXX) -print-file-name=libstdc++.a) \
$(shell $(CXX) -print-file-name=libgcc.a) \
$(shell $(CXX) -print-file-name=libgcc_eh.a) \
-Wl,-Bdynamic \
-lpthread -lc -lm -ldl
CAVEAT: Use with caution! This may work on, say, Solaris, and be
completely wrong for, say, AIX or Linux. And the libraries may be correct
for GCC 3.2, and wrong for GCC 3.3. Your mileage may vary.
HTH,
--Eljay
prev parent reply other threads:[~2004-05-11 16:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-11 16:05 Conklin, Larry
2004-05-11 16:18 ` Eljay Love-Jensen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6.0.3.0.2.20040511110839.0202eec8@iplan-mn.corp.adobe.com \
--to=eljay@adobe.com \
--cc=Larry.Conklin@wiltel.com \
--cc=gcc-help@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).