Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Jack Mitchell <ml@communistcode.co.uk>
To: openembedded-core@lists.openembedded.org
Subject: Re: static busybox?
Date: Tue, 31 Jul 2012 21:02:53 +0100	[thread overview]
Message-ID: <501839ED.4050004@communistcode.co.uk> (raw)
In-Reply-To: <50183924.8010309@windriver.com>

On 31/07/2012 20:59, Mark Hatle wrote:
> On 7/31/12 1:14 PM, Stuart Yoder wrote:
>> We are doing some work with LXC (containers) and one of the templates
>> is for busybox.  For LXC, the busybox package needs to be built 
>> statically and
>> there is a config option for this.
>>
>> A couple possible approaches:
>>
>>     -create a new 'busybox_static' recipe that the lxc package
>>      depends on that turns on the needed build options. Pretty
>>      straightforward, but now there are 2 variants of the busybox
>>      package.
>>
>>     -somehow propagate some configuration options through to
>>      the standard busybox recipe so it turns on the config
>>      option to build things statically.   Not sure how to
>>      do this, and seems like it could get pretty messy.
>>
>> Any thoughts?
>
> We've been talking about this as well..  I'm currently of the opinion 
> that the kernel's config fragement processing be added to busybox.  
> This way someone can simply add a configuration fragment via a 
> bbappend, or other approach and it'll pick it up.   That same can be 
> used to specify how to enable other optional pieces of busybox.

I like this, Busybox is one of the more complex recipes and a way to add 
and subtract config options without keeping your own copy in sync would 
be nice.

Regards,
Jack.

>
> --Mark
>
>> Thanks,
>> Stuart Yoder
>>
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>>
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core




  reply	other threads:[~2012-07-31 20:14 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-31 18:14 static busybox? Stuart Yoder
2012-07-31 19:36 ` McClintock Matthew-B29882
2012-07-31 20:01   ` Mark Hatle
2012-08-01 16:48     ` Darren Hart
2012-07-31 19:59 ` Mark Hatle
2012-07-31 20:02   ` Jack Mitchell [this message]
2012-07-31 20:07   ` Bruce Ashfield
2012-08-01 16:21     ` Stuart Yoder
2012-08-01 16:36       ` Mark Hatle
2012-08-01 16:49         ` Darren Hart
2012-08-01 16:52           ` Bruce Ashfield
2012-08-01 18:59         ` McClintock Matthew-B29882
2012-08-01 19:05           ` Mark Hatle
2012-08-01 20:05             ` Otavio Salvador
2012-08-02 22:50               ` Stuart Yoder
2012-08-03 10:20                 ` Koen Kooi
2012-08-03 11:19                 ` Otavio Salvador
2012-08-03 15:30                   ` Mark Hatle

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=501839ED.4050004@communistcode.co.uk \
    --to=ml@communistcode.co.uk \
    --cc=openembedded-core@lists.openembedded.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