Age | Commit message (Collapse) | Author |
|
uninative changes the location of the IBM850 codepage used by mcopy. So
make sure to set GCONV_PATH to the correct location when using
uninative.
Signed-off-by: Randy Witt <randy.e.witt@linux.intel.com>
|
|
Set a variable so other metadata can easily tell where uninative is
located.
Signed-off-by: Randy Witt <randy.e.witt@linux.intel.com>
|
|
Use uninative by default, not least to benefit from sstate cache reuse on
the autobuilders.
(From meta-yocto rev: a7b6eeb96e3bd2e8865224204c674e148b1cfa46)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Upgrades to stable LINUX_VERSION 4.4.3
(From meta-yocto rev: 85c4b7b831f2d33fe44f0742df623607250fe5e4)
Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Upgrades to stable LINUX_VERSION 4.1.18
Also fixes booting core-image-lsb since it needs preliminary graphics support 4.1
[YOCTO #9139]
(From meta-yocto rev: cbb7dc64e8c150c920e5cc1d66b7efafd517ecb5)
Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
uninative needs to adjust NATIVELSBSTRING fairly late in the
configuration parsing process but the sstate code encodes it into
variables. Since this string doesn't vary on a per recipe basis, we
defer its expansion until usage time.
(From OE-Core rev: 7b949f5f55b0cece0cc091c2f0492f91b0e3df96)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
(From OE-Core rev: c81fc055b7f817ba14eee93a7748ad2b1568290f)
Signed-off-by: Andre McCurdy <armccurdy@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
In the class-target case the code uses prelink-rtld so add the missing
DEPENDS.
(From OE-Core rev: eac7dcaabc2a5ff9e399feeee1348d71b4b5f68e)
(From OE-Core rev: 211db79747ea9e2728f6606d81d849b214531424)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
When musl is in use, GLib binaries crash on assertion failures under qemu
(From OE-Core rev: a9aa952ed8e67a3ee1e97d8840371adb0b4d4a9a)
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Previous, two things were wrong:
1) lib_basename was set from STAGING_LIBDIR only if prefix parameter was empty or missing
2) if prefix was not empty, lib_basename reverted to sys.lib, even if STAGING_LIBDIR
should've overriden it
(From OE-Core rev: e9f607dea216c8dffcdd00e3810f953d21946fb5)
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Inheriting distutils-base takes care of that.
(From OE-Core rev: 67f31f3b8d532fb53a005000f945ab0f465a15b6)
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
x32 isn't supported by user mode qemu so we can't build
gobject-introspection-data, so disable it in this case.
(From OE-Core rev: 4ee1eb8ddd3fbe144fbaeb32e07b66e191aa7548)
(From OE-Core rev: 700cf0d128980a8153c8483c6b73a139228e563a)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
(From OE-Core rev: d912d266bb10ca477ac89b369790eeb566e131b8)
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
(From OE-Core rev: 8d1c1494ced3c4a62c51644458ad53e04e66edbd)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
'inherit gobject-introspection' is added to each gnome-related recipe as needed.
(From OE-Core rev: 5729ecc4bc046c65b1b7a0fa8c0bec507107f4c4)
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
recipes
Previously native vapigen was provided via a symlink to target sysroot
which was causing build issues.
(From OE-Core rev: cc9b8ab36f927523e51f70d1b71d08f30fb229cd)
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
(From OE-Core rev: 3ae5c78818c26d9db95eae4680324f7153bd3d7c)
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
(From OE-Core rev: a6b7394d5218a25f9b5e574b97c4a75e3df95522)
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
(From OE-Core rev: b985f72624af2571b37f112344f82c6f64af7384)
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
(From OE-Core rev: 61fc0a8483b951ef0231d323efdc49135f363fa4)
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
DISTRO/MACHINE_FEATURES_BACKFILL
This means that introspection data will be generated using qemu by default.
If this causes trouble (qemu does not always emulate target architectures
perfectly), then add
MACHINE_FEATURES_BACKFILL_CONSIDERED = "gobject-introspection-data"
to machine configuration or
DISTRO_FEATURES_BACKFILL_CONSIDERED = "gobject-introspection-data"
to distro configuration.
(From OE-Core rev: 7e135aac58071e521db0f296658f54f31c42f27c)
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
This allows easy testing of introspection for example using
http://python-gtk-3-tutorial.readthedocs.org/en/latest/introduction.html
(From OE-Core rev: 7f2825f9e02baa4bc62bb11ad4dae821fb772106)
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
(From OE-Core rev: 0d2e5a47e9ac5452cfbe62a2014641c3503d1974)
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
This also requires various tweaks to recipes that depend on this class, which are included in this commit as well.
One of those tweaks is that pygobject is finally updated to the latest upstream release.
(From OE-Core rev: 70f11b0c9a348de86a0f05437ab54dcca1e23f74)
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
(From OE-Core rev: c783f1b607b923042b182d30cd93193e710278a6)
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
(From OE-Core rev: a5027eb94bbf714bc3599087a040a50be2386772)
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
(From OE-Core rev: f3a3e9d03f1e704ff8ae831bcad301a3a2af3f93)
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
We need to make sure that our fixed vapigen.m4 is used instead.
(From OE-Core rev: af77cb87e21b9419709b6b2485af25ccba3d12f8)
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
(From OE-Core rev: 04dfb5ca2a395978e5730104d759c22ab2106627)
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
(From OE-Core rev: a7034ac541a77c791a1decd33ecd0ae38a6f5209)
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
(From OE-Core rev: 0da45a6a38580d2e89bcddf10f392a21c5dd1b43)
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
(From OE-Core rev: ebd9339ba1b2ece5663f42d52ee977015295162b)
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
(From OE-Core rev: 1a6f3a5f2a9b8c315bcf78ef15f15a9656568f46)
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
(From OE-Core rev: e294c4307eeb0b6533b7f9b1603378e0daf7cbb1)
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
(From OE-Core rev: 5b58f229696754ef69479284c811939cf12c9cae)
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Now that gobject-introspection is supported, generation of .vapi
files for develeloping Vala code against gobject-based libraries
should be supported as well.
(From OE-Core rev: c3b1d234e8aa7c964ec3f186d713cf420ec1f8d9)
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
(From OE-Core rev: 87e11e73ba1fdaa576e47bb1fa15abde926705e8)
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
python-pygtk hasn't been updated in several years, is incompatible
with the current version of pygobject, and is generally obsolete as
all modern python gtk apps use introspection directly.
(From OE-Core rev: 1ccf6cc7b12a4cf65c0cb7f44344e3f578e09f0d)
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
python-pygtk is removed in a separate commit; the reasons for
that are explained in that commit's message.
(From OE-Core rev: 1a38e31c091c65e1118d7ba85cf1eb4f503ffcc3)
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
In python 3.4 python-config was rewritten in shell, ironically
to support cross-compilation:
https://bugs.python.org/issue16235
This new shell version is broken in several ways, and doesn't
have our oe-specific tweaks. Let's revert to the old script,
which is still provided.
(From OE-Core rev: e145257b979a57a279f9b3fd66baca420a240929)
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
(From OE-Core rev: 0bc30b4ccc3a90e5413faf74be94d351abf17ce5)
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
As we provide the full introspection support, we need to remove
the stubs from this package that conflict with it.
(From OE-Core rev: 22ef0b1722715c19e5d0a45a6a58176ec5f7f8fa)
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
The recipe has comments that explain what is going on and why.
Also, there are patches necessary to make it work in Yocto cross-compilation environment;
they will be submitted upstream.
(From OE-Core rev: c405abec95c05e647a7f78a28570651eefa97c0b)
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
The class had qemu_run_binary() which was not suitable for gobject-introspection,
as it required the name of the binary to run.
qemu_wrapper_cmdline() returns just the command line string needed to run
binaries, and does not require the binary name.
(From OE-Core rev: 24861ac849aa416664eda85572025d99d27e0156)
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
The previous attempt at soft-failing when uninative was enabled didn't actually
work, because the workers didn't evaluate the function that actually enabled
uninative.
In a BuildStarted handler we can check if we need to download or extract the
uninative tarball.
In a ConfigParsed handler on the workers we can check if the uninative loader is
present, and if so enable it.
(From OE-Core rev: 6e7b3c9889dbb77cd75106c124d9b01aabc8027b)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
uninative has some specific setup requirements. Rather than have everyone
doing this themselves, do this centrally and allow people to opt into it
based on some Yocto Project builds of the uninative tarballs.
(From OE-Core rev: c86b4b5af8b3942ff051605722abd418484370a6)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Prelinking on x86-64 wasn't working out the box as it uses /lib and
not /lib64 for libs. Prelink was refusing to link as the dynamic loader
didn't match its idea of the right path. Passing in the --dyanmic-linker
option avoids this.
We can share code from image-mklibs so abstract that into a new class,
linuxloader.bbclass.
This does break prelinking of multilib images, I've opened a bug so we
can loop back and fix that problem, the code would need to iterate the
dynamic loaders (and setup ld.so.conf files for it).
(From OE-Core rev: b3cc8304922ffbc945dcab208e467946f047ed4a)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Prelink contains some hardcoded assumptions about the path layout of
the target system. Unfortunately if the system doesn't match, prelink
doesn't work. This breaks:
a) prelink of those images
b) the unsafe-references-in-binaries QA test (which uses prelink-rtld)
One way to work around this is to construct an ld.so.conf file which
lists the library paths in question. We do this in sanity QA check and
in the rootfs prelink code, being careful not to trample any existing
target ld.so.conf.
There is an additional problem that $LIB references in RPATHs won't be
handled correctly, I've not see any system use these in reality though
so this change at least improves things.
(From OE-Core rev: 666b124645523d338caf115733a1258443b322c4)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
When installing the eSDK, if setscene task fail for some reason, the tests
would ignore this. This is bad since we assume they're working.
This adds some sanity test code which detects if setscene tasks are
needing to run and errors if there are any.
(From OE-Core rev: 16d8bb9e33272dd90722d1cc9d17adcfe9bc0c68)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
(From OE-Core rev: aa73c6f8e840ad134a93016eb42ab5007b1dc23c)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|