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 12:52:12 +0300 [thread overview]
Message-ID: <ZS5ZTMlhyMdLPEQ_@nuoska> (raw)
In-Reply-To: <AM9PR03MB7012DDCF969FEAAD42A8817992D6A@AM9PR03MB7012.eurprd03.prod.outlook.com>
Hi,
On Tue, Oct 17, 2023 at 09:21:27AM +0000, Dave Hitchman wrote:
> Oh I dont know. This is getting to be a bit annoying.
> I had already included the inherit cmake line but now it seems maybe that you dont need to put any cmake commands in... not 100% sure, no one seems to explain this, I am not convinced.
> However I want some extra flags and I have read that you should be able to:
> TARGET_CFLAGS += "-DBUILD_PYTHON_BINDINGS=ON -DBUILD_SHARED=ON -DBUILD_TOOLS=ON"
Don't put these into CFLAGS. I presume you want to give these to CMake via EXTRA_OECMAKE
variable to be used at do_configure time. Check poky tree for documentation and examples,
docs are also here:
https://docs.yoctoproject.org/dev/singleindex.html#cmake
> but building that gives me
> + cd /home/dave/Documents/Kymati/yocto/build/tmp/work/cortexa53-crypto-phytec-linux/libkymati/1.0-r0/build
> + do_configure
> + cd /home/dave/Documents/Kymati/yocto/build/tmp/work/cortexa53-crypto-phytec-linux/libkymati/1.0-r0/git
> + TARGET_CFLAGS:=-DBUILD_PYTHON_BINDINGS=ON -DBUILD_SHARED=ON -DBUILD_TOOLS=ON
>
> /home/dave/Documents/Kymati/yocto/build/tmp/work/cortexa53-crypto-phytec-linux/libkymati/1.0-r0/temp/run.do_configure.991537: 159: TARGET_CFLAGS:=-DBUILD_PYTHON_BINDINGS=ON -DBUILD_SHARED=ON -DBUILD_TOOLS=ON: not found
>
> Is there a good, really works, actually sets extra flags, really shows and explains with comments and everything example I can look at? This bitbake is clearly clever, so is cmake, but in honesty I really gave up trying to understand any of it and just want it to work, writing the code is one thing but these build systems are a fight all of their own that takes longer than the code to solve the universe
Build systems are hard. I'm sure someone will invent another one to solve all issues
and resurrect all old ones. :)
Cheers,
-Mikko
next prev parent reply other threads:[~2023-10-17 9:52 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 [this message]
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=ZS5ZTMlhyMdLPEQ_@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.