Thanks Nicolas! Sent from my Windows Phone ________________________________ From: Nicolas Dechesne<mailto:nicolas.deche...@linaro.org> Sent: 9/26/2013 15:29 To: Brad Litterell<mailto:b...@evidence.com> Cc: yocto@yoctoproject.org<mailto:yocto@yoctoproject.org> Subject: Re: [yocto] Question about automatic debug package generation
On Fri, Sep 27, 2013 at 12:00 AM, Brad Litterell <b...@evidence.com<mailto: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 doesn't appear in the image, but is in the package folder: ./package/foo/bin/.debug/fooapp It appears something is automatically creating these .debug files during the packaging steps, but the corresponding file isn't under packages-split. Can someone point me to a place to learn more about how these are created and packaged? this is done in meta/classes/package.bbclass. at the beginning of that file, you will find an overall description of what the 'packaging' steps are, and you can see, among many things: # d) split_and_strip_files - split the files into runtime and debug and strip them. # Debug files include debug info split, and associated sources that end up in -dbg packages you can then check the source code for the function split_and_strip_files. Now, about 'packaging' the files, you need to look at meta/conf/bitbake.conf and search for FILES_{PN}-dbg. this is the default variable that specifies which files go into the -dbg package. Your issue above is because the 'default' path for binary is /usr/bin, hence the 'default' path for debug variants is /usr/bin/.debug. But if you need '/foo' , you can change these default in your recipe, by modifying FILES_{PN}xxx in your .bb file.
_______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
