linux/poky.git/meta/recipes-devtools/installer, branch 1.6_M5

adt_installer: fix issue with x86_64

2014-02-28T14:01:12+00:00

When the default tune for x86_64 was changed to core2-64, the environment setup script name did not contain x86 anymore. Hence, the adt_installer failed for x86_64. This commit contains a generic fix and is supposed to work with any kind of machine/tune setting. It's actually extracting the environment script name using 'opkg files meta-environment-MACHINE'. So, no need to do any other sort of searches. We know exactly which is the environment setup script for the specified machine. [YOCTO #5806] (From OE-Core rev: a88c386239ddc5816d9045d12cf6db4872fa86da) Signed-off-by: Laurentiu Palcu Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

adt-installer: Disable multilibs

2014-02-16T16:06:52+00:00

This recipe is pointless as a multilib and worse, it races agaist itself causing autobuilder failures. Disable the multilib case. (From OE-Core rev: e927e838cf2b4d6c2a55421f2db957dcfb186b8a) Signed-off-by: Richard Purdie

unfs3, unfs-server: Replace all instances of unfs-server with unfs3

2014-01-28T00:52:35+00:00

Other recipes dependencies and even some comments need to be updated for the removal of unfs-server and the replacement with unfs3. The unfs3 is a complete drop in replacement providing all the prior functionality of NFSv2 but also adding NFSv3. [YOCTO #5639] (From OE-Core rev: d577c56519a448b142da5b43e46d5bd9d3a3b4bd) Signed-off-by: Jason Wessel Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

adt_installer: do not install rootfs if target is not selected

2014-01-22T07:20:04+00:00

Currently, if YOCTOADT_TARGETS does not contain an architecture but the rootfs/machine settings are uncommented, then the rootfs is installed and adt will throw an error because is not able to find the toolchain environment script. This patch will: * not allow to install a target rootfs if the toolchain for the target architecture is not selected; * uncomment the target rootfs/machine settings for the other architectures since it's easier for the user to just add a new architecture in YOCTOADT_TARGETS and have the target rootfs installed; [YOCTO #5727] (From OE-Core rev: 22351d27de76b39cb71904396e73497e36d9e1d6) Signed-off-by: Laurentiu Palcu Signed-off-by: Richard Purdie

Update after toplevel LICENSE file checksum change

2014-01-02T14:21:04+00:00

(From OE-Core rev: bbd88aebcabbb19c27a7d752d4a5b8ad9ff9412e) Signed-off-by: Richard Purdie

adt-installer: tweak DESCRIPTION and add SUMMARY and HOMEPAGE

2014-01-02T12:50:24+00:00

(From OE-Core rev: 48bdfc957f1994f945ca46fd769e154c1d50f027) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

adt_installer: Fix missing autogen.sh error

2013-11-30T22:26:26+00:00

With the transition from svn -> tarball release, this issue was missed. Instead of using autogen.sh, we can call configure directly. [YOCTO #5606] (From OE-Core rev: 776e3b19160e5e1cceec1a8941c831be4d1f82b0) Signed-off-by: Richard Purdie

adt-installer: Switch from svn to tarball release for opkg

2013-11-24T12:25:36+00:00

(From OE-Core rev: 899fd09328a35228a5c96785131930b69ef19a49) Signed-off-by: Richard Purdie

adt-installer: add warning if MACHINE is not set in adt-installer.conf

2013-09-26T15:37:56+00:00

Since the MACHINE can now be specified in adt-installer.conf, in order to install the proper toolchain and environment script for the given machine, add a sanity checking at the beginning to make sure MACHINE is set for the wanted architecture. Also: * uncomment the x86 target variables, in adt-installer.conf, in order to have qemux86 MACHINE set, by default, and also the sysroot installed (since it doesn't make much sense to install the toolchain without a target sysroot); * remove 'sudo' when creating relocate_sdk_tmp.py because the file is created in adt-installer directory; [YOCTO #5259] (From OE-Core rev: 0623a0e1bd7cf0c405a0469e9f16779971c0c3b5) Signed-off-by: Laurentiu Palcu Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

adt-installer: check if sudo is needed when installing target sysroot

2013-09-26T15:37:56+00:00

Currently, if SDK is installed in a directory that needs sudo preivileges, the target sysroot is also installed with sudo, even though the location is in users's home directory. This patch reuses the ownership checking code and uses it to check if sudo is needed for target sysroot too. [YOCTO #5259] (From OE-Core rev: 5acfced041477d8c272485196e87ad601a0ce5b4) Signed-off-by: Laurentiu Palcu Signed-off-by: Saul Wold Signed-off-by: Richard Purdie