From: Daniel Laird <danieljlaird@hotmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Enabling Static builds
Date: Wed, 7 Feb 2007 09:00:29 -0800 (PST) [thread overview]
Message-ID: <8849503.post@talk.nabble.com> (raw)
I have been looking at a number of the packages in the system. Do people
think that -enable-static is a good idea as it seems to be used in a log of
package configures.
would a global enable-static option and enable-shared option be good idea?
This would mean that if you choose it it passes --enable-option to configure
else --disable-option this could be helpful for embedded systems
What do people think?
--
View this message in context: http://www.nabble.com/Enabling-Static-builds-tf3188244.html#a8849503
Sent from the BuildRoot mailing list archive at Nabble.com.
next reply other threads:[~2007-02-07 17:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-07 17:00 Daniel Laird [this message]
2007-02-07 17:19 ` [Buildroot] Enabling Static builds Bernhard Fischer
2007-02-07 18:15 ` Marc Lindahl
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=8849503.post@talk.nabble.com \
--to=danieljlaird@hotmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox