From: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
To: fdk17 <fdk17@ftml.net>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [meson][PATCH] meson: Allow for llvm-native tools to be used
Date: Fri, 27 Dec 2019 12:03:17 +0000 [thread overview]
Message-ID: <54a01022886647f9baa8608f8a6af5b1@XBOX03.axis.com> (raw)
In-Reply-To: <1758bd87-e492-46bc-8aaa-514e802c5030@www.fastmail.com>
[-- Attachment #1: Type: text/plain, Size: 2188 bytes --]
If we're adding a --native-file, shouldn't it always be specified, regardless of --cross-file?
Also, it looks as most of what is currently done in override_native_tools() and meson_do_configure_prepend_class-native() could be moved to the native-file (the exception seems to be the unsetting of CPPFLAGS, CFLAGS, CXXFLAGS and LDFLAGS).
//Peter
From: openembedded-core-bounces@lists.openembedded.org <openembedded-core-bounces@lists.openembedded.org> On Behalf Of fdk17
Sent: den 25 december 2019 12:49
To: openembedded-core@lists.openembedded.org
Subject: [OE-core] [meson][PATCH] meson: Allow for llvm-native tools to be used
I created a bbappend to build the LLVM recipe so that all the libraries were available for use on the host.
These libraries are then used by a host/sdk tool to prepare binary files for use by an application on the target.
When building our tool using meson it wasn't able to find the Yocto built LLLVM libraries.
This fixes the issue so meson uses the correct llvm-config tool.
Author: Fred Baksik <fred.baksik@mrcy.com<mailto:fred.baksik@mrcy.com>>
Date: Tue Dec 24 20:38:47 2019 -0500
meson: Allow for llvm-native tools to be used
Signed-off-by: Fred Baksik <fred.baksik@mrcy.com<mailto:fred.baksik@mrcy.com>>
diff --git a/meta/classes/meson.bbclass b/meta/classes/meson.bbclass
index e1a13bbbf7..b5cd2ee8c4 100644
--- a/meta/classes/meson.bbclass
+++ b/meta/classes/meson.bbclass
@@ -33,6 +33,7 @@ EXTRA_OEMESON_append = " ${PACKAGECONFIG_CONFARGS}"
MESON_CROSS_FILE = ""
MESON_CROSS_FILE_class-target = "--cross-file ${WORKDIR}/meson.cross"
MESON_CROSS_FILE_class-nativesdk = "--cross-file ${WORKDIR}/meson.cross"
+MESON_CROSS_FILE_class-native = "--native-file ${WORKDIR}/meson.native"
def meson_array(var, d):
items = d.getVar(var).split()
@@ -110,6 +111,14 @@ endian = '${@meson_endian('TARGET', d)}'
EOF
}
+do_write_config_class-native() {
+ # This needs to be Py to split the args into single-element lists
+ cat >${WORKDIR}/meson.native <<EOF
+[binaries]
+llvm-config = 'llvm-config${LLVMVERSION}'
+EOF
+}
+
CONFIGURE_FILES = "meson.build"
meson_do_configure() {
[-- Attachment #2: Type: text/html, Size: 7522 bytes --]
next prev parent reply other threads:[~2019-12-27 12:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-25 11:49 [meson][PATCH] meson: Allow for llvm-native tools to be used fdk17
2019-12-25 12:02 ` ✗ patchtest: failure for " Patchwork
2019-12-27 12:03 ` Peter Kjellerstedt [this message]
2019-12-27 14:25 ` [meson][PATCH] " fdk17
2019-12-27 14:30 ` Fred Baksik
2020-01-02 17:28 ` Ross Burton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54a01022886647f9baa8608f8a6af5b1@XBOX03.axis.com \
--to=peter.kjellerstedt@axis.com \
--cc=fdk17@ftml.net \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox