All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hamish Moffatt <hamish@cloud.net.au>
To: buildroot@busybox.net
Subject: [Buildroot] future of project support
Date: Mon, 20 Apr 2009 10:32:49 +1000	[thread overview]
Message-ID: <20090420003249.GA18066@cloud.net.au> (raw)
In-Reply-To: <877i1j9zcu.fsf@macbook.be.48ers.dk>

On Fri, Apr 17, 2009 at 03:36:01PM +0200, Peter Korsgaard wrote:
> Because of the project stuff. There's been discussion about getting
> rid of that and simply use the external toolchain stuff if you want to
> build seperate rootfs'es for similar hw, and I'm seriously considering
> doing so.

I'm in favour of some simplification. Here's my usage:

I have a few related projects. I want to build them from the same source
tree. Ideally I can have them all built within one check-out, so I can
quickly make a change and test it in multiple projects (without checking
in, updating the other check out etc).

I don't care if everything is rebuilt for each project.. (except the
toolchain possibly). I think the current mix of build_arch /
project_build_arch is a mess, I'd prefer to have everything in
project_build_arch really.



Hamish
-- 
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>

  reply	other threads:[~2009-04-20  0:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-17  8:33 [Buildroot] Properly setting up hotplug Sagaert Johan
2009-04-17  8:52 ` Thiago A. Corrêa
2009-04-17 13:56   ` Peter Korsgaard
2009-04-17 14:19     ` Lloyd Sargent
2009-04-17 13:36 ` Peter Korsgaard
2009-04-20  0:32   ` Hamish Moffatt [this message]
2009-04-21  6:11     ` [Buildroot] future of project support Peter Korsgaard

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=20090420003249.GA18066@cloud.net.au \
    --to=hamish@cloud.net.au \
    --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.