On 2013-11-22 06:15, Robert P. J. Day wrote:
if i use "bb show" to examine the files that go into each package
(eg, for "zlib" here), what i get is the collection of wildcards that
will, of course, still be processed when sequentially creating each
package:
$ bb show -r zlib FILES_zlib-dev
Parsing recipes..done.
# FILES_zlib-dev=${includedir} ${FILES_SOLIBSDEV} ${libdir}/*.la
${libdir}/*.o ${libdir}/pkgconfig ${datadir}/pkgconfig
${datadir}/aclocal ${base_libdir}/*.o ${libdir}/${BPN}/*.la
${base_libdir}/*.la
FILES_zlib-dev="/usr/include /lib/lib*.so /usr/lib/lib*.so
/usr/lib/*.la /usr/lib/*.o /usr/lib/pkgconfig /usr/share/pkgconfig
/usr/share/aclocal /lib/*.o /usr/lib/zlib/*.la /lib/*.la"
$
is there an equivalently simple way to display the end result of the
contents of each package?
You can use the package manager (opkg, rpm) to ask for this info.
For example, using opkg on an installed image:
# opkg list-installed
# opkg files ethtool
You can even run this on an [uninstalled] image. From your build tree,
the tools are accessible and the image root file system as well. In the
example above:
$ tmp/sysroots/x86_64-linux/usr/bin/opkg-cl -f tmp/work/sabrelite-poky-linux-gnueabi/poky-x11-image/1.0-r0/opkg.conf -o
tmp/work/sabrelite-poky-linux-gnueabi/poky-x11-image/1.0-r0/rootfs list-installed
$ tmp/sysroots/x86_64-linux/usr/bin/opkg-cl -f tmp/work/sabrelite-poky-linux-gnueabi/poky-x11-image/1.0-r0/opkg.conf -o
tmp/work/sabrelite-poky-linux-gnueabi/poky-x11-image/1.0-r0/rootfs files ethtool
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
