From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] Another Buildroot Enhancement Suggestion (re-use base build)
Date: Fri, 17 Jul 2015 10:04:07 +0300 [thread overview]
Message-ID: <20150717070407.GF3147@tarshish> (raw)
In-Reply-To: <CALoSW65V2bmF8GEtUH_hLm-_n9vPDEjnK5-YXyx_eXoy04fDKw@mail.gmail.com>
Hi Nimai,
On Thu, Jul 16, 2015 at 08:48:02AM -0400, Nimai Mahajan wrote:
> I should have brought this up during the hackathon but it totally
> slipped my mind. But anyways, here it goes: we use Buildroot for ~3-4
> projects here at work and it's been great for us since it is very easy
> to customize and build from the ground up. We generally compile our
> builds from scratch, as is the Buildroot norm, and that works (I also
> use CCACHE and external toolchain and that does help quite a bit) but
> I was wondering if this could be even further sped up.
>
> The use case is that our release builds for those 3-4 projects is
> always the same (minus a slightly different fs overlay and 1-2
> different packages). Is there any way or do you guys see any
> usefulness in taking an already built "external base build" with all
> the packages that subsequent builds will use and telling Buildroot
> what to add on top of it? Basically, it doesn't make sense to me to
> rebuild the entire thing when only a few files change. This is
> probably a huge effort as I don't think a mechanism exists to do it
> but I'm just looking for some comments/thoughts. Does this even make
> sense or is there already a decent way to do this?
>
> For release builds, this is not a major problem because builds only
> take 5-10 min at most, but when you're compiling debug builds with
> debugging symbols for various projects, this can add hours or even
> days if builds fail. We have Jenkins running and pumping out builds
> for us 24/7, and this would help a lot in testing, taking a prebuilt
> base build and just recompiling our custom packages (for now, we do a
> -dirclean on our packages and rebuild them every time which works for
> the time being).
The patch at http://patchwork.ozlabs.org/patch/464753/ might be helpful for
you. Please check it out and let us know.
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
next prev parent reply other threads:[~2015-07-17 7:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-16 12:48 [Buildroot] Another Buildroot Enhancement Suggestion (re-use base build) Nimai Mahajan
2015-07-17 7:04 ` Baruch Siach [this message]
2015-07-17 13:17 ` Nimai Mahajan
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=20150717070407.GF3147@tarshish \
--to=baruch@tkos.co.il \
--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.