Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Christian Hitz via buildroot <buildroot@buildroot.org>
Cc: Christian Hitz <christian@klarinett.li>,
	James Hilliard <james.hilliard1@gmail.com>,
	Christian Hitz <christian.hitz@bbv.ch>,
	Asaf Kahlon <asafka7@gmail.com>
Subject: Re: [Buildroot] [PATCH 1/3] package/python-fonttools: enable host-package
Date: Tue, 26 Mar 2024 15:41:08 +0100	[thread overview]
Message-ID: <20240326154108.28f91cb1@windsurf> (raw)
In-Reply-To: <20240228145013.411919-1-christian@klarinett.li>

Hello Christian,

On Wed, 28 Feb 2024 15:50:09 +0100
Christian Hitz via buildroot <buildroot@buildroot.org> wrote:

> From: Christian Hitz <christian.hitz@bbv.ch>
> 
> The fonttools are used to generate static fonts from variable fonts
> at build time.
> 
> Signed-off-by: Christian Hitz <christian.hitz@bbv.ch>
> ---
>  package/python-fonttools/Config.in.host      | 6 ++++++
>  package/python-fonttools/python-fonttools.mk | 1 +
>  2 files changed, 7 insertions(+)
>  create mode 100644 package/python-fonttools/Config.in.host
> 
> diff --git a/package/python-fonttools/Config.in.host b/package/python-fonttools/Config.in.host
> new file mode 100644
> index 0000000000..641efb1cfb
> --- /dev/null
> +++ b/package/python-fonttools/Config.in.host
> @@ -0,0 +1,6 @@
> +config BR2_PACKAGE_HOST_PYTHON_FONTTOOLS
> +	bool "host-python-fonttools"
> +	help
> +	  Tools to manipulate font files.
> +
> +	  https://github.com/fonttools/fonttools

We don't really need this part, at least for PATCH 3/3. Just adding
$(eval $(host-python-package)) is sufficient. Adding a Config.in entry
is only needed if the host package needs to be made user-visible. In
your case, we don't need to make it user-visible: this host package is
merely a build-time dependency of generating static fonts from the
googlefontdirectory package.

Best regards,

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2024-03-26 14:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-28 14:50 [Buildroot] [PATCH 1/3] package/python-fonttools: enable host-package Christian Hitz via buildroot
2024-02-28 14:50 ` [Buildroot] [PATCH 2/3] package/googlefontdirectory: bump to 2125bc9b447971543caaa132530b828e5e682819 Christian Hitz via buildroot
2024-03-26 14:39   ` Thomas Petazzoni via buildroot
2024-02-28 14:50 ` [Buildroot] [PATCH 3/3] package/googlefontdirectory: allow generating static fonts Christian Hitz via buildroot
2024-03-26 14:41 ` Thomas Petazzoni 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=20240326154108.28f91cb1@windsurf \
    --to=buildroot@buildroot.org \
    --cc=asafka7@gmail.com \
    --cc=christian.hitz@bbv.ch \
    --cc=christian@klarinett.li \
    --cc=james.hilliard1@gmail.com \
    --cc=thomas.petazzoni@bootlin.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