From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] First Step in allowing Static / shared library choice
Date: Thu, 8 Feb 2007 18:23:18 +0100 [thread overview]
Message-ID: <20070208172318.GA8945@aon.at> (raw)
In-Reply-To: <8867285.post@talk.nabble.com>
On Thu, Feb 08, 2007 at 07:18:08AM -0800, Daniel Laird wrote:
>
>Following on from my question of 'how do we deal with shared and static
>builds"
>I enclose the following patch.
>This is for the top level Config.in
>It will appear under Build options
>this means that the variables BR2_STATIC_LIBS and BR2_SHARED_LIBS are
>available.
>
>Once this patch is in we can start to modify packages to use this
>information. (no packages modified yet)
Sounds good.
Can you please also add $(BR2_ENABLE_SHARED) rsp. $(BR2_ENABLE_STATIC)
variables (and the corresponding DISABLE) that get passed to
TARGET_CONFIGURE_OPTS (spelling?) to toolchain/Makefile.in or an
appropriate place?
TIA,
next prev parent reply other threads:[~2007-02-08 17:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-08 15:18 [Buildroot] First Step in allowing Static / shared library choice Daniel Laird
2007-02-08 17:23 ` Bernhard Fischer [this message]
2007-02-08 17:39 ` Daniel Laird
2007-02-08 17:43 ` Bernhard Fischer
2007-02-08 17:49 ` Bernhard Fischer
2007-02-09 9:59 ` Daniel Laird
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=20070208172318.GA8945@aon.at \
--to=rep.dot.nop@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.