automatic debug package generation
On Fri, Sep 27, 2013 at 12:00 AM, Brad Litterell
b...@evidence.commailto:b...@evidence.com wrote:
My recipe builds and ships an executable in /foo/bin/fooapp
FILES_${PN} += /foo/bin/*
WARNING: QA Issue: foo: Files/directories were installed but not shipped
/foo
On Fri, Sep 27, 2013 at 8:11 AM, Brad Litterell b...@evidence.com wrote:
Thanks Nicolas!
Sent from my Windows Phone
From: Nicolas Dechesne
Sent: 9/26/2013 15:29
To: Brad Litterell
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] Question about automatic
On Fri, Sep 27, 2013 at 8:49 AM, Hans Beckérus hans.becke...@gmail.comwrote:
Actually, I have a related question. If you choose to install -dbg
variants, you will get a .debug folder copied to the target.
That .debug folder can then be pointed out by debuggers etc. to get
the symbol
My recipe builds and ships an executable in /foo/bin/fooapp
FILES_${PN} += /foo/bin/*
WARNING: QA Issue: foo: Files/directories were installed but not shipped
/foo/bin/.debug
/foo/bin/.debug/fooapp
This file doesn't appear in the image, but is in the package folder:
On Fri, Sep 27, 2013 at 12:00 AM, Brad Litterell b...@evidence.com wrote:
My recipe builds and ships an executable in /foo/bin/fooapp
FILES_${PN} += /foo/bin/*
WARNING: QA Issue: foo: Files/directories were installed but not shipped
/foo/bin/.debug
/foo/bin/.debug/fooapp
This file
