From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Sourabh Hegde <hrsourabh011@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] How to pass EXTRA_OECMAKE_BUILD in Buildroot package definition?
Date: Fri, 22 Sep 2023 19:06:14 +0200 [thread overview]
Message-ID: <20230922170614.GS512384@scaer> (raw)
In-Reply-To: <CADYjeSv4H7rqSaq5D7a9zHyZxSMp1vJv5sNs6Lj7RJLgmXEd3w@mail.gmail.com>
Sourabh, all,
Please do not top-post, this is considered bad etiquette. Reply in-line
as I do:
On 2023-09-22 18:22 +0200, Sourabh Hegde spake thusly:
> Yes, I checked in "Infrastructure for Cmake based packages" but couldn't find anything relevant.
> There seems to be no direct way to do this in Buildroot. Please correct me if I'm wrong.
So, you have to know what that OE variable does (I have no idea, I don't
do OE). But by the name, and the value it is assigned, it looks like it
is the list of cmake rules to build.
We do have that in Buildroot: LIBFOO_MAKE_OPTS
You could look at existign packages to see how it is used, e.g.:
$ grep _MAKE_OPTS $(git grep -l -E 'eval \$\(cmake-')
Now, if you are trying to use tensorflow-lite, there is a pending series
by James, and it would be nice if you could have a look at it, test it,
and report, rather than try yet something else:
https://patchwork.ozlabs.org/project/buildroot/list/?series=346546
Regards,
Yann E. MORIN.
Regards,
Yann E. MORIN.
> On Fri, Sep 22, 2023, 18:04 Yann E. MORIN < [1]yann.morin.1998@free.fr> wrote:
>
> Sourabh, All,
>
> On 2023-09-22 17:33 +0200, Sourabh Hegde spake thusly:
> > Hi,
> > I am trying to add a Buildroot package where I need to specify EXTRA_OECMAKE_BUILD. But I couldn't find any relevant
> > variable in Buildroot for this.
>
> This variable is specific to the OpenEmbedded world.
>
> Look at the Buildroot manual to find the corresponding variable:
>
> [2]https://buildroot.org/downloads/manual/manual.html
>
> Hint: "Infrastructure for CMake-based packages"
>
> Regards,
> Yann E. MORIN.
>
> > Example will be from
> > [1]
> [3]https://github.com/nxp-imx/meta-imx/blob/64a864ab77de06a557afcb01e6dd4d21606e6948/meta-ml/recipes-libraries/tensorflow-lite/tensorflow-lite_2.10.0.bb#L41
> > Can anyone please let me know how to achieve this?
> > Thanks in advance.
> >
> > Links:
> > 1.
> [4]https://github.com/nxp-imx/meta-imx/blob/64a864ab77de06a557afcb01e6dd4d21606e6948/meta-ml/recipes-libraries/tensorflow-lite/tensorflow-lite_2.10.0.bb#L41
>
> > _______________________________________________
> > buildroot mailing list
> > [5]buildroot@buildroot.org
> > [6]https://lists.buildroot.org/mailman/listinfo/buildroot
>
> --
> .-----------------.--------------------.------------------.--------------------.
> | Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
> | +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___
> |
> | +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
> | [7]http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
> '------------------------------^-------^------------------^--------------------'
>
> Links:
> 1. mailto:yann.morin.1998@free.fr
> 2. https://buildroot.org/downloads/manual/manual.html
> 3. https://github.com/nxp-imx/meta-imx/blob/64a864ab77de06a557afcb01e6dd4d21606e6948/meta-ml/recipes-libraries/tensorflow-lite/tensorflow-lite_2.10.0.bb#L41
> 4. https://github.com/nxp-imx/meta-imx/blob/64a864ab77de06a557afcb01e6dd4d21606e6948/meta-ml/recipes-libraries/tensorflow-lite/tensorflow-lite_2.10.0.bb#L41
> 5. mailto:buildroot@buildroot.org
> 6. https://lists.buildroot.org/mailman/listinfo/buildroot
> 7. http://ymorin.is-a-geek.org/
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-09-22 17:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-22 15:33 [Buildroot] How to pass EXTRA_OECMAKE_BUILD in Buildroot package definition? Sourabh Hegde
2023-09-22 16:04 ` Yann E. MORIN
2023-09-22 16:22 ` Sourabh Hegde
2023-09-22 17:06 ` Yann E. MORIN [this message]
2023-09-24 20:31 ` Sourabh Hegde
2023-09-26 4:52 ` Sourabh Hegde
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=20230922170614.GS512384@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@buildroot.org \
--cc=hrsourabh011@gmail.com \
/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