Skip to contentSkip to conversation

remove dbg and dev packages

DISCUSSION Jaap de Jong 3 participants 5 messages Mar 16, 2012 – Mar 20, 2012

lore
Share & tools
lore
#0 lore raw

Hi!

is there an option (in local.conf?) to not build (or not add to the repository of) the dbg and dev packages?

Thanks!
Jaap

#1 lore raw
Quoted 7 lines · Jaap de Jong

Hi!

is there an option (in local.conf?) to not build (or not add to the repository of) the dbg and dev packages?

Thanks!
Jaap

Why dont write a shell skript which deletes all dbg and dev packages and calles the opkg index command afterwards?

Bye Henning

#2 lore raw

That was my first guess too.
If I remove them from the build/deploy/glibc/ipk/* directories and then do 'bitbake package-index' that would do the trick? But I would have to remove them after every package I build...

Quoted 18 lines · Henning Heinold
Quoted 7 lines · Jaap de Jong

Hi!

is there an option (in local.conf?) to not build (or not add to the repository of) the dbg and dev packages?

Thanks!
Jaap

Why dont write a shell skript which deletes all dbg and dev packages and calles the opkg index command afterwards?

Bye Henning

_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

#3 lore raw
In reply to Jaap de Jong
Quoted 4 lines · Jaap de Jong

Hi!

is there an option (in local.conf?) to not build (or not add to the repository of) the dbg and dev packages?

You have to build the dev packages, otherwise you can't (cross) compile the software in the development environment.

The dbg packages are optional, but if you disable them then things may or may not be stripped and the filesizes on the target may increase. (It's been a while since I tried it w/o dbg packages...)

Is there a reason why you don't want the dev and dbg packages to be generated? They should only be installed onto a target filesystem if you've requested them (or a package has a dependency on them). Normal, non-dev, filesystems shouldn't be installed any of those components... if they are, there is a packaging bug in something.

See the meta/conf/local.conf.sample.extended:

# Uncomment this to disable the split of the debug information into -dbg files # INHIBIT_PACKAGE_DEBUG_SPLIT = "1"

(There are also other settings to control the specific mechanisms of the package split.. "debian" style or "fedora" style...)

--Mark

Quoted 7 lines

Thanks!
Jaap

_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

#4 lore raw
Quoted 7 lines · Mark Hatle
Quoted 4 lines · Jaap de Jong

Hi!

is there an option (in local.conf?) to not build (or not add to the repository of) the dbg and dev packages?

You have to build the dev packages, otherwise you can't (cross) compile the software in the development environment.

Clear!

Quoted 3 lines

The dbg packages are optional, but if you disable them then things may or may not be stripped and the filesizes on the target may increase. (It's been a while since I tried it w/o dbg packages...)

Don't want that.

Quoted 5 lines

Is there a reason why you don't want the dev and dbg packages to be generated? They should only be installed onto a target filesystem if you've requested them (or a package has a dependency on them). Normal, non-dev, filesystems shouldn't be installed any of those components... if they are, there is a packaging bug in something.

The only simple reason is to keep the repository's and the Packages* files smaller.

Thanks for your comments!