Use the separate builddir code for poky.
(From meta-yocto rev: 2e861624ebcadd1ebbd37fa5892d2f9f44215c13)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
srcdir is still relative to pwd. We need to use
abs_srcdir to get absolute source directory names
(From OE-Core rev: 9297e01b2095d90b5365d23c10de699a7cf411ea)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Various section heading titles were not using capital letters
for primary words. Fixed this up.
(From yocto-docs rev: da15d2ac3d043a0296a51d1a9fac69e7b4229f75)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added a new bullet as a tip for best practices that addresses
how we address bug 3071 and 3274. We are suggesting they enable
a PR Service if they are using continually incrementing PR values
when package feeds are published or used.
Reported-by: Richard Purdie <richard.purdie@linux.com>
(From yocto-docs rev: b90497f139b1b6f7ab5510313eb297d5d7fb4e68)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes YOCTO #2827
Replaced the path where one findes the binary for the meta-
toolchain to a more recent example that was built from
the beagleboard and using arm.
(From yocto-docs rev: 020a7fcd7f99c50d32e831b8d51150e8db8ab4e9)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Changed the wording on when a user would consider using
the BBMASK variable. It is more suited for excluding things
that cause problems rather than for speeding up build time.
Reporte-by: Paul Eggleton <paul.eggleton@linux.com>
(From yocto-docs rev: 993d7c953a37747297238cd9af53a1f00e737df9)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
There was a danny-specific note here that did not apply to the
section any longer. I have removed it per Tom Zanussi's
suggestion.
(From yocto-docs rev: 2a3ccab263cfaa779a5182e6a4a7e534db253700)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Removed the danny-specific note at the end of the
"OProfileUI - A GUI for OProfile" section per Tom Zanussi.
(From yocto-docs rev: b665be9ad906cdc3ac644e67151da3a2cc1acfd3)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
With dylan, the two patches are no longer required. However,
the information to view traces still holds true regarding
using Eclipse's Juno. Updated appropriately.
(From yocto-docs rev: 90845677a37562b465bbd2bc849f773a2f54d92e)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I changed the distro name variable to "dylan" and the release
to 9.0.
(From yocto-docs rev: 4afec4519f3104f5a2e906f9ec4dfcca35d8000a)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Cleared up some old wording that was confusing the build
system with "Poky". Also, added a note at the front of the
manual to be clear that the ADT is distribution-neutral.
(From yocto-docs rev: 52d090ab931e5cbeffc612b91c11dbb55db15297)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Applied two comments sent by Paul Eggleton.
(From yocto-docs rev: d3b61e07b5b9db6a582c76f66a984b9f27812a6f)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
These changes are basically Paul Eggleton's review comments.
(From yocto-docs rev: bb92dbb968013952c4308b9aeed48223f49c866d)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The final paragraph of the "Creating Your Own Distribution" really
should have been in list form and should have some cross-refs
for other parts of the manual. The paragraph is now in list
form and there are some references.
(From yocto-docs rev: 02c4b2e99a3237d1506887659be0e67d6b000648)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added a couple of notes to point out the ease of creating your
own distro and not just relying on a Poky distribution. One
note is at the very beginning of the manual and mentions
Angstrom as an example of a distro based on the YP. The
other note is at the beginning of the second chapter.
(From yocto-docs rev: 1525a5e34c615cbfd25aeb12cc7a27ef95b51eab)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added the "var-" part of links for the creating your own
distribution section.
(From yocto-docs rev: d419cd67084ce25d0d4b4437d8ce4cec180da59a)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This is needed since the mesa-dri recipes in oe-core got renamed to just
mesa.
[YOCTO #3385]
(From meta-yocto rev: 0aaada20aa7453f7a5d9342b7f26ff4fa8b044b2)
Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
mesa-dri has been renamed to mesa.
[YOCTO #3385]
(From meta-yocto rev: ba8d5b6dcb6fa4721e85b62f15713072cc0fa23f)
Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Due to quarks with the way bitbake handles variable key values, the
hard coded FILES_vte-dbg or automatic FILES_${PN}-dbg could replace
each other, leaving the system in an inconsistent state.
(From OE-Core rev: 7846f68537a942d340d5931e23a4fceb84b6edcb)
Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Rename mesa-dri recipes to just mesa. Also, replace all references to
mesa-dri in all recipes/configs.
The reason for this renaming (quote from bugzilla):
"mesa-dri is a artefact of mesa-xlib existing, which doesn't anymore.
mesa-dri should be renamed to mesa."
[YOCTO #3385]
(From OE-Core rev: c8bbb9983bcc7cfc5332e89c3e8148505b4ca83f)
Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The previous disk monitor is based on the disk, and one disk only can
have one action, now it is based on the path, so we remove the additional
comments from local.conf.sample.extended
[YOCTO #3995]
(From meta-yocto rev: 29c5de1feb144a768d6c60b8e5128b29091cf5a8)
Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Remove the duplicated SRCREV_pn-exmap-console.
[YOCTO #4064]
(From meta-yocto rev: c5c544876c6c0bcb088d6244aa3585d874d3559a)
Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
There are several duplicated lines in maintainers.inc, remove the
duplicated ones.
[YOCTO #4064]
(From meta-yocto rev: 389cd73a1294ec4f8e810bc42307f7e753f917a7)
Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
1. check if gcc_test is really generate before os.remove("gcc_test") to avoid
following error:
ERROR: Execution of event handler 'check_sanity_eventhandler' failed
Traceback (most recent call last):
File "check_sanity_eventhandler(e)", line 4, in check_sanity_eventhandler(e=<bb.event.ConfigParsed object at 0x3151450>)
File "sanity.bbclass", line 107, in check_sanity(sanity_data=<bb.data_smart.DataSmart object at 0x11ba110>)
File "sanity.bbclass", line 22, in check_gcc_march(sanity_data=<bb.data_smart.DataSmart object at 0x11ba110>)
OSError: [Errno 2] No such file or directory: 'gcc_test'
2. set result to False when build failed with -march=native to ensure
-march=native is appended to BUILD_CFLAGS when host gcc really supports this flag,
otherwise following error appears when build native packages.
| cap_text.c:1: error: bad value (native) for -march= switch
| cap_text.c:1: error: bad value (native) for -mtune= switch
(From OE-Core rev: 4a4228fe250c8b23a5deeb25825d61c6e84a47a2)
Signed-off-by: Zhenhua Luo <zhenhua.luo@freescale.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
routerstationpro is limited to 16mb flash size. Exceeding that size may
not be noticed immediately, which we don't want.
"The current latest kernel for the routerstationpro machine is far
beyond the 16MB of it's flash size [0]. I think it would be good to
[test if the size of the image is above that size]."
Setting this variable will enable the do_sizecheck task and produce an
error when the image is too large:
"ERROR: This kernel (size=90230265 > 16777216) is too big for your
device. Please reduce the size of the kernel by making more of it
modular."
[YOCTO #3514]
(From meta-yocto rev: bb25e15c62cdde749f34050933d056a79dd2d3c5)
Signed-off-by: Michel Thebeau <michel.thebeau@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
[Hob #4070]
- tweaked the spacing on info windows
- fixed text bolding in simple settings dialog
(Bitbake rev: 2ecb102968cdbbdbbfa91e1dcccf45bcd0b59a89)
Signed-off-by: Andrei Dinu <andrei.adrianx.dinu@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Implemented the search functionality for recipes and packages using
filters on the listmodel. I have used the design which can be found in
bugzilla.
[YOCTO #3529]
(Bitbake rev: b77166ad7b8571895f73a84f7789d93fbd4f6d04)
Signed-off-by: Cristiana Voicu <cristiana.voicu@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
For a custom image from scratch, the image version is not set and
it gives an error.
[YOCTO #4065]
(Bitbake rev: 43703f3eb5f71a117e6315fa5df91711653636a3)
Signed-off-by: Cristiana Voicu <cristiana.voicu@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
While GPT works fine when writing to actual media, it cannot be reliably
used for distributing disk images as it requires the backup table to be
on the last block on the device, which of course varies from device to
device. Use MSDOS tables instead.
Use mkfs to label the filesystems as msdos tables do not support
partition labeling.
(From OE-Core rev: 049ea1e0a6a1017a5020de38bd7ce93515bd62f4)
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Most firmware implementations use the EFI specified
EFI/BOOT/bootia32.efi (and similar) boot paths. Only broken firmware
uses different paths for removable media. In those cases, the user can
add their own startup.nsh.
For the compliant case, selecting "Shell" from the EFI boot menu should
go to the shell.
(From OE-Core rev: d031cdbf40231b8c103d78c69252bf9d584d0605)
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Without a reliable way of knowing if the target device with be an
asyncronous block device on the target (MMC or USB), err on the side of
caution of always specifcy "rootwait", ensuring the kernel will wait for
the device to appear and not abort if it hasn't appeared in time for
mount.
Document the remaining kernel parameters added by this script on the
same line as rootwait.
(From OE-Core rev: 5b6a6a3872fd341cf978be40c69707223e3c29df)
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
There is no need to boot with "rw". Booting with "ro" will allow for
fsck to be run during boot, and a proper /etc/fstab will still ensure
the rootfs is "rw" by the time the user can interact with the system.
Change the "rw" to "ro" in the kernel parameters specified in the
generated grub.cfg file.
Fixes [YOCTO 4036] mkefidisk.sh hardcodes 'rw' as root mount option
(From OE-Core rev: 960f0cbf85a4124adbc74d8b2ceb09a7d39ecc04)
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
Cc: Koen Kooi <koen@dominion.thruhere.net>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The current script only replaces an existing root= kernel parameter
which can result images created without a root= paremeter, even though
the script expects a target rootfs parameter.
Rather than replacing the root= parameter, delete the root= parameter if
it exists, then append an appropriate root= parameter.
Fixes [YOCTO 4035] mkefidisk.sh forgets to add root= parameter
(From OE-Core rev: e5dbec7e7d3bb29676280823b0337ad429c75120)
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
Cc: Koen Kooi <koen@dominion.thruhere.net>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
By inheriting gnome this package was build-depending on
gtk-update-icon-cache-native, gconf, gconf-native, shared-mime-info and
hicolor-icon-theme for no reason. Change this to inherit autotools pkgconfig to
reduce the build-dependencies.
Also, add a missing dbus-glib build-dependency that was previously pulled in
through something in the gnome class.
(From OE-Core rev: bde2c0ab1500976e2cb50f1526df04fb8b2cd408)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The tclibc file for uclibc already empties IMAGE_LINGUAS, so there's no point
to this conditional as far as I can tell, and it can cause issues for certain
values of TARGET_OS.
(From OE-Core rev: 0fdda5840452c7715ed775d5d18d9f850396f483)
Signed-off-by: Christopher Larson <chris_larson@mentor.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This was removed from package_rpm and package_ipk years ago, and shouldn't be
needed, installing the packages from package_linguas should be sufficient.
(From OE-Core rev: e9485c7077e5a9508371bbbbebdaaf1e9685da61)
Signed-off-by: Christopher Larson <chris_larson@mentor.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Coreutils does not depend on ACL but also does not disable it. Effect is
that from time to time I have a copy in sstate-cache which got built
with ACL and then I have problem while building images or sdk:
| Collected errors:
| * satisfy_dependencies_for: Cannot satisfy the following dependencies for packagegroup-core-standalone-hhvm-sdk-target:
| * libacl1 (>= 2.2.51) *
| * opkg_install_cmd: Cannot install package packagegroup-core-standalone-hhvm-sdk-target.
(From OE-Core rev: d54141130475b091358807dce17ba8d244d33ea1)
Signed-off-by: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The recursive parameter is set to True, the regex for the first call to
do_split_packages matches any path under ${libdir}/perl/${PV}/auto/, and
the .debug directories contain .so files, so each one was getting picked
up as a package. Change the regex to disallow dots in the path beneath
auto/ and thus avoid the .debug directories.
Fixes [YOCTO #4048].
(From OE-Core rev: f8f6992fe0f29db1cc4df15b7449e06188052041)
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Richard Purdie
Khem Raj
Scott Rifenbark
Laurentiu Palcu
Mark Hatle
Robert Yang
Zhenhua Luo
Michel Thebeau
Emilia Ciobanu
Andrei Dinu
Cristiana Voicu
Darren Hart
Ross Burton
Christopher Larson
Marcin Juszkiewicz
Paul Eggleton