Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Alsey Coleman Miller <alseycmiller@gmail.com>
Cc: buildroot@buildroot.org, Michael Fischer <mf@go-sys.de>
Subject: Re: [Buildroot] [PATCH 6/8] package/sdl3_ttf: build plutosvg support when available
Date: Mon, 19 Oct 2026 23:50:52 +0200	[thread overview]
Message-ID: <ataQkSFmjK-IjEcL@windsurf> (raw)
In-Reply-To: <20260816191830.533747-7-alseycmiller@gmail.com>

On Sun, Aug 16, 2026 at 03:18:28PM -0400, Alsey Coleman Miller wrote:
> Colour emoji fonts store their glyphs as SVG, which SDL3_ttf renders
> through plutosvg. Without it those glyphs are skipped and the rest of
> the font still renders.
> 
> plutosvg is packaged in the swift-linux ports tree rather than in
> Buildroot, so BR2_PACKAGE_PLUTOSVG is undefined on a plain Buildroot and
> the branch selects SDLTTF_PLUTOSVG=OFF - the behaviour before this
> commit. Not for upstream until plutosvg and plutovg are packaged there.
> 
> Signed-off-by: Alsey Coleman Miller <alseycmiller@gmail.com>

I'm not sure what happened, but we don't have plutosvg in Buildroot at
the moment, so I changed this to a simpler commit that disables
plutosvg support entirely.

Could you resubmit the plutosvg package and its support, if you're
still interested into this?

Thanks a lot!

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

  reply	other threads:[~2026-10-19 21:51 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-16 19:18 [Buildroot] [PATCH 0/8] package/sdl3*: complete the SDL3 family Alsey Coleman Miller
2026-08-16 19:18 ` [Buildroot] [PATCH 1/8] package/plutovg: new package Alsey Coleman Miller
2026-09-22 20:23   ` Julien Olivain via buildroot
2026-08-16 19:18 ` [Buildroot] [PATCH 2/8] package/plutosvg: " Alsey Coleman Miller
2026-09-22 20:27   ` Julien Olivain via buildroot
2026-08-16 19:18 ` [Buildroot] [PATCH 3/8] package/sdl3: add ALSA and test program options, follow dbus Alsey Coleman Miller
2026-09-22 20:08   ` Julien Olivain via buildroot
2026-08-16 19:18 ` [Buildroot] [PATCH 4/8] package/sdl3_image: bump to version 3.4.4 Alsey Coleman Miller
2026-10-19 21:49   ` Thomas Petazzoni via buildroot
2026-08-16 19:18 ` [Buildroot] [PATCH 5/8] package/sdl3_ttf: do not build the samples or install man pages Alsey Coleman Miller
2026-10-19 21:49   ` Thomas Petazzoni via buildroot
2026-08-16 19:18 ` [Buildroot] [PATCH 6/8] package/sdl3_ttf: build plutosvg support when available Alsey Coleman Miller
2026-10-19 21:50   ` Thomas Petazzoni via buildroot [this message]
2026-08-16 19:18 ` [Buildroot] [PATCH 7/8] package/sdl3_mixer: new package Alsey Coleman Miller
2026-09-22 19:59   ` Julien Olivain via buildroot
2026-08-16 19:18 ` [Buildroot] [PATCH 8/8] package/sdl3_net: " Alsey Coleman Miller
2026-10-19 21:51   ` Thomas Petazzoni via buildroot

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=ataQkSFmjK-IjEcL@windsurf \
    --to=buildroot@buildroot.org \
    --cc=alseycmiller@gmail.com \
    --cc=mf@go-sys.de \
    --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