Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] make linux26-force
Date: Fri, 25 Jun 2010 09:24:50 +0200	[thread overview]
Message-ID: <20100625092450.25314ba1@surf> (raw)
In-Reply-To: <0D753D10438DA54287A00B02708426976372DCA426@AUSP01VMBX24.collaborationhost.net>

Hello,

On Thu, 24 Jun 2010 10:48:09 -0500
H Hartley Sweeten <hartleys@visionengravers.com> wrote:

> No.  Manually adding a new patch or making a change to one of the source
> files will not cause the kernel to be rebuilt.  And, doing a linux26-menuconfig
> also will not cause the rebuild (unless something is changed).

True.

> I'm trying to bring up a new board design so I am always making changes to
> my kernel board init file, either to enable a new feature or test something.
> 
> I know I can force the rebuild by touching the stamp_configured file but
> it's kind of a hassle since I was used to just doing either:
> 
> $ make linux26-force;make
> 
> Of 
> 
> $ make linux26-force;make linux26
> 
> This has worked fine for me since I started using buildroot.  The linux-cleanup
> commit changed that behavior.

I understand.

In general, Buildroot is not really good at allowing people to change
the code of the different components it compiles. We had this
linux26-specific thing, but for all other regular packages, we have
nothing in place.

So, I'd prefer not to add a linux26-specific knob and have a generic
reflexion on how we want to handle this use-case, for all packages. And
in general the use-case of Buildroot being used during *development*
and not only for integration.

Regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2010-06-25  7:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-23 22:59 [Buildroot] make linux26-force H Hartley Sweeten
2010-06-24  7:23 ` Thomas Petazzoni
2010-06-24 15:48   ` H Hartley Sweeten
2010-06-25  7:24     ` Thomas Petazzoni [this message]
2010-06-25  9:53     ` 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=20100625092450.25314ba1@surf \
    --to=thomas.petazzoni@free-electrons.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