[Buildroot] Is there an equivalent of yocto's devshell?

[Matt Flax]

On 01/09/16 22:18, Ottavio Campana wrote:
>> 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.
> Thomas, you are 100%.
>
> The usual situation is you develop a portable program, but then you need to specialize some part that is platform-specify and you need to work on the sources with the cross compiler.
>
>
Further on this topic...
If you need to work on sources w.r.t. specific cross compile setups, 
there are a few ways to do that effectively/efficiently when using 
buildroot.

One way for example is to use quilt ... e.g. when editing an old linux 
mach/plat device file, have an external buildroot directory with a 
patches/linux directory.
You can then "make linux" then "cd output/build/linux" and "ln -s" your 
external patches/linux folder to the quilt expected patches directory. 
You can then use quilt as expected, and whenever "quilt refresh" is run, 
the external patches get updated.

In this manner, you use standard buildroot and quilt to manage patches 
for cross-compiled packages ... once you are happy, you can then either 
use the patches as per the standard process with buildroot or apply them 
against your original sources.

Matt