From: Guillermo Rodriguez Garcia <guille.rodriguez@gmail.com>
To: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: [ptxdist] Circular dependencies in ptxdist
Date: Tue, 11 Oct 2016 09:26:02 +0200 [thread overview]
Message-ID: <CABDcavZhGubG7U-qO9uM=to0JX=so0Y2RXG9joCZY-Z7YGpxEA@mail.gmail.com> (raw)
Hello,
I am trying to create a ptxdist package for Harfbuzz
(https://www.freedesktop.org/wiki/Software/HarfBuzz/) but I have found
that Harfbuzz has a circular dependency with freetype: FreeType can
use Harfbuzz to improve hinting, but Hardbuzz needs FreeType to build.
Typical advice on how to handle this is: First build freetype without
Harfbuzz support, then build and install Harfbuzz, then rebuild and
reinstall Freetype with Harfbuzz support.
"Install FreeType, then HarfBuzz, then after HarfBuzz is installed,
rebuild and reinstall FreeType".
My question is, how can this handled in ptxdist?
I am considering something like the following:
1. A Freetype_bootstrap package that will build FT without Harfbuzz,
with an empty targetinstall stage. This is just so that Harfbuzz can
build
2. A Harfbuzz package that requires Freetype_bootstrap, and does the
actual targetinstall for Harfbuzz
3. Modify the Freetype package to add a "ENABLE_HARFBUZZ" option. If
this is enabled, then Freetype also SELECTS Harfbuzz.
Does this sound reasonable?
Are there other cases like this in ptxdist ?
Guillermo Rodriguez Garcia
guille.rodriguez@gmail.com
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next reply other threads:[~2016-10-11 7:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-11 7:26 Guillermo Rodriguez Garcia [this message]
2016-10-11 14:43 ` Michael Olbrich
2016-10-12 9:00 ` Guillermo Rodriguez Garcia
2016-10-20 7:16 ` Michael Olbrich
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='CABDcavZhGubG7U-qO9uM=to0JX=so0Y2RXG9joCZY-Z7YGpxEA@mail.gmail.com' \
--to=guille.rodriguez@gmail.com \
--cc=ptxdist@pengutronix.de \
/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