From: Baruch Siach via buildroot <buildroot@buildroot.org>
To: "Kennedy, Andy Collins via buildroot" <buildroot@buildroot.org>
Cc: "Kennedy, Andy Collins" <Andy.A.Kennedy@collins.com>
Subject: Re: [Buildroot] Python for host?
Date: Fri, 18 Oct 2024 08:16:48 +0300 [thread overview]
Message-ID: <87froung73.fsf@tarshish> (raw)
In-Reply-To: <BN2P110MB1060B7C18C429384A20EF037C840A@BN2P110MB1060.NAMP110.PROD.OUTLOOK.COM> (Andy Collins via buildroot Kennedy's message of "Fri, 18 Oct 2024 02:43:10 +0000")
Hi Andy,
On Fri, Oct 18 2024, Kennedy, Andy Collins via buildroot wrote:
> I'm in need of Python 3 and supporting libraries for the host. I do not
> want to build Python3 and the libraries for my limited storage embedded
> system, but I do have requirements on it for the host. One of the
> libraries I need is python-pylibfdt. It seems that I can only select to
> build the host version of this package if I have selected packages ->
> Python3, then choose the external package at that time. Given that I
> have a build need for this tool (a support package from a vendor that
> needs that library and I'm working on a super old Ubuntu distro and
> am unable to update) I would really like to select and build the host
> package. I can go through and add in a Config.in.host for this
> particular package and dup the .mk file as HOST (removing the
> $(eval host-python-package) into the host-...mk file but I feel like
> this is the wrong way.
>
> Anyone else in the WORLD having to run BR on a 20yo system and need
> Python host? Anyone have a clue an easy solution? Am I just being
> dumb? <<<< I HOPE that is the easy answer.
Adding host-python-pylibfdt to the list of your target package
<PKG>_DEPENDENCIES should be enough. No need for Config.in.host
file. See for example boot/ti-k3-r5-loader/ti-k3-r5-loader.mk, and
boot/uboot/uboot.mk, that both use host-python-pylibfdt.
Hope this helps,
baruch
--
~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch@tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-10-18 5:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-18 2:43 [Buildroot] Python for host? Kennedy, Andy Collins via buildroot
2024-10-18 5:16 ` Baruch Siach via buildroot [this message]
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=87froung73.fsf@tarshish \
--to=buildroot@buildroot.org \
--cc=Andy.A.Kennedy@collins.com \
--cc=baruch@tkos.co.il \
/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.