public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Bo Do" <bodo@flygp.se>
To: <gcc-help@gcc.gnu.org>
Subject: How handle static libraries?
Date: Mon, 17 Nov 2003 09:09:00 -0000	[thread overview]
Message-ID: <000801c3aceb$a6d0ce20$2bfb0ec2@flygp.se> (raw)

Hey all,

I've written some (static) libraries I use pretty often. Lets call them A, B, C.....
When I want to use one, lets say B, I simply include B.h and link in B in my program.

My question is, I have a library C which needs/uses library A. Can I compile/archive
C in some way so that when I want to use C in a program, I just include C.h and link in C?
What I have to do now is to also link A to my program. But this look wierd (to me!)
because my program doesn't use A.

Thanks for any tip,
/Bo

             reply	other threads:[~2003-11-17  9:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-17  9:09 Bo Do [this message]
2003-11-17 23:18 ` Erik Christiansen
2003-11-18  8:17   ` Bo Do
2003-11-18 18:20 lrtaylor
2003-11-19  8:22 ` Bo Do

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='000801c3aceb$a6d0ce20$2bfb0ec2@flygp.se' \
    --to=bodo@flygp.se \
    --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).