All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Laird <danieljlaird@hotmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] First Step in allowing Static / shared library choice
Date: Thu, 8 Feb 2007 07:18:08 -0800 (PST)	[thread overview]
Message-ID: <8867285.post@talk.nabble.com> (raw)


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)

I hope this can get into the mainline without to much difficulty

Cheers
Dan

--- Config.in.orig	2007-02-08 15:08:18.000000000 +0000
+++ Config.in	2007-02-08 15:11:24.000000000 +0000
@@ -361,6 +361,20 @@
 
 	  WARNING: This is highly experimental at the moment.
 
+config BR2_STATIC_LIBS
+	bool "Build static libs for target"
+	default n
+	help
+	    This option when selected will try and build packages with static
libraries.
+	    This will increase code size and is not recommended for embedded
systems.
+
+config BR2_SHARED_LIBS
+	bool "Build shared libs for target"
+	default y
+	help
+	    This option when selected will try and build packages as shared
libraries.
+	    This will increase loading time but minimise size.
+
 
 endmenu
-- 
View this message in context: http://www.nabble.com/First-Step-in-allowing-Static---shared-library-choice-tf3193891.html#a8867285
Sent from the BuildRoot mailing list archive at Nabble.com.

             reply	other threads:[~2007-02-08 15:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-08 15:18 Daniel Laird [this message]
2007-02-08 17:23 ` [Buildroot] First Step in allowing Static / shared library choice Bernhard Fischer
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=8867285.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 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.