mirror of
https://git.yoctoproject.org/poky
synced 2026-05-08 05:09:24 +00:00
Hongxu Jia
19ac10a86d
Invoking dpkg-scanpackages on Fedora 17 to build deb image meets such an error: Can't locate Dpkg.pm in @INC (@INC contains: /usr/local/lib64/perl5 /usr/loc al/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr /lib64/perl5 /usr/share/perl5.) at tmp/sysroots/x86_64-linux/usr/bin/dpkg-sca npackages line 27. 1. The dpkg-scanpackages is invoked at deb image creation time and it is built by dpkg-native. The dpkg-scanpackages is a perl script and import module `Dpkg'. 2. The Dpkg.pm has been installed in perl's staging dir at dpkg-native compiling time. Such as `tmp/sysroots/x86_64-linux/usr/lib/perl-native/perl/Dpkg.pm' 3. The dpkg-native uses create_wrapper to relocate to perl-native if perl-native has been built. If perl-native isn't built, it will use the host Dpkg as default. 4. If dpkg-native is built on a new build envionment which means perl-native doesn't exist before, and the build system doesn't install dpkg (such as Fedora 17), the dpkg-scanpackages could not work correctly. 5. Modify dpkg-native's depends, change `perl-native-runtime' to `perl-native', Let perl-native automatically be built before building dpkg-native. [YOCTO #3817] (From OE-Core rev: 7d194e72ee12cb6690bf07a8423cb461dd210719) Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Poky
====
Poky is an integration of various components to form a complete prepackaged
build system and development environment. It features support for building
customised embedded device style images. There are reference demo images
featuring a X11/Matchbox/GTK themed UI called Sato. The system supports
cross-architecture application development using QEMU emulation and a
standalone toolchain and SDK with IDE integration.
Additional information on the specifics of hardware that Poky supports
is available in README.hardware. Further hardware support can easily be added
in the form of layers which extend the systems capabilities in a modular way.
As an integration layer Poky consists of several upstream projects such as
BitBake, OpenEmbedded-Core, Yocto documentation and various sources of information
e.g. for the hardware support. Poky is in turn a component of the Yocto Project.
The Yocto Project has extensive documentation about the system including a
reference manual which can be found at:
http://yoctoproject.org/documentation
OpenEmbedded-Core is a layer containing the core metadata for current versions
of OpenEmbedded. It is distro-less (can build a functional image with
DISTRO = "") and contains only emulated machine support.
For information about OpenEmbedded, see the OpenEmbedded website:
http://www.openembedded.org/
Where to Send Patches
=====================
As Poky is an integration repository, patches against the various components
should be sent to their respective upstreams.
bitbake:
bitbake-devel@lists.openembedded.org
meta-yocto:
poky@yoctoproject.org
Most everything else should be sent to the OpenEmbedded Core mailing list. If
in doubt, check the oe-core git repository for the content you intend to modify.
Before sending, be sure the patches apply cleanly to the current oe-core git
repository.
openembedded-core@lists.openembedded.org
Note: The scripts directory should be treated with extra care as it is a mix
of oe-core and poky-specific files.