1f53edeaf9
The libtool would be very slow if run "automake/autoconf --version", for example, when compile xz-native (make -j1, only compile, no confiure or install): before patched: 19s after patched: 11s Use plain text to instead of running them. NOTE: it is still a little slower than libtool 2.4.2 when compile xz-native because of other parts: make -j1: about 2s slower make -j32: about 0.4s slower If we run to do_install: (PARALLEL_MAKE = "-j32") libtool 2.4.2: $ bitbake xz-native -cinstall && bitbake xz-native -ccleansstate && time bitbake xz-native -cinstall real 0m21.092s user 0m28.292s sys 0m3.932s libtool 2.4.5: $ bitbake xz-native -cinstall && bitbake xz-native -ccleansstate && time bitbake xz-native -cinstall real 0m21.380s user 0m31.140s sys 0m4.068s About 0.3s, slightly different. But when using /bin/bash as CONFIG_SHELL, the new libtool would be much slower: real 0m23.106s user 0m44.044s sys 0m4.280s About 2s slower, for the big package like cairo, it is more slower (about 6s), unfortunately, /bin/bash is most default CONFIG_SHELL for the recipes since configure checks first check bash. (From OE-Core rev: eb9d896db2fc67bac8efd258744d06fbbee87f06) Signed-off-by: Robert Yang <liezhi.yang@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 = "nodistro") 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.