From: "André Draszik" <git@andred.net>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/9] meson: add a recipe and class from meta-oe
Date: Fri, 15 Dec 2017 15:29:52 +0000 [thread overview]
Message-ID: <1513351792.21903.53.camel@andred.net> (raw)
In-Reply-To: <CAJ86T=Xk+1sKXvfq3EfEwOuwfuPDeW72G0GSdQtqgTKieLH3JQ@mail.gmail.com>
On Thu, 2017-12-07 at 11:27 -0800, Andre McCurdy wrote:
> On Fri, Nov 17, 2017 at 4:02 AM, Alexander Kanavin
> <alexander.kanavin@linux.intel.com> wrote:
> > +
> > +MESON_HOST_ENDIAN = "${@bb.utils.contains('SITEINFO_ENDIANNESS', 'be',
> > 'big', 'little', d)}"
>
> SITEINFO_ENDIANNESS returns the endianness of the target, not the
> host.
Isn't the host what you call target? When cross-compiling, the host machine
normally refers to the system where the built programs will be run, and
target machine to where the a compiler will run, in case a compiler is being
(cross-)compiled.
${MESON_HOST_ENDIAN} is used inside the [host_machine] statement, so this
looks right.
> [...]
>
> > +MESON_TARGET_ENDIAN = "${@bb.utils.contains('TUNE_FEATURES',
> > 'bigendian', 'big', 'little', d)}"
>
> This won't work for all targets (e.g. PowerPC is big endian but
> doesn't include "bigendian" in TUNE_FEATURES). To determine the
> endianness of the target, use SITEINFO_ENDIANNESS instead.
${MESON_TARGET_ENDIAN} is used inside a [target_machine] statement, though.
Not sure about the naming and intention here...
Cheers,
Andre'
next prev parent reply other threads:[~2017-12-15 15:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-17 12:02 [PATCH 0/9] Introduce meson build system Alexander Kanavin
2017-11-17 12:02 ` [PATCH 1/9] meson: add a recipe and class from meta-oe Alexander Kanavin
2017-12-07 15:06 ` Peter Kjellerstedt
2017-12-15 14:57 ` Alexander Kanavin
2017-12-07 19:27 ` Andre McCurdy
2017-12-15 15:04 ` Alexander Kanavin
2017-12-15 15:29 ` André Draszik [this message]
2017-12-15 16:01 ` Linus Svensson
2017-12-15 16:13 ` Alexander Kanavin
2017-11-17 12:02 ` [PATCH 2/9] gnomebase.bbclass: split into autotools and meson versions Alexander Kanavin
2017-11-17 12:02 ` [PATCH 3/9] json-glib: convert to meson build Alexander Kanavin
2017-11-17 12:02 ` [PATCH 4/9] libepoxy: " Alexander Kanavin
2017-11-17 12:02 ` [PATCH 5/9] libinput: " Alexander Kanavin
2017-11-17 12:02 ` [PATCH 6/9] sysprof: " Alexander Kanavin
2017-11-17 12:02 ` [PATCH 7/9] gst-player: Upgrade, rename to gst-examples Alexander Kanavin
2017-11-17 12:02 ` [PATCH 8/9] meson: Port pkgconfig-native patch to 0.43.0 Alexander Kanavin
2017-11-17 12:02 ` [PATCH 9/9] meson: export native env only for native build Alexander Kanavin
-- strict thread matches above, loose matches on Subject: below --
2017-12-21 13:04 [PATCH 1/9] meson: add a recipe and class from meta-oe Alexander Kanavin
2018-01-04 13:12 Alexander Kanavin
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=1513351792.21903.53.camel@andred.net \
--to=git@andred.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