From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Christopher Howard <christopher@librehacker.com>, 51183@debbugs.gnu.org
Subject: bug#51183: lagrange: fribidi and harfbuzz dependencies?
Date: Thu, 14 Oct 2021 08:55:49 +0200 [thread overview]
Message-ID: <a1ac7393379bded0205a416d932f81396ded063f.camel@gmail.com> (raw)
In-Reply-To: <844b8d8659ee7ff5486c783a4c25243d8653f389.camel@librehacker.com>
Hi,
Am Mittwoch, den 13.10.2021, 15:40 -0800 schrieb Christopher Howard:
> Hello, the following did NOT work:
>
> ```
> (use-modules (guix packages))
> (use-modules (gnu packages web-browsers))
> (use-modules (gnu packages gtk))
> (use-modules (gnu packages fribidi))
>
> (packages->manifest
> (list
> (package
> (inherit lagrange)
> (inputs
> `(("harfbuzz" ,harfbuzz)
> ("fribidi" , fribidi)
> ,@(package-inputs lagrange))))))
> ```
>
> The package does build, but the problem remains with the script being
> displayed in the wrong direction.
>
> I'm am greatly curious if there are more configure time options that
> need to be set in relation to this. This paragraph indicates there
> are related configure options:
>
> https://github.com/skyjake/lagrange#unicode-text-rendering
By default, Lagrange should have ENABLE_FRIBIDI and ENABLE_HARFBUZZ be
ON, whereas ENABLE_FRIBIDI_BUILD and ENABLE_HARFBUZZ_MINIMAL are set
OFF, just as the script states. It would seem to be a bug elsewhere
then.
Try to check the build log to see whether or not harfbuzz and fribidi
respectively get correctly detected by CMake. It ought to use pkg-
config to do so, but I don't trust CMake on a fundamental level. If it
does, there might be a problem with how Lagrange uses them?
next prev parent reply other threads:[~2021-10-14 6:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-13 15:22 bug#51183: lagrange: fribidi and harfbuzz dependencies? Christopher Howard
2021-10-13 22:56 ` Liliana Marie Prikler
2021-10-13 23:40 ` Christopher Howard
2021-10-14 6:55 ` Liliana Marie Prikler [this message]
2021-10-14 10:39 ` Bengt Richter
2021-10-17 19:14 ` Efraim Flashner
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=a1ac7393379bded0205a416d932f81396ded063f.camel@gmail.com \
--to=liliana.prikler@gmail.com \
--cc=51183@debbugs.gnu.org \
--cc=christopher@librehacker.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
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.