All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Kessler <djkessler@utexas.edu>
To: buildroot@busybox.net
Subject: [Buildroot] How to avoid rebuilding host-cmake
Date: Wed, 18 Feb 2015 09:28:52 -0600	[thread overview]
Message-ID: <54E4AFB4.1000705@utexas.edu> (raw)
In-Reply-To: <CAMQcK5+EMynEMspbf6N8VAbHeJksnZg4fP5NSqRDz2smdTK4yA@mail.gmail.com>

Hi Ryan,

Thanks for the reply. Before posting, I looked over the documentation 
that discusses when a full rebuild is required.  Your assumption is 
mostly correct, I have been doing some light kernel development. And I 
have been utilizing buildroot's <pkg>_OVERRIDE_SRCDIR option. However, I 
have also been experimenting with many different configuration options, 
options provided by buildroot and by the linux kernel.  According to the 
buildroot documentation, a full rebuild is required when removing a 
package, and I haven't had much success with adding packages without 
doing a full rebuild.

So, I ask about rebuilding host-cmake because it takes quite a long 
time, and it doesn't seem like it needs to be rebuilt when I'm merely 
adding or removing a package.  I suppose that is a bit of an assumption 
on my part.... maybe host-cmake does indeed need to be rebuilt, 
depending on the package I've added or removed?

In any case, thanks for your suggestions.

Best Regards,
David Kessler--


On 02/17/2015 05:02 PM, Ryan Barnett wrote:
> David,
>
> On Tue, Feb 17, 2015 at 4:38 PM, David Kessler <djkessler@utexas.edu> wrote:
>> I am trying to reduce the amount of time it takes to rebuild the
>> linux kernel and its dependencies.  I am already using the external
>> toolchain option (toolchain was originally built using buildroot, but
>> in an external directory) so I?m not rebuilding the toolchain
>> unnecessarily. However, for some reason after doing ?make clean?,
>> host-cmake has to be rebuilt. For my configuration host-cmake is
>> the most time consuming part of the build.
> A 'make clean' in the concept of Buildroot delete all build products
> (including build directories, host, staging and target trees, the
> images and the toolchain). Therefore, an understanding of when a full
> rebuild is necessary. Please see the following section in the manual:
>
> http://nightly.buildroot.org/manual.html#full-rebuild
>
> A per package rebuild functionality is availalbe and is described here:
>
> http://nightly.buildroot.org/manual.html#rebuild-pkg
>
> Is it fair to assume that you are trying to do kernel development?
>
> If so, then you should have a look at utilizing the
> <pkg>_OVERRIDE_SRCDIR functionality that Buildroot has which allows
> you to development of a package outside of Buildroot. For more
> detailed information on how to use this feature see Section 8.11.6 in
> the manual:
>
> http://nightly.buildroot.org/manual.html#_advanced_usage
>
> Lastly, you should take a look at utilizing ccache to speed up your
> builds, see Section 8.11.3 in the manual:
>
> http://nightly.buildroot.org/manual.html#_advanced_usage
>
> Thanks,
> -Ryan
>

  reply	other threads:[~2015-02-18 15:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-17 22:38 [Buildroot] How to avoid rebuilding host-cmake David Kessler
2015-02-17 23:02 ` Ryan Barnett
2015-02-18 15:28   ` David Kessler [this message]
2015-02-18 15:33     ` Ryan Barnett
2015-02-18 16:01     ` Thomas Petazzoni

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=54E4AFB4.1000705@utexas.edu \
    --to=djkessler@utexas.edu \
    --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.