| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
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>
|
| |
|
