On Tue, Mar 8, 2016 at 3:06 PM, Pascal Bach wrote:
> Hi Andreas
>> I am using sysroot for debugging too. I have no
>>
>> * INHERIT += "rm_work"
>>
>> and added
>>
>> INHIBIT_SYSROOT_STRIP = "1"
>>
>> to my local.conf
>>
>> I use this approach for very long time now and from my point of view
>> it
> > The only way I could get this to work is to extract both the rootfs and the
> > rootfs-dbg into the same place and then set sysroot to that location.
> > Is this the way it is supposed to be?
>
> Yes
>
Ok I was hoping to keep them seperate.
This because I'm using the rootfs for NFS and by hav
Hi Andreas
> I am using sysroot for debugging too. I have no
>
> * INHERIT += "rm_work"
>
> and added
>
> INHIBIT_SYSROOT_STRIP = "1"
>
> to my local.conf
>
> I use this approach for very long time now and from my point of view
> it has one BIG advantage: I can use these settings for productive
> i
On Mar 8, 2016 3:54 PM, "Pascal Bach" wrote:
>
> Hi Richard
> > Using this method is a supported approach. I'm a little surprised
> > .debug directories don't work. Have you tried just setting:
> >
> > set sysroot /home/projects/rootfs-dbg
> > set substitute-path /usr/src/debug /home/projects/root
On 8 March 2016 at 10:01, Andreas Müller
wrote:
> How much time is really saved by stripping sysroot?
>
It was more about reducing the size of the sstate than build performance.
It's a toggle for precisely this reason: some users may not care about the
space saving but want to use the sysroot fo
On Fri, Mar 4, 2016 at 12:20 PM, Richard Purdie
wrote:
> On Tue, 2016-02-23 at 15:09 +0100, Pascal Bach wrote:
>> Currently debugging using sysroots seems to work as long as the work
>> folder containing the original source is available.
I am using sysroot for debugging too. I have no
* INHERIT
Hi Richard
> Using this method is a supported approach. I'm a little surprised
> .debug directories don't work. Have you tried just setting:
>
> set sysroot /home/projects/rootfs-dbg
> set substitute-path /usr/src/debug /home/projects/rootfs
> -bbg/usr/src/debug
This doesn't seem to work (tried onl
On Fri, 2016-03-04 at 15:06 +0100, Pascal Bach wrote:
> > It really depends on your view of what the sysroot is used for. We
> > intentionally strip a variety of things out of it as things work
> > today
> > basically for size/performance reasons. If we start putting
> > debugging
> > source in the
> It really depends on your view of what the sysroot is used for. We
> intentionally strip a variety of things out of it as things work today
> basically for size/performance reasons. If we start putting debugging
> source in there, it will become huge and this will image the size of
> things like
On Tue, 2016-02-23 at 15:09 +0100, Pascal Bach wrote:
> Currently debugging using sysroots seems to work as long as the work
> folder containing the original source is available.
> Once this work dir is gone the debugger is no longer able to find the
> source code. This is especially confusing if s
ping!
No comment on this topic?
Am 23.02.2016 um 15:09 schrieb Pascal Bach:
> Hi Everybody
>
> Currently debugging using sysroots seems to work as long as the work folder
> containing the original source is available.
> Once this work dir is gone the debugger is no longer able to find the source
Hi Everybody
Currently debugging using sysroots seems to work as long as the work folder
containing the original source is available.
Once this work dir is gone the debugger is no longer able to find the source
code. This is especially confusing if some packages are taken from sstate and
others
12 matches
Mail list logo
