[Buildroot] [RFC PATCH 1/1] core: add option to disable RPATH sanitation in target tree

Arnout Vandecappelle arnout at mind.be
Thu May 3 21:27:34 UTC 2018

On 03-05-18 23:21, Ciro Santilli wrote:
> On Thu, May 3, 2018 at 10:16 PM, Arnout Vandecappelle <arnout at mind.be> wrote:
>> On 03-05-18 21:15, Ciro Santilli wrote:
>>> Signed-off-by: Ciro Santilli <ciro.santilli at gmail.com>
>>> ---
>>> As explained on the Config, the rationale is to speed up BR2_EXTERNAL
>>> package development build iteration.
>>  I don't see what this has to do with package development. Anyway, when you're
>> developing package foo, wouldn't you run 'make foo' rather than just 'make' (and
>> thus never even hit that code path)?
> How to test the modification without rebuilding the image to run it on
> the target?

 Ah, I usually just scp or rsync the (unstripped) binaries to the target system.
I'll typically write a little script that does something like 'make
FOO_OVERRIDE_SRCDIR=... foo; ssh target rm -f /usr/bin/foo; scp
output/target/usr/bin/foo target:/usr/bin; ssh target killall foo; ssh -f target

>>> This would make users targetting virtual machines happy.
>>  Huh? Or you mean building in virtual machines?
> No, cross compiling for VMs from host as opposed to real hardware.

 What difference does it make whether your target is a VM or real hardware?



Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF

More information about the buildroot mailing list