summaryrefslogtreecommitdiffstats
path: root/meta
Commit message (Collapse)AuthorAgeFilesLines
* bitbake.conf/package: Collapse PKGDATA_DIR into a single machine specific ↵Richard Purdie2013-09-1413-79/+39
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | directory Currently we have a hierarchy of pkgdata directories and the code has to put together a search path and look through each in turn until it finds the data it needs. This has lead to a number of hardcoded paths and file globing which is unpredictable and undesirable. Worse, certain tricks that should be easy like a GL specific package architecture become problematic with the curretn search paths. With the modern sstate code, we can do better and construct a single pkgdata directory for each machine in just the same way as we do for the sysroot. This is already tried and well tested. With such a single directory, all the code that iterated through multiple pkgdata directories and simply be removed and give a significant simplification of the code. Even existing build directories adapt to the change well since the package contents doesn't change, just the location they're installed to and the stamp for them. The only complication is the we need a different shlibs directory for each multilib. These are only used by package.bbclass and the simple fix is to add MLPREFIX to the shlib directory name. This means the multilib packages will repackage and the sstate checksum will change but an existing build directory will adapt to the changes safely. It is close to release however I believe the benefits this patch give us are worth consideration for inclusion and give us more options for dealing with problems like the GL one. It also sets the ground work well for shlibs improvements in 1.6. (From OE-Core rev: 1b8e4abd2d9c0901d38d89d0f944fe1ffd019379) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* layer.conf: Version bump for DEPLOY_DIR layout changeRichard Purdie2013-09-141-1/+1
| | | | | | | | | Increase the version to signify the layout change of the images in the deploy directory. (From OE-Core rev: 4246e7dd59800a1d6c6d02c00f4e86eeac020767) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: include machine name in DEPLOY_DIR_IMAGEPaul Eggleton2013-09-143-2/+9
| | | | | | | | | | | | | | | | | | | This allows a clean seperation between image outputs from different machines, and makes it possible to have convenience symlinks to make the output ready to deploy. This did require some surgery in runqemu; if explicit paths to the image and kernel are not supplied then DEPLOY_DIR_IMAGE needs to be determined from bitbake or set in the environment. However the script does try to avoid requiring it unless it really is needed. Corresponding changes were made in the automated testing code as well. Based on an RFC patch by Koen Kooi <koen@dominion.thruhere.net> (From OE-Core rev: 7e90261aec61f79680b5eaeaf5b18c7b795412a4) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* icu-native: do_install: Segmentation faultRobert Yang2013-09-142-1/+32
| | | | | | | | | | | | | | | There was a "Segmentation fault" error when build icu-native when the TMPDIR is in a deep directory (for example, when len(readlink -f $TMPDIR == 410)), use LARGE_BUFFER_MAX_SIZE for cmd rather than SMALL_BUFFER_MAX_SIZE would fix the problem, this should be a misplay because other cmd uses LARGE_BUFFER_MAX_SIZE. [YOCTO #5171] (From OE-Core rev: ebfdddc23ff78231a819c62c8ffcced9633aa08b) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* perf: source should be ready after do_unpackRobert Yang2013-09-141-0/+3
| | | | | | | | | | | | | | | | | | | In perf.bb: S = "${STAGING_KERNEL_DIR}" So the source should be ready after the do_unpack, and we need this: do_unpack[depends] += "virtual/kernel:do_populate_sysroot" Otherwise, maybe no source after do_unpack. [YOCTO #5168] (From OE-Core rev: 01d3b15518b981199120b3b9c6923678244aefdc) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Stop providing ${P} and ${PF} by defaultRichard Purdie2013-09-141-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | For a long time we've provided PN-PV and PN-PV-PR by tweaking PROVIDES. This looks nice at first glance however it turns out to be a bit problematic. Taking make as an example where there are two versions, 3.81 and 3.82, what should "bitbake make-3.81" do? Currently it builds make-3.81 and make-3.82 and breaks in interesting ways. Is that a bitbake bug? Well, it certainly shouldn't try and run the build. Why is it building 3.82 though? Its due to finding a dependency on "make-dev" and then trying to figure out what provides it? The answer is "make" and the default version of "make" is 3.82. So arguably, finding "make-3.81" should infer PREFERRED_VERSION_make = "3.81". Doing so resolved the above problem since now "make" resolves to "make-3.81". So what about if we have Recipe A: DEPENDS = "make-3.81" and Recipe B: DEPENDS = "make-3.82" That is clearly an error, easy. So finally what about if we have Recipe A: DEPENDS = "make-3.81" and Recipe B: DEPENDS = "make" The first recipe infers the PREFERRED_VERSION_make = "3.81" and then forces that version on everything else. Is that desired? Probably not in most cases, at least not silently. As mitigation, we could print a WARNING about this happening. The final part of the problem is that we can ony figure this out within bitbake itself. That means we'd have to teach bitbake about the PN-PV format of PROVIDES which is breaking the separation between bitbake and the metadata. We can't win :(. Nobody that I know of is using or relying on this functionality so perhaps we should just remove it instead which is what this patch does. Opinions? (From OE-Core rev: a87c205bb6cefd5e1a41b8e7ef02b5bfa380e3b6) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate.bbclass: fix parallel building issueRoy.Li2013-09-141-1/+1
| | | | | | | | | | | | | | | | | | | | | | sstate_package creates hardlink from sysroot to SSTATE_BUILDDIR, then sstate_create_package will store SSTATE_BUILDDIR into a archive file by tar, but once other packages install the same file into sysroot, the creating the archive file will fail with below error: DEBUG: Executing shell function sstate_create_package tar: x86_64-linux/usr/share/aclocal/xorg-macros.m4: file changed as we read it This kind of error is harmless, use --ignore-failed-read to ignore it. The error in tar occurs when the timestamp of the file changes and this can happen when the number of symlinks change. The file will be included in the archive. [YOCTO #5122] (From OE-Core rev: 4b3e353a532c7b68b0bb86df4a2fcc44f8bb3ef2) Signed-off-by: Roy.Li <rongqing.li@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libnewt-python: Don't write a whiptail packageRichard Purdie2013-09-121-0/+1
| | | | | | | | | The whiptail package is written by the libnewt recipe so for the python version we need to ensure its not in PACKAGES. (From OE-Core rev: b26157a8b575aa7b5c96ffe782fc23ec0920311c) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* populate_sdk_rpm: Only remove trailing whitespace, not all whitespaceRichard Purdie2013-09-121-2/+2
| | | | | | (From OE-Core rev: 06cb4deba6e4df4ffe3015602d5997b26d28778b) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* weston: as weston-launch depends on PAM, control it with a PACKAGECONFIGRoss Burton2013-09-111-2/+4
| | | | | | | (From OE-Core rev: fb430271da67d7ec98c285a3420b00db737cae55) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* clutter: fix compilation when building without X11 backendRoss Burton2013-09-112-1/+59
| | | | | | | | | | | | | If Clutter is building the Wayland backend but not the X11 backend, the Cogl support doesn't get enabled so the Wayland backend (which uses it) fails to compile. Backport a fix from upstream to fix this situation. (From OE-Core rev: 6df36a004210901acceff4a201d0f910d99eccfe) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* x11vnc: add dependencies for xrandr/xfixes/xdamage/xtstRoss Burton2013-09-111-1/+1
| | | | | | | | | | | Inspired by a patch by Martin Jansa but with these libraries required, as a VNC server without them is suboptimal. Don't add an option for Xinerama as our X server always disables it. (From OE-Core rev: 4bca0b8adcac6eebc4466a2eea03de3493bf1cc4) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* populate_sdk_rpm: Ensure empty strings aren't passed to attemponly rpm codeRichard Purdie2013-09-111-2/+2
| | | | | | | | | If empty strings are passed to the rpm attemptonly code, it breaks. This ensures we don't do that. (From OE-Core rev: 6a0d5a3158608364f6baa11fe9ab7fa1f8e251ab) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* xf86-video-vmware: respect opengl DISTRO_FEATURERoss Burton2013-09-111-2/+2
| | | | | | | | | | | | | | Conditionalise the GL dependencies on the opengl DISTRO_FEATURE so this driver can build without the opengl feature active, as the configure script will enable/disable the GL sub-driver depending on the presence of these libraries. This is an interim patch to fix the autobuilder, a more complete patch heading upstream to make the GL sub-driver deterministic will follow. (From OE-Core rev: 66b7c59442cc494179418995292c57bab56fada3) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bluez4/5: Add EXCLUDE_FROM_WORLD = 1Saul Wold2013-09-112-0/+3
| | | | | | | | | | | | | | | We can't build both recipes in the world build as there is a collision of package name and PR values. Specificly the libasound-module-bluez which is the same in both goes backwards from r5 (bluez4) -> r0 (bluez5) and the subpackage_metadata check fails: ERROR: Recipe lib32-bluez5 is trying to change PR from 'r0' to 'r5'. This will cause do_package_write_* failures since the incorrect data will be used and they will be unable to find the right workdir. [YOCTO #5165] (From OE-Core rev: 3653500c7e5d365ddc2868d985c6001d40123672) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* xf86-video-intel: disable DRI2 tests if no DRI2 is availableRoss Burton2013-09-112-0/+52
| | | | | | | | | | Somehow this slipped past the initial testing and can cause build errors in non-GL distros. (From OE-Core rev: 975412f446066215a94be78a7f7e1db9e28ebbbf) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* xf86-video-vesa: change depends to refect realityRoss Burton2013-09-111-4/+1
| | | | | | | | | | | This recipe appears to have been a copy-and-paste from -intel, because it has dependencies and configure options that xf86-video-vesa just doesn't have, such as virtual/libgl and XVMC. (From OE-Core rev: 4995acafc139107c2323da69eca718009384efe4) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ia32-base: only depend on GL if opengl DISTRO_FEATURE enabledRoss Burton2013-09-111-3/+3
| | | | | | | | | | | As Mesa refuses to compile if the "opengl" DISTRO_FEATURE isn't enabled, mesa-driver-i9xx and the GLX X module have to be conditional in the ia32 machine defintion too. (From OE-Core rev: 8b5c07e6c3b492f56ce9c5f99a732793403d6b36) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* lib/oeqa/runtime: smart: limit channel add to useful onesStefan Stanacar2013-09-111-1/+3
| | | | | | | | | | | Don't add inappropiate channels on the target. This happens when building two different machines in the same dir and then running the tests for each machine. (From OE-Core rev: 9e4e475b598f6b9bd2b653c72a1c1d5bd5c0b8c9) Signed-off-by: Stefan Stanacar <stefanx.stanacar@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* classes/package_rpm: remove unsed outdir variableStefan Stanacar2013-09-111-2/+1
| | | | | | | | | Not only outdir had the wrong value, it wasn't used actually used in that function. (From OE-Core rev: 5db4b53e5d969a6da314904fa2335462947c97ea) Signed-off-by: Stefan Stanacar <stefanx.stanacar@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ptest-runner: trivial fixes and refineRoy Li2013-09-111-7/+23
| | | | | | | | | | | | | | | | | 1. ptest files may be installed under /usr/lib64/ for 64bit filesystem or under /usr/lib/ for 64bit multilib filesystem, so we should check both directories 2. If a soft link is linking to a directory under the same directory, we only run once. [YOCTO #5125] [YOCTO #5126] (From OE-Core rev: 51c43e08b388ed15520c66977bbb49df18e5f124) Signed-off-by: Roy Li <rongqing.li@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libcroco: disable Bsymbolic if it is not supported on some hostsTing Liu2013-09-111-1/+1
| | | | | | | | | | | | | | | | | | | | When trying to build on my Centos 5.5 machine, got below error: | checking for gtkdoc-mkpdf... no | checking whether to build gtk-doc documentation... no | checking for CROCO... yes | checking if gcc supports "-Wl,-Bsymbolic-functions" flag... | configure: error: -Bsymbolic requested but not supported by ld. Use --disable-Bsymbolic to disable | Configure failed. The contents of all config.log files follows to aid debugging | | configure: exit 1 | ERROR: oe_runconf failed Set --enable-Bsymbolic=auto to disable it when it is not suppported. (From OE-Core rev: e7c691b33573b3309752d6eb397486c2c8620adb) Signed-off-by: Ting Liu <b28495@freescale.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python-smartpm: Add an attempt install modeMark Hatle2013-09-113-5/+62
| | | | | | | | | | | | | | [ YOCTO #3723 ] Add a mode to smart that will allow an installation to continue, instead of failure in the case that one or more items is uninstallable. Uninstallable packages are simply ignored, and no error is generated. (From OE-Core rev: bdf07b1698d228dc7ff555199a269b1ff8ceca19) Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* uclibc: Add missing DEPENDS on kern-tools-nativeRichard Purdie2013-09-112-2/+3
| | | | | | | | This is needed for the kconfig handling and the merge-config.sh script. (From OE-Core rev: 1c34b0e871e475a90e27d338469ba31f322d5300) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* image/populate_sdk: Ensure symlinks in target sysroot are relativeRichard Purdie2013-09-111-1/+6
| | | | | | | | | | | | In the target sysroot of an SDK we can have target system absolute links which don't make sense. This adds a script which fixes them up to become relative paths instead. [YOCTO #5020] (From OE-Core rev: 57d6bdcad55c119e9ab8089d23d462436a0e4440) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemu: only depend on mesa-driver-swrast if opengl is enabledRoss Burton2013-09-113-3/+3
| | | | | | | | | | As Mesa refuses to compile if the "opengl" DISTRO_FEATURE isn't enabled, mesa-driver-swrast has to be conditional in the QEMU machine defintions too. (From OE-Core rev: 9951e1da6a755f9a46d3a595aa4c2f975aee8f46) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* init-live.sh: distinguish between a read-only image and a read-write imageChen Qi2013-09-111-11/+18
| | | | | | | | | | | | | | | | | | | | | | | The iso and hddimg share a common concept of 'live image', and they use the same initramfs and thus the same init. However, that init script in initramfs made a wrong assumption that the rootfs image was read-only by itself. This is apparently not true for hddimg. To make things work as expected, this init script should at least distinguish between a read-only rootfs image and a read-write one. This patch adds this ability to the init script. After this change, the init script would be able to check whether the rootfs image is read-only or not. If the rootfs image is read-write, the image will be mounted and then booted directly. No union mounts will be attempted in this case. [YOCTO #5164] (From OE-Core rev: 29f869b68a9017502f75915784a924f0fe9d4be1) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* midori: excluded from mips64 temporarilyKai Kang2013-09-111-0/+4
| | | | | | | | | | | | Exclude midori from mips64 temporarily. Becuase midori depends on webkit-gtk which could not build for mips64 with 64bits userspace now. [YOCTO #5141] (From OE-Core rev: 1b0602b5933b3ee8e4ae36d447bf881308528a47) Signed-off-by: Kai Kang <kai.kang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* systemd.bbclass: get the correct /lib directorySaul Wold2013-09-101-3/+3
| | | | | | | | | | | By using os.path.dirname(systemd_unitdir) we get the correct /lib directory instead of dealing with possibly multilib directories. This address a QA Error for shipped/not installed /lib with multilib and x32. (From OE-Core rev: 5b451a46550ba62e2fbfe5dbe50723b34a4fd527) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* systemd: Remove base_libdir if installed only for systemd_unitdirMuhammad Shakeel2013-09-101-0/+3
| | | | | | | | | | | | | | | | | | | If a recipe installs systemd_unitdir and it is a non-systemd build than systemd.bbclass deletes systemd_unitdir (/lib/systemd/) but not base_libdir (/lib). In this case if base_libdir is empty than following QA Issue is reported. ERROR: QA Issue: openssh: Files/directories were installed but not shipped /lib If base_libdir was installed due to systemd_unitdir installation than for non-systemd build it should also be removed. (From OE-Core rev: c700cb21c189e23a78f0efaaf763259c8cfefa4d) Signed-off-by: Muhammad Shakeel <muhammad_shakeel@mentor.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* nfs-utils: Add systemd supportMuhammad Shakeel2013-09-105-2/+95
| | | | | | | | | | - Remove dependency on meta-systemd (From OE-Core rev: 644394c074c359505fcd750356fb4db58b939729) Signed-off-by: Muhammad Shakeel <muhammad_shakeel@mentor.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rpcbind: Add systemd supportMuhammad Shakeel2013-09-103-1/+32
| | | | | | | | | | - Remove dependency on meta-systemd (From OE-Core rev: 3ecb5e21b3b4f05f2d527264c3574fdc37984a77) Signed-off-by: Muhammad Shakeel <muhammad_shakeel@mentor.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* lighttpd: Add systemd supportMuhammad Shakeel2013-09-102-1/+23
| | | | | | | | | | - Remove dependency on meta-systemd (From OE-Core rev: 36e3d63abaeafc5d2e671bad45b599c159ed10ab) Signed-off-by: Muhammad Shakeel <muhammad_shakeel@mentor.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* openssh: Add systemd supportMuhammad Shakeel2013-09-104-2/+47
| | | | | | | | | | -Remove dependency on meta-systemd (From OE-Core rev: 6e6445d487c033913a29763f8e3a7a339d5b612d) Signed-off-by: Muhammad Shakeel <muhammad_shakeel@mentor.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* avahi: use correct names in SYSTEMD_SERVICE_* variablesRoss Burton2013-09-101-2/+2
| | | | | | | | | | | | Don't hard-code full package names in SYSTEMD_SERVICE_*, because in multilib they'll be changed. [ YOCTO #4803 ] (From OE-Core rev: 013cc8b6397c29e8f0d7adf63d8e06caab778da2) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* dbus-ptest: fix populate_sdk errorMaxin B. John2013-09-101-0/+1
| | | | | | | | | | | | | | | | | | When we enable "ptest", populate_sdk fails with the following error: # bitbake core-image-minimal -c populate_sdk .. Collected errors: * satisfy_dependencies_for: Cannot satisfy the following dependencies for dbus-ptest-dev: * dbus-ptest (= 1.6.10-r0) * * opkg_install_cmd: Cannot install package dbus-ptest-dev. Disable that dependency. (From OE-Core rev: a59b7341d136bf8ee4a22c2968ca95dc17be3947) Signed-off-by: Maxin B. John <maxin.john@enea.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* initscripts: filter out empty lines from volatiles in check_requirements()Ming Liu2013-09-101-2/+2
| | | | | | | | | | So far the rules of check_requirements() is too strict to lead mismatch when empty lines exist in volatiles. (From OE-Core rev: 71ab9ee58b0ba5e3f5cbf403d1b8fb79fc7f5ed1) Signed-off-by: Ming Liu <ming.liu@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* btrfs-tools: fix a parallel build issueRoy Li2013-09-102-0/+31
| | | | | | | (From OE-Core rev: 637e0484ea4e7a39ac4d9c407c585201e6be1bc0) Signed-off-by: Roy Li <rongqing.li@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* mount.sh: automount cdrom device even if no ID_FS_TYPE availableChen Qi2013-09-101-1/+5
| | | | | | | | | | | | | | | | | | This script was modified to check whether $ID_FS_TYPE is empty before automount, however, for cdrom devices on qemu, the ID_FS_TYPE is not set, yet the device should be mounted. Otherwise, when booting an iso image with runqemu, the boot process hangs at 'waiting for removable media'. This patch fixes this problem by first checking whether the block device is a cdrom. [YOCTO #4487] (From OE-Core rev: 2df21a3b27543df912a3ce05bef2415fae13cb7c) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gstreamer-plugins: Change anonymous python structureSaul Wold2013-09-101-4/+6
| | | | | | | | | | | | This change ensures that the SRC_URI is set before base.bbclass code is called. This will also ensure that the xz-native depends is set correct. [YOCTO #5127] (From OE-Core rev: 787335494dc0a3f93d9bf5a6cf1b603c8675df66) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cmake.bbclass: ensure CMAKE_SYSTEM_NAME is correctSaul Wold2013-09-101-1/+1
| | | | | | | | | | | | Using TARGET_OS can add the ABIEXTENSION so ensure that is is removed for the Linux TARGET_OS, we might have other TARGET_OSes so don't hard code CMAKE_SYSTEM_NAME [YOCTO #5145] (From OE-Core rev: 7d8b700242b1b32c6b6d0735b497701800f54fc4) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* adt-installer: allow installation of other machinesLaurentiu Palcu2013-09-105-40/+42
| | | | | | | | | | | | | | | | | | | | | | | | | Currently, adt-installer allows only the installation of qemu target sysroots. The changes in this patch do the following: * add a new setting in adt-installer.conf (YOCTOADT_TARGET_MACHINE) for each target architecture. For example, for arm we can choose to use a qemuarm sysroot or a beagleboard sysroot. By default, only the qemu target sysroots are selected (current behavior); * change adt_installer scripts to allow installing the correct meta-environment package for the selected machine; * remove some left-over commented lines; * use packagegroup-cross-canadian-${MACHINE} when installing the cross canadian packages instead of doing it separately for each package; * change the opkg config files in order to be able to find the packagegroup package, which is allarch; [YOCTO #4783] (From OE-Core rev: 02085d410bf734e833d45293f4d5b06bb9536a60) Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta-toolchain-qt: include the proper cross-canadian packageLaurentiu Palcu2013-09-101-1/+1
| | | | | | | | | | | | packagegroup-cross-canadian package name was changed to contain MACHINE. Make the necessary changes here too. [YOCTO #4783] (From OE-Core rev: 8f8cd338faf63f665c2214f0110b712736f8ed5d) Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* populate_sdk_base.bbclass: select the proper cross-canadian packageLaurentiu Palcu2013-09-101-1/+1
| | | | | | | | | | | | Since packagegroup-cross-canadian package name has MACHINE in it, make the necessary changes here. [YOCTO #4783] (From OE-Core rev: 23531590d40acde2775b7c3b90682edc501d68f4) Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* packagegroup-cross-canadian: change package name to include MACHINELaurentiu Palcu2013-09-101-8/+5
| | | | | | | | | | | | | | | Since meta-environment package name was changed to contain MACHINE, change packagegroup-cross-canadian package name too, in order to be able to select the proper environment files for a certain machine. Also, remove the RPROVIDES since adt-installer doesn't really need it. [YOCTO #4783] (From OE-Core rev: d713447dc2fab8900f47c542cfbbb76bad19a7e2) Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta-environment: change package name to include MACHINELaurentiu Palcu2013-09-101-1/+1
| | | | | | | | | | | | | | | | | Currently, the package name contains just the TRANSLATED_TARGET_ARCH. When compiling the toolchain for two machines, belonging to the same architecture (for example: qemuarm and beagleboard), this package gets overwritten and adt-installer repo will contain just one meta-environment package... This leads to situations like installing the toolchain for qemuarm and end up with meta-environment package with beagleboard cpu options. [YOCTO #4783] (From OE-Core rev: 09a2b158818e2ec3c3e3b53b6d14fd3527c32c99) Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto/3.10: bump kver to 3.10.11Bruce Ashfield2013-09-103-16/+16
| | | | | | | | | | | | | | | | | | Bumping to the 3.10.11 -stable release. Of note in this update is the timer_list fix, which broke ssh access in the previous 3.10 series of updates: timer_list: correct the iterator for timer_list commit 84a78a6504f5c5394a8e558702e5b54131f01d14 upstream. With this, we can revert the two temporary fixes for timer lists. ssh access has been directly tested after this update. (From OE-Core rev: 659528f0f99cec94991ec96fa124c4497237e9f8) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* u-boot, u-boot-fw-utils-cross, u-boot-mkimage: Upgrade to 2013.07Otavio Salvador2013-09-1015-504/+47
| | | | | | | | | | | | | | | | | | | | | This upgrades the U-Boot based recipes for 2013.07 release. This removes the 2011.03, 2011.06 and 2013.01.01 versions so we keep a single one in core. The following recipes has been upgraded: - u-boot (remove old versions) - u-boot-mkimage (remove old versions) - u-boot-fw-utils -> u-boot-fw-utils-cross (renamed and reworked) The u-boot-fw-utils-cross recipe has been reworked as it uses the UBOOT_MACHINE to find default environment for use so it is indeed a cross binary and not a native one. (From OE-Core rev: c5fff5748e0aaf7e135fdd464c2104b1d3cbfd5a) Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* systemd: Fix build with multilibKhem Raj2013-09-101-1/+1
| | | | | | | | | | | | rpm macros should be independent of libdir Fixes errors seen when multilib is turned on it shows up since then libdir != usr/lib (From OE-Core rev: 6126c6e4b9c40c222519914c8fe0a51f9eee8d41) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* systemd: update patch header and commentsRoss Burton2013-09-101-2/+7
| | | | | | | | (From OE-Core rev: 856f74db0f56e4885af625665f8d85841f198e8d) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-11-14 15:34:25 +0000