From: John Stile <john@stilen.com>
To: buildroot@busybox.net
Subject: [Buildroot] howto incorporate buildroot into an autobuild
Date: Mon, 12 Nov 2012 16:47:29 -0800 [thread overview]
Message-ID: <1352767649.18724.34.camel@genx> (raw)
I am using buildroot for an embedded Arm project.
I was wondering how people using buildroot implement continuous
integration builds?
Do you start from a clean checkout, build the whole tool chain (which
takes a long time), and then build the project specific stuff?
I worry about not starting from a clean checkout, since some options may
change, and the tools won't be rebuilt.
But I also worry people will complain how long the build takes.
Is there a good strategy to balance these concerns?
next reply other threads:[~2012-11-13 0:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-13 0:47 John Stile [this message]
2012-11-13 5:02 ` [Buildroot] howto incorporate buildroot into an autobuild Avery Pennarun
2012-11-13 21:04 ` Arnout Vandecappelle
2012-11-13 8:45 ` Thomas Petazzoni
2012-11-13 20:43 ` Arnout Vandecappelle
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=1352767649.18724.34.camel@genx \
--to=john@stilen.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