From: Mike Frysinger <vapier@gentoo.org>
To: buildroot@busybox.net
Subject: [Buildroot] prefer static libraries question
Date: Tue, 12 Apr 2011 18:36:54 -0400 [thread overview]
Message-ID: <201104121836.55644.vapier@gentoo.org> (raw)
In-Reply-To: <9AC3F0E75060224C8BBC5BA2DDC8853A1FA8E4DC@EXV1.corp.adtran.com>
On Tuesday, April 12, 2011 11:20:38 ANDY KENNEDY wrote:
> Yeah, well at the moment it isn't on my plate as I'm writing kernel
> code attempting to get a PHY up and running, so I'll get back to
> this later.
np. i was just trying to fill out some of your "unknowns".
> I will probably go forth with the mentality of "only
> do static" and attempt to make things work in a sensible manner.
might be better to rename or add a new option. then the build logic is clear:
if user *prefers* static linking, we'll still build/install shared libs, but
we'll generate static programs everywhere. if the user *only* wants static
builds, then we can skip the shared lib stuff entirely.
> Question: Where should I put the libs? I'm guessing that I should
> have all libs install to STAGING_DIR, but I want to make sure I'm
> doing the right thing.
i believe that is correct. staging is where all the generated stuff goes that
you need to link other packages against, but it isnt the target rootfs tree
which is used at runtime on the target hardware.
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20110412/9d3be647/attachment-0001.asc>
next prev parent reply other threads:[~2011-04-12 22:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-28 21:49 [Buildroot] prefer static libraries question ANDY KENNEDY
2011-04-12 6:48 ` Mike Frysinger
2011-04-12 15:20 ` ANDY KENNEDY
2011-04-12 22:36 ` Mike Frysinger [this message]
2011-04-22 13:25 ` Thomas Petazzoni
2011-05-14 9:38 ` Peter Korsgaard
2011-06-18 18:47 ` Mike Frysinger
2011-06-18 19:38 ` Bernhard Reutner-Fischer
2011-06-20 14:53 ` ANDY KENNEDY
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=201104121836.55644.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=buildroot@busybox.net \
/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