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 08:49:58 +0300 [thread overview]
Message-ID: <ZS4ghiXPvYDDW_LC@nuoska> (raw)
In-Reply-To: <AM9PR03MB7012E6E478F4D2899CBE0F5192D7A@AM9PR03MB7012.eurprd03.prod.outlook.com>
Hi,
On Mon, Oct 16, 2023 at 03:27:01PM +0000, Dave Hitchman wrote:
> So my current recipe for the project works, including building various C, C++ files
> I wanted to now add a library of someone elses creation.
> On my machine this library builds using the tools installed so the code is ok
>
> I added a recipe to my yocto build and it attempts to do the cmake.
>
> Unfortunately whatever I have tried over 2 days cmake insists:
>
> 1. On using the from my machine NOT the cross compiling tool set the rest of the yocto build uses.
> | -- The CXX compiler identification is GNU 9.4.0
> | -- The C compiler identification is GNU 9.4.0
> 2.
> Getting upset about the flags passed in:
> | g++: warning: ‘-mcpu=’ is deprecated; use ‘-mtune=’ or ‘-march=’ instead
> | cc1plus: error: bad value (‘armv8-a+crc+crypto’) for ‘-march=’ switch
> I cant even find where these flags are actually set, where I found them and thought they were set I altered them to be FRED and nothing changed in the errors at all.
>
> Any idea? Surely it should be pretty easy?
"inherit cmake" in the recipe and then fix the CMake scripts to use variables from
the toolchain file and only append to them. Same problems in all build tools. CMake
adds several abstractions on top though so finding out the details may be tricky.
See the toolchain.cmake file in recipe build directory. If this is not followed
wrong compiler can be used, with wrong flags, using wrong binary, module and header file
search paths...
Cheers,
-Mikko
next prev parent reply other threads:[~2023-10-17 5:50 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 [this message]
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
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=ZS4ghiXPvYDDW_LC@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.