From: Mikko Rapeli <mikko.rapeli@linaro.org>
To: Dave Hitchman <dave.hitchman@kymati.com>
Cc: "yocto@lists.yoctoproject.org" <yocto@lists.yoctoproject.org>
Subject: Re: [yocto] Using cmake... how?
Date: Tue, 17 Oct 2023 15:23:27 +0300 [thread overview]
Message-ID: <ZS58vzbmpFG8ck9i@nuoska> (raw)
In-Reply-To: <AM9PR03MB701278137F02C02E6532EFE192D6A@AM9PR03MB7012.eurprd03.prod.outlook.com>
Hi,
On Tue, Oct 17, 2023 at 11:58:23AM +0000, Dave Hitchman wrote:
> I understand that, and the compiler the rest of the recipe uses does cope so I am trying to understand why this bit of the whole thing is using a different compiler. Maybe it is somewhere in the cmake of the library, but it certainly isnt obvious. Thats where I am digging for the moment.
One thing could be CMake calls to sub projects/directories/modules where the
toolchain file is not propagated. So first level CMake gets correctly called with
cross compile toolchain file but second or third level ones not. These are
annoyingly tricky to spot. It makes sense to change the do_configure
task calls to cmake be as verbose as possible. CMake doesn't make these easy.
Hope this helps,
-Mikko
next prev parent reply other threads:[~2023-10-17 12:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-16 11:22 [meta-rockchip][kirkstone][PATCH] bsp: rkbin: fix default COMPATIBLE_MACHINE matching all Quentin Schulz
2023-10-16 15:27 ` [yocto] Using cmake... how? Dave Hitchman
2023-10-16 19:48 ` Khem Raj
2023-10-17 5:49 ` Mikko Rapeli
2023-10-17 9:21 ` Dave Hitchman
2023-10-17 9:52 ` Mikko Rapeli
2023-10-17 10:09 ` Dave Hitchman
2023-10-17 10:22 ` Mikko Rapeli
2023-10-17 11:35 ` Dave Hitchman
2023-10-17 11:42 ` Mikko Rapeli
2023-10-17 11:53 ` Mikko Rapeli
2023-10-17 11:58 ` Dave Hitchman
2023-10-17 12:23 ` Mikko Rapeli [this message]
2023-10-17 13:32 ` Ross Burton
2023-10-17 15:18 ` Dave Hitchman
2023-10-25 13:43 ` [yocto] [meta-rockchip][kirkstone][PATCH] bsp: rkbin: fix default COMPATIBLE_MACHINE matching all Trevor Woerner
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=ZS58vzbmpFG8ck9i@nuoska \
--to=mikko.rapeli@linaro.org \
--cc=dave.hitchman@kymati.com \
--cc=yocto@lists.yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.