* xft use --with-cairo
@ 2019-06-24 19:36 Stefan Monnier
2019-06-24 22:37 ` YAMAMOTO Mitsuharu
0 siblings, 1 reply; 4+ messages in thread
From: Stefan Monnier @ 2019-06-24 19:36 UTC (permalink / raw)
To: emacs-devel
I just noticed a funny detail of the `configure` step when
using --with-cairo:
[...]
Does Emacs use -lotf? yes
Does Emacs use -lxft?
Does Emacs use -lsystemd? no
[...]
Notice how it stays silent about xft.
The build goes through just fine, so I'm not sure what this means.
Should it say yes/no, or is xft indispensable for Cairo, in which case
the whole line should maybe be removed?
Stefan
^ permalink raw reply [flat|nested] 4+ messages in thread* Re: xft use --with-cairo
2019-06-24 19:36 xft use --with-cairo Stefan Monnier
@ 2019-06-24 22:37 ` YAMAMOTO Mitsuharu
2019-06-24 23:27 ` Stefan Monnier
0 siblings, 1 reply; 4+ messages in thread
From: YAMAMOTO Mitsuharu @ 2019-06-24 22:37 UTC (permalink / raw)
To: Stefan Monnier; +Cc: emacs-devel
On Tue, 25 Jun 2019 04:36:21 +0900,
Stefan Monnier wrote:
>
> I just noticed a funny detail of the `configure` step when
> using --with-cairo:
>
> [...]
> Does Emacs use -lotf? yes
> Does Emacs use -lxft?
> Does Emacs use -lsystemd? no
> [...]
>
> Notice how it stays silent about xft.
> The build goes through just fine, so I'm not sure what this means.
> Should it say yes/no, or is xft indispensable for Cairo, in which case
> the whole line should maybe be removed?
The cairo build used to depend on Xft, but that is no longer the case
(even with lwlib-Xaw). I overlooked this one when I made such
changes. I've pushed a fix to display "no" for this case.
YAMAMOTO Mitsuharu
mituharu@math.s.chiba-u.ac.jp
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: xft use --with-cairo
2019-06-24 22:37 ` YAMAMOTO Mitsuharu
@ 2019-06-24 23:27 ` Stefan Monnier
2019-06-25 2:43 ` Eli Zaretskii
0 siblings, 1 reply; 4+ messages in thread
From: Stefan Monnier @ 2019-06-24 23:27 UTC (permalink / raw)
To: YAMAMOTO Mitsuharu; +Cc: emacs-devel
> The cairo build used to depend on Xft, but that is no longer the case
> (even with lwlib-Xaw). I overlooked this one when I made such
> changes. I've pushed a fix to display "no" for this case.
Thanks. I wonder, tho: the user might be tempted to conclude that the
xft headers were not found or something like this, so maybe it's better
to remove the line altogether (or put something like "N/A").
Stefan
^ permalink raw reply [flat|nested] 4+ messages in thread* Re: xft use --with-cairo
2019-06-24 23:27 ` Stefan Monnier
@ 2019-06-25 2:43 ` Eli Zaretskii
0 siblings, 0 replies; 4+ messages in thread
From: Eli Zaretskii @ 2019-06-25 2:43 UTC (permalink / raw)
To: Stefan Monnier; +Cc: mituharu, emacs-devel
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Date: Mon, 24 Jun 2019 19:27:46 -0400
> Cc: emacs-devel@gnu.org
>
> > The cairo build used to depend on Xft, but that is no longer the case
> > (even with lwlib-Xaw). I overlooked this one when I made such
> > changes. I've pushed a fix to display "no" for this case.
>
> Thanks. I wonder, tho: the user might be tempted to conclude that the
> xft headers were not found or something like this, so maybe it's better
> to remove the line altogether (or put something like "N/A").
The xft non-use in this case is similar to half a dozen other lines in
the same list, so if we are going to display something other than just
YES or NO, we should do that in all such lines.
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2019-06-25 2:43 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2019-06-24 19:36 xft use --with-cairo Stefan Monnier
2019-06-24 22:37 ` YAMAMOTO Mitsuharu
2019-06-24 23:27 ` Stefan Monnier
2019-06-25 2:43 ` Eli Zaretskii
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).