Martin,

Good question and several reasons.  Build time isn’t as much of a factor as 
most of the packages that create the –dbg and –doc packages are core packages 
that don’t get rebuilt very often.  The big reason is that I’m using a copy of 
the tmp/deploy/ipk/ directory for firmware upgrade for our devices and trying 
to reduce the clutter.  By just going through and deleting all the –dbg and 
–doc packages from the ipk/ directory I reduced its size from about 300 MB to 
about 150 MB (side note: the 300 MB ipk/ directory size was after some 
additional cleanup.  I recently reset my tmp/ directory as the ipk/ directory 
had grown to 700 MB with different stuff I have tried).  Since one method of 
firmware upgrade for us is through a USB stick, the smaller that directory gets 
the easier it is to transfer to a USB stick.  So my thought was that if I’m 
building the packages for a production setup in which the –dbg and –doc 
packages will never be used, why bother even generating them in the first place?

My overall goal, which this is part of, is to reduce the resulting ipk/ 
directory to only the packages that are actually used by the image I built.  
Based on my final image size, if I only include the packages that are used for 
the image I believe I could get the ipk/ directory to under 50 MB.  Making it 
that small would make some options, such as providing a download from our 
company’s website for our customers, more reasonable.

Thanks,
Bryan

From: Martin Jansa [mailto:martin.ja...@gmail.com]
Sent: Wednesday, October 23, 2013 6:12 PM
To: Bryan Evenson
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] How to prevent building -dbg and -doc packages?

Why do you want to disable them? All the files are already there, so packaging 
them in right package doesn't cost much (if your reason was build time).

On Wed, Oct 23, 2013 at 6:31 PM, Bryan Evenson 
<beven...@melinkcorp.com<mailto:beven...@melinkcorp.com>> wrote:
I'm on poky/dylan-9.0.1.  I'm not using any of the -dbg and the -doc packages 
and I'd like to clean things up for my build by not building these packages in 
the first place across the entire system.  I see references in the 
documentation to these package types, but I haven't found anything about how to 
keep the system from generating them.

I tried going into meta/conf/bitbake.conf and modifying the PACKAGES variable 
to look as follows:

PACKAGES = "${PN}-staticdev ${PN}-dev ${PN}-locale ${PACKAGE_BEFORE_PN} ${PN}"

This caused a bunch of packages to get rebuilt and seemed to be working until 
it got to the libpam package.  Then I got the following errors:

ERROR: QA Issue: non debug package contains .debug directory: libpam-xtests 
path 
/work/arm926ejste-poky-linux-gnueabi/libpam/1.1.6-r2/packages-split/libpam-xtests/usr/share/Linux-PAM/xtests/.debug/tst-pam_dispatch2
ERROR: QA Issue: non debug package contains .debug directory: libpam-xtests 
path 
/work/arm926ejste-poky-linux-gnueabi/libpam/1.1.6-r2/packages-split/libpam-xtests/usr/share/Linux-PAM/xtests/.debug/tst-pam_pwhistory1
ERROR: QA Issue: non debug package contains .debug directory: libpam-xtests 
path 
/work/arm926ejste-poky-linux-gnueabi/libpam/1.1.6-r2/packages-split/libpam-xtests/usr/share/Linux-PAM/xtests/.debug/tst-pam_access3
ERROR: QA Issue: non debug package contains .debug directory: libpam-xtests 
path 
/work/arm926ejste-poky-linux-gnueabi/libpam/1.1.6-r2/packages-split/libpam-xtests/usr/share/Linux-PAM/xtests/.debug/tst-pam_unix2
ERROR: QA Issue: non debug package contains .debug directory: libpam-xtests 
path 
/work/arm926ejste-poky-linux-gnueabi/libpam/1.1.6-r2/packages-split/libpam-xtests/usr/share/Linux-PAM/xtests/.debug/tst-pam_succeed_if1
ERROR: QA Issue: non debug package contains .debug directory: libpam-xtests 
path 
/work/arm926ejste-poky-linux-gnueabi/libpam/1.1.6-r2/packages-split/libpam-xtests/usr/share/Linux-PAM/xtests/.debug/tst-pam_authsucceed
ERROR: QA Issue: non debug package contains .debug directory: libpam-xtests 
path 
/work/arm926ejste-poky-linux-gnueabi/libpam/1.1.6-r2/packages-split/libpam-xtests/usr/share/Linux-PAM/xtests/.debug/tst-pam_dispatch4
ERROR: QA Issue: non debug package contains .debug directory: libpam-xtests 
path 
/work/arm926ejste-poky-linux-gnueabi/libpam/1.1.6-r2/packages-split/libpam-xtests/usr/share/Linux-PAM/xtests/.debug/tst-pam_access1
ERROR: QA Issue: non debug package contains .debug directory: libpam-xtests 
path 
/work/arm926ejste-poky-linux-gnueabi/libpam/1.1.6-r2/packages-split/libpam-xtests/usr/share/Linux-PAM/xtests/.debug/tst-pam_time1
ERROR: QA Issue: non debug package contains .debug directory: libpam-xtests 
path 
/work/arm926ejste-poky-linux-gnueabi/libpam/1.1.6-r2/packages-split/libpam-xtests/usr/share/Linux-PAM/xtests/.debug/tst-pam_unix3
ERROR: QA Issue: non debug package contains .debug directory: libpam-xtests 
path 
/work/arm926ejste-poky-linux-gnueabi/libpam/1.1.6-r2/packages-split/libpam-xtests/usr/share/Linux-PAM/xtests/.debug/tst-pam_authfail
ERROR: QA Issue: non debug package contains .debug directory: libpam-xtests 
path 
/work/arm926ejste-poky-linux-gnueabi/libpam/1.1.6-r2/packages-split/libpam-xtests/usr/share/Linux-PAM/xtests/.debug/tst-pam_cracklib1
ERROR: QA Issue: non debug package contains .debug directory: libpam-xtests 
path 
/work/arm926ejste-poky-linux-gnueabi/libpam/1.1.6-r2/packages-split/libpam-xtests/usr/share/Linux-PAM/xtests/.debug/tst-pam_access2
ERROR: QA Issue: non debug package contains .debug directory: libpam-xtests 
path 
/work/arm926ejste-poky-linux-gnueabi/libpam/1.1.6-r2/packages-split/libpam-xtests/usr/share/Linux-PAM/xtests/.debug/tst-pam_cracklib2
ERROR: QA Issue: non debug package contains .debug directory: libpam-xtests 
path 
/work/arm926ejste-poky-linux-gnueabi/libpam/1.1.6-r2/packages-split/libpam-xtests/usr/share/Linux-PAM/xtests/.debug/tst-pam_dispatch1
ERROR: QA Issue: non debug package contains .debug directory: libpam-xtests 
path 
/work/arm926ejste-poky-linux-gnueabi/libpam/1.1.6-r2/packages-split/libpam-xtests/usr/share/Linux-PAM/xtests/.debug/tst-pam_dispatch5
ERROR: QA Issue: non debug package contains .debug directory: libpam-xtests 
path 
/work/arm926ejste-poky-linux-gnueabi/libpam/1.1.6-r2/packages-split/libpam-xtests/usr/share/Linux-PAM/xtests/.debug/tst-pam_limits1
ERROR: QA Issue: non debug package contains .debug directory: libpam-xtests 
path 
/work/arm926ejste-poky-linux-gnueabi/libpam/1.1.6-r2/packages-split/libpam-xtests/usr/share/Linux-PAM/xtests/.debug/tst-pam_dispatch3
ERROR: QA Issue: non debug package contains .debug directory: libpam-xtests 
path 
/work/arm926ejste-poky-linux-gnueabi/libpam/1.1.6-r2/packages-split/libpam-xtests/usr/share/Linux-PAM/xtests/.debug/tst-pam_group1
ERROR: QA Issue: non debug package contains .debug directory: libpam-xtests 
path 
/work/arm926ejste-poky-linux-gnueabi/libpam/1.1.6-r2/packages-split/libpam-xtests/usr/share/Linux-PAM/xtests/.debug/tst-pam_unix4
ERROR: QA Issue: non debug package contains .debug directory: libpam-xtests 
path 
/work/arm926ejste-poky-linux-gnueabi/libpam/1.1.6-r2/packages-split/libpam-xtests/usr/share/Linux-PAM/xtests/.debug/tst-pam_access4
ERROR: QA Issue: non debug package contains .debug directory: libpam-xtests 
path 
/work/arm926ejste-poky-linux-gnueabi/libpam/1.1.6-r2/packages-split/libpam-xtests/usr/share/Linux-PAM/xtests/.debug/tst-pam_unix1
ERROR: QA run found fatal errors. Please consider fixing them.
ERROR: Function failed: do_package_qa
ERROR: Logfile of failure stored in: 
/media/sda3/poky/poky-build/tmp/work/arm926ejste-poky-linux-gnueabi/libpam/1.1.6-r2/temp/log.do_package.8163
ERROR: Task 362 
(/media/sda3/poky/meta/recipes-extended/pam/libpam_1.1.6.bb<http://libpam_1.1.6.bb>,
 do_package) failed with exit code '1'

So either I didn't remove enough from bitbake.conf or there is a better way to 
do this.  Does anyone know of a good way to avoid building all the -dbg and 
-doc packages?

Thanks,
Bryan




_______________________________________________
yocto mailing list
yocto@yoctoproject.org<mailto:yocto@yoctoproject.org>
https://lists.yoctoproject.org/listinfo/yocto

_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Reply via email to