I needed to reference the image differently for the pre-built section.
(From yocto-docs rev: 10568a0a8c4160af995089e481ccc2772e81d805)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This was a final scrub of the manual. I updated all examples and links
to be current for what I think will be the 1.1 release. I also added
some cross-referencing into the YP dev manual that now exist.
(From yocto-docs rev: 4c10b0e04856817a1d03aee7a9ed6e4d5d73a3ac)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
These changes reflect corrections resulting from Jessica Zhang's review
of the sections.
(From yocto-docs rev: c3fed39bc3909c38424e7e72c40471dcb0053c8d)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
After working through this stuff I was still confused as to how to
guide the user toward proper toolchain installation and on what they
needed to do for collecting their kernel and filesystem images.
These changes included some information on when and how to extract
the rootfs when the user is booting to NFS. Plus some other
general items like the significance of meta-toolchain-sdk as
compared to meta-toolchain.
(From yocto-docs rev: 2cc88b5193888a074ffd87cb253b9cfe08146877)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I had definitions for "The Yocto Project Files" and "The Yocto
Project Build Tree" in this chapter. They were misplaced. I have
deleted them and moved them to the development manual.
(From yocto-docs rev: 9238e75abc4578043fd625b3796b86d42204e16f)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I moved the terms "Yocto Project Files" and "Yocto Project Build
Tree" into this development manual. They were previous defined
in the ADT manual. It makes more sense to have them where with other
terms.
(From yocto-docs rev: 2133110fd280db8cfbe998e6b46cdee0b260e777)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I made changes to the section titles so they have quotes around them
for easier reading in the PDF manual.
(From yocto-docs rev: 5bea470682c3d834f30ab0d2fcba148ea33d653f)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I added a development writer note and I noted that running a project
as an eclipse application pops a new instance of Eclipse.
(From yocto-docs rev: 6408ff7f4d59a0e535e560c7c0c63a3f373c640b)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I added a couple of writer notes for development purposes. I also
formated the section title references so they have quotes around them
for easier reading in the PDF verison.
(From yocto-docs rev: 37adb580cf6c1369da43fc4ef7aaa4cc1cee0e5c)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
fixed some section naming conventions and minor wordings.
(From yocto-docs rev: 768d386c135c57ed3573e08bac72cad47fa101ce)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The information in the "Contributions" section has been migrated to
a "Submitting a Change" section in the YP Development Manual.
I re-wrote this section here to simply make a general statement
about how you can submit a change and then provided a reference
link to the appropriate section in the dev manual.
(From yocto-docs rev: 038caebb2815a8f09d35e99d5a2a0be76b05cacf)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The section on submitting a change was very sparse and incomplete.
I have significantly upgraded this section to provide more details.
(From yocto-docs rev: af43bb1e4902c45afb5ac4b0f099877acd7a81a2)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Without this change we may or may not include startup-notification support.
We therefore explictly include it in the dependency list.
(From OE-Core rev: 8ad24306d8bc9c2fd73f4b814eb1a64c04707da5)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The debug and verbosity levels (as set by the -D and -v command line
options respectively) were not being passed through within msg.py since
bitbake revision 45aad2f9647df14bcfa5e755b57e1ddab377939a due to
incorrect variable names.
Fixes [YOCTO #1513].
(Bitbake rev: c6e88b7c0e61f9586a275df53f48b90687c5f92f)
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This fixes the internal dirtiness tracking such that if the Save menu item
is selected after loading a recipe the existing file is updated rather than
the user being prompted for the path to create a recipe at.
(Bitbake rev: 00fc1d7249b5e217cc7c36ac71b63ddad1c5b769)
Signed-off-by: Joshua Lock <josh@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
After the reparse we were setting the model to reflect the values before
the reparse was triggered but clearing the internal variables used to test
whether these values are set, leading to the UI erroneously reporting that
selections had not been made.
(Bitbake rev: 656eafe0f2c9ec7730d33e15705b8c720f787c49)
Signed-off-by: Joshua Lock <josh@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Instead of calling getVariable commands each time the BBPATH and BBFILES
entries need testing cache the results as a member variable at object
instantiation.
Fixes [YOCTO #1521]
(Bitbake rev: 109e1597671dfb7222672e268190aabc727960ca)
Signed-off-by: Joshua Lock <josh@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added a native sstate post install function to fix the links
created between /lib and /usr/lib for the library files. These
links could point to an invalid build area when using shared state.
(From OE-Core rev: 8ab7b681cdb43c6c21c187b8cd01faa39727824a)
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This fixes a problem when building meta-toolchain-gmae, by adding items that
will be provided by the host system, such as /bin/bash, /usr/bin/env and
libGL.so
(From OE-Core rev: 01361f9d25b0a0027bbbe713b93051a4663b14fc)
Signed-off-by: Saul Wold <sgw@linux.intel.com>
RP: libGL.so() -> libGL.so
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #1514]
Without a native dependency on libxml-parser-perl-native,
shared-mime-info-native can fail its do_configure task.
checking for XML::Parser... configure: error: XML::Parser perl module is
required for intltool
Testing: Successfully built shared-mime-info and shared-mime-info-native for
qemuppc.
(From OE-Core rev: 51b1df89828e677232e125181209b26d3c5ec928)
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
CC: Joshua Lock <josh@linux.intel.com>
CC: Richard Purdie <richard.purdie@linuxfoundation.org>
CC: Koen Kooi <koen@dominion.thruhere.net>
CC: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This patch partially fixes problems when building multilib extended
images such as libXX-core-image-minimal. Its not a perfect/complete
solution but works much better than any previous code did.
[YOCTO #1496] (partial)
[YOCTO #1497] (partial)
[YOCTO #1498] (partial)
(From OE-Core rev: 00c38774ef0232cc2be924ed8e59220e7c452096)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
[YOCTO #1507]
We need to remove the file qemuarm/shutdown.desktop, or else, on qemuarm,
due to the PACKAGE_ARCH overriding from all to qemuarm in base.bbclass,
the generated deb file will be stored at
tmp/deploy/deb/qemuarm/qemu-config_1.0-r21_allarch.deb rather than
tmp/deploy/deb/all/qemu-config_1.0-r21_all.deb, and the package qemu-config
won't be installable -- task-base finally rdepends on qemu-config, so we get
the do_rootfs failure:
The following packages have unmet dependencies:
| task-base-extended: Depends: task-base but it is not going to be installed
| E: Broken packages
There is also a generic shutdown.desktop, we can keep it and use a proper
pkg_postinst to cope with the case of qemuarm.
(From OE-Core rev: 751212d5effdceab91d95705e647cf07e6820940)
Signed-off-by: Dexuan Cui <dexuan.cui@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This eliminates a good chunk of buildtime when building console-only image.
The bluez4 and this recipe share a .inc file since the source is the same.
(From OE-Core rev: 5eaed4bba35e8188855acb93344adf48201748a2)
Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Disable a few checks, and hard code the values for a few other items
to work around potential host contamination issues. We also default
to the cups configuration for items.
(From OE-Core rev: ef7ad7a7c6b5f5a6c9d0d9e35e07b5a0dabe5be9)
Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
${libdir} is not used, instead they use a common ${exec_prefix}/lib
directory structure for helpers, filters, renderers, etc.
(From OE-Core rev: 24ae432b1a3906956381d83c1984687e45c5a1d1)
Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
We pass --with-cpu to eglibc now. Which breaks
the configure for cpus that it does not support
We add support for ppc603e which gets 2.12
building for qemuppc.
(From OE-Core rev: 465a988e2370ec377875b599045f2a7bad913ac6)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This reverts commit 974cdb88680359aac5aefd11b84c4a374ab3a753.
See the mailing list for details, this broke things for too
many people such as where PKGSUFFIX is used in PREFERRED_PROVIDER.
odified: meta/recipes-core/eglibc/eglibc-locale.inc
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
New gcc uses "%esp" rather than "%ebp" to index local variable in stack, and
push between save-to/restore-from stack decrease "%esp", which leads wrong
index. Saving registers via local variables to make gcc aware of this and avoid
stack disorder.
[YOCTO #1442] got fixed
(From OE-Core rev: afc9edc27e77e80fdd24b4c8c538f91672940e75)
Signed-off-by: Zhai Edwin <edwin.zhai@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
eglibc.inc contains packaging rules that depend on PKGSUFFIX expansion.
However that variable wasn't expanded properly in some case. E.g.
PACKAGES = " ... nscd${PKGSUFFIX} ..."
FILES_nscd${PKGSUFFIX} = "${sbindir}/nscd*"
would be expanded to
PACKAGES = " ... nscd-nativesdk ..."
FILES_nscd = "${sbindir}/nscd*"
Thus leading to empty -nativesdk packages and missing files. To overcome
that use python code blob to properly define PKGSUFFIX variable.
(From OE-Core rev: 974cdb88680359aac5aefd11b84c4a374ab3a753)
Signed-off-by: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Some scripts are necessary to develop programs with libcom_err and
libss. Include those into e2fsprogs-dev package.
(From OE-Core rev: 46332c2313abb273f6fc889fac4daa91cf43faa3)
Signed-off-by: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
glib-utils already includes glib-gettextize program. Include some files
necessary for glib-gettextize to work.
(From OE-Core rev: c98356e9c46cd28b7ca8e84fe0ea56dc6d812a8d)
Signed-off-by: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
alsa-lib: Don't use versioned symbols on uclibc builds as it causes strange hangs. Taken from oe-classic.
(From OE-Core rev: b354eb957ce08ac7814ce46c13ca3a8449b4063a)
Signed-off-by: Daniel Lazzari Jr <dlazzari@leapfrog.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
libxml2 provides a libxml2.a library, which wasn't included in any of
the packages. Usually static libs are included into a -staticdev
package, but this package wasn't generated for libxml2, due to
libxml2.inc redeclaring PACKAGES variable (to include libxml2-utils).
Replace PACKAGES setting with expansion to include all default packages
(and so -staticdev package with libxml2.a).
(From OE-Core rev: 76052861cc95fd4ad4c4b9eb6ce4cd1065ad4dc9)
Signed-off-by: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
It seems nobody uses preloadable_libintl.so in OE world. It's not
included in any package. To stop oe-core from emiting a unshipped files
warning, remove that file in the end of do_install.
(From OE-Core rev: 9d33b6973438f514f1ca609c3a936b45af921e2f)
Signed-off-by: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
1) Drop static versions of extensions, as there is no point in them
2) For completeness include .la files for extensions into polkit-dev
(From OE-Core rev: e1a9f9e7f823330ab5140735b80988541e86e2d4)
Signed-off-by: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
1) Package gail modules into libgail package. .la files go into main
gtk+-dev package, debug symbols to gtk+-dbg.
2) For completeness add printerbackends .la files to gtk+-dev
(From OE-Core rev: a797c4ff1246566b545dc6cab2713a04f24fea6e)
Signed-off-by: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>