| Age | Commit message (Collapse) | Author |
|---|
|
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Add a dynamic BBFILES pattern so that patches for openembedded-layer
are conditionally applied only if meta-oe is present.
Signed-off-by: Sinan Kaya <okaya@kernel.org>
Signed-off-by: Joshua Watt <JPEWhacker@gmail.com>
|
|
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
This converts the layer to the new override syntax. This was done using
<oe-core>/scripts/contrib/convert-overrides.py <this-layer>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Disables debuginfod when using MingGW. This feature brings in
unbuildable dependencies and can't be used.
Signed-off-by: Joshua Watt <JPEWhacker@gmail.com>
|
|
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Certain recipes require the "glibc-utils" recipe to include Glibc utility tools.
However, the native version is incompatible with the Windows host, and thus these
recipes will cause the Windows SDK to fail to build, particularly the kernel
development recipes.
[YOCTO #14286]
Signed-off-by: amann <anmolbir.mann@windriver.com>
Signed-off-by: dreyna <david.reyna@windriver.com>
Signed-off-by: Joshua Watt <JPEWhacker@gmail.com>
|
|
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Set SDK_VENDOR to '-w64', which makes the host triplet match what GCC
expect to find when using mingw32-w64. This enables features that are
not functional in the classic mingw32, but have been implemented in the
mingw32-w64.
Disable 32bit libs from the runtime component when compiling for 64bit,
which were enabled as a side effect of the GCC config change.
Signed-off-by: Samuli Piippo <samuli.piippo@qt.io>
Signed-off-by: Joshua Watt <JPEWhacker@gmail.com>
|
|
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Adds the framework for testing SDKs that ties into the oeqa test
framework. This allows commands like:
$ bitbake -c testsdk ...
to be run for MinGW SDKs.
The test framework currently executes all tests under Wine in lieu of
having access to actual Windows machines.
[YOCTO #13020]
Signed-off-by: Joshua Watt <JPEWhacker@gmail.com>
|
|
Use the winpthreads library available in the mingw64 and
change the thread model from win32 to posix to get access
to c++11 features.
Signed-off-by: Samuli Piippo <samuli.piippo@qt.io>
Signed-off-by: Joshua Watt <JPEWhacker@gmail.com>
|
|
GCCPIE defaults to "--enable-default-pie" in security_flags.inc,
which breaks Windows binaries.
Signed-off-by: Samuli Piippo <samuli.piippo@qt.io>
Signed-off-by: Joshua Watt <JPEWhacker@gmail.com>
|
|
Fix below problem:
MACHINE=intel-x86-64
SDKMACHINE = "i686-mingw32"
bitbake freetype
do_compile failed with below error:
x86_64-wrs-linux-libtool: compile: x86_64-wrs-linux-windres
--include-dir=work/corei7-64-wrs-linux/freetype/2.9.1-r0/recipe-sysroot/usr/include
/work/corei7-64-wrs-linux/freetype/2.9.1-r0/freetype-2.9.1/src/base/ftver.rc
-o work/corei7-64-wrs-linux/freetype/2.9.1-r0/build/.libs/ftver.o
work/corei7-64-wrs-linux/freetype/2.9.1-r0/build//x86_64-wrs-linux-libtool:
line 1752: x86_64-wrs-linux-windres: command not found
we don't want to use windres for target build, only export WINDRES/RC when build
SDK. SDK_OS = "mingw32", so use this override to fix it.
Signed-off-by: Changqing Li <changqing.li@windriver.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
|
|
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
We need to set this so that the override for nativesdk builds using MinGW don't
think they're using glibc.
Signed-off-by: Ross Burton <ross.burton@intel.com>
|
|
Signed-off-by: Ross Burton <ross.burton@intel.com>
|
|
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
|
|
The MinGW runtime doesn't provide libintl, so set gettext as the preferred
provider for libintl.
Signed-off-by: Ross Burton <ross.burton@intel.com>
|
|
Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
|
|
Use explicit mingw32 override for
PREFERRED_PROVIDER_virtual/nativesdk-${SDK_PREFIX}libc-initial
to avoid multiple providers and consequently broken builds.
Allow building static libraries, disabled by default.
Signed-off-by: Juro Bystricky <juro.bystricky@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
WINDRES and RC values are exported when building for a mingw32 target. These
values, due to being exported, end up in the signature hash for everything in
the system. By adding these to the whitelist we prevent contamination and
allow the system to properly reuse existing -native and other sstate-cache.
Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
We need to ensure that WINDRES searches the correct include directory
for header files. Now that a default sysroot is specified to an invalid
location, it highlights that we need to specify the location manually and
explictly.
autotools appears to use "RC" in preference to "WINDRES" so we need
to export that to ensure it doesn't just find the utility and use it
without an include directory.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
mingw builds use WINDRES so export this tool in the same manner as the other
tools for mingw builds.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Nowadays this is already set in OE-Core, in tcmode-default.inc.
Fixes:
WARNING: Variable key
PREFERRED_PROVIDER_virtual/${SDK_PREFIX}binutils-crosssdk
(binutils-crosssdk-${SDK_ARCH}) replaces original key
PREFERRED_PROVIDER_virtual/x86_64-oesdk-mingw32-binutils-crosssdk
(binutils-crosssdk-${SDK_ARCH}).
Signed-off-by: Jacob Kroon <jacob.kroon@mikrodidakt.se>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Adding the SDKTAROPTS can result in either a failure or an endless loop when
generating the SDK tarball. This is due to potential recursive symlinks
within the cross compiler directory structure.
It also means files from places /var/log on the build system can be pulled
into the sdk, dependning on the chosen rootfs of the target system this
is built against.
Disabling it is therefore the best opton, when post processing the tarball,
the symlinks can be dealt with accordingly but the current approach is just
dangerous.
Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
|
Richard Purdie
Sinan Kaya
Joshua Watt
amann
Samuli Piippo
Changqing Li
Ross Burton
Mark Hatle
Juro Bystricky
Jacob Kroon