openembedded-core.git/meta/recipes-devtools/installer, branch dora

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

2013-09-26T15:37:13+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]

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:13+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]

Signed-off-by: Laurentiu Palcu 
Signed-off-by: Saul Wold 
Signed-off-by: Richard Purdie

adt-installer: fix opkg repo name

2013-09-14T07:20:32+00:00

I mistakenly named the allarch opkg repo the same as nativesdk one...

This patch fixes it.

[YOCTO #5181]

Signed-off-by: Laurentiu Palcu 
Signed-off-by: Richard Purdie

adt-installer: allow installation of other machines

2013-09-10T21:55:10+00:00

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]

Signed-off-by: Laurentiu Palcu 
Signed-off-by: Richard Purdie

adt_installer: allow specifying relative target sysroot paths

2013-08-02T04:57:53+00:00

If one specifies a relative target sysroot path, then he/she must always
be in the same directory in order to be able to compile.

With this patch, adt_installer will automatically convert user
supplied relative paths to absolute.

[YOCTO #4955]

Signed-off-by: Laurentiu Palcu 
Signed-off-by: Saul Wold

adt_installer_internal: fix spelling error

2013-07-22T05:13:25+00:00

s/envrionement/environment/

Signed-off-by: Beth Flanagan 
Signed-off-by: Saul Wold

populate_sdk_base.bbclass: use new perm option for find

2013-07-18T14:14:41+00:00

Old way find -perm +mode is no longer supported in newer
versions of find (Fedora 19). Man page says:
-perm +mode
       This  is  no  longer  supported  (and  has been deprecated since
       2005).  Use -perm /mode instead.

[YOCTO #4853]

Signed-off-by: Stefan Stanacar 
Signed-off-by: Saul Wold

adt_installer_internal:add sudo when permission deny on installation directory

2013-06-27T16:55:58+00:00

When the user doesn't have rights to access the installation directory,
the sdk installation will fail, add sudo to fix this.

[YOCTO #4760]

Signed-off-by: Hongxu Jia 
Signed-off-by: Saul Wold

adt_installer_internal:fix perl lib version mismatch

2013-06-27T16:55:58+00:00

When run "autoreconf" in toolchain, there is an error if the host's perl's
version is not the same as the one in the SDK, the error says that the
executable perl mismatches the perl lib's version.

This is because most of the autotools' scripts use the "#!/usr/bin/perl -w"
which is host perl, but the gnu-configize uses "#! /usr/bin/env perl" which
invokes the perl wrapper in the SDK, and the wrapper will set the PERL5LIB to
the SDK which causes the mismatch. We can make all the perl scripts to use the
host perl or the SDK perl to fix this problem.

[YOCTO #4758]

Signed-off-by: Hongxu Jia 
Signed-off-by: Saul Wold

adt_installer_internal: fix perl modules relocated failed on older distributions

2013-06-27T16:55:57+00:00

The perl module for automake has an embedded path in it, this needs
to be relocated.

Older versions of 'file' do not return the "ASCII" text in the output for
a perl module file. Hence, the regex pattern didn't match perl module and
they were not getting relocated at all on older distributions.

1) On CentOS release 6.4, the version of file is 5.04
$ file /usr/lib/perl5/Config_heavy.pl
$ /usr/lib/perl5/Config_heavy.pl: Perl5 module source text

2) On Ubuntu 13.04, the version of file is 5.11
$ file /usr/lib/perl/5.14/Config_heavy.pl
$ /usr/lib/perl/5.14/Config_heavy.pl: C source, ASCII text, with very long lines

[YOCTO #4550]

Signed-off-by: Hongxu Jia 
Signed-off-by: Saul Wold