From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Is there an equivalent of yocto's devshell?
Date: Thu, 1 Sep 2016 11:39:41 +0200 [thread overview]
Message-ID: <20160901113941.36166d9e@free-electrons.com> (raw)
In-Reply-To: <8b51ea03-6172-ce10-9a80-7caf43952de1@flatmax.org>
Hello,
On Thu, 1 Sep 2016 17:51:31 +1000, Matt Flax wrote:
> Is it necessary to have a devshell ? Could you simply run 'make package'
> instead and work live in the output/build/package directory ?
> You can rerun various parts of the make process by deleting the .stamp_*
> files in the package directory.
>
> Conceptually if you build the package you are working on natively on
> your desktop, you should be able to do all the library inclusion and
> linking locally ... once happy, you can simply invoke buildroot to cross
> compile for you ... I would imagine that that would be a much faster way
> top develop ...
Fully agreed. I am not sure I understand the usefulness of devshell. It
is just easier and more efficient to use the build system directly.
However, if you're actively working on the source of a package, do
*NOT* make your changes in outptu/build/<package>-<version>/. This
directory is a temporary location. Instead, use the OVERRIDE_SRCDIR
mechanism, which allows you to tell Buildroot to take the source code
for a given package from a given directory. See
http://free-electrons.com/doc/training/buildroot/buildroot-slides.pdf
slides 261 and following.
My feeling is that things like devshell are created because using Yocto
during development is too painful. Buildroot simply doesn't need
something like devshell because using the build system during active
development is perfectly fine. Of course, if you disagree and have some
concrete examples, we'll be happy to look into this.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-09-01 9:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-31 16:12 [Buildroot] Is there an equivalent of yocto's devshell? Ottavio Campana
2016-08-31 20:50 ` Peter Korsgaard
2016-09-01 7:20 ` Ottavio Campana
2016-09-01 7:51 ` Matt Flax
2016-09-01 9:39 ` Thomas Petazzoni [this message]
2016-09-01 10:23 ` Zoltan Gyarmati
2016-09-01 12:18 ` Ottavio Campana
2016-09-02 1:51 ` Matt Flax
2016-09-01 20:53 ` 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=20160901113941.36166d9e@free-electrons.com \
--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