untangling the EOT mess
rene at debian.org
Sat Jul 30 10:23:32 UTC 2022
(and the follow-up
it seems that EOT usage is completely disabled whatever it takes.
Was this intended?
I have --enable-eot and --with-system-libeot in my confiugure flags
(which are the correct ones, otherwise configure would complain about
unknown flags! - I actually adapted them after seeing those commits back
then..) and I also even get
checking which eot to use... external
checking for libeot >= 0.01... yes
in configures output
$ grep EOT config_host.mk
export LIBEOT_LIBS=$(gb_SPACE) -leot
So far so good, but:
$ cat config_host/config_eot.h
/* config_host/config_eot.h. Generated from config_eot.h.in by
#define ENABLE_LIBEOT 0
which then of course makes it not built (I noticed because a upgrade
7.3->7.4 in Debian says "libeot0" is now not needed anymore).
I *belivee* that this is due to the ",disabled" in configure.ac (which
is actually even the only occurence of it):
$ grep \,disabled configure.ac
libo_CHECK_SYSTEM_MODULE([eot],[LIBEOT],[libeot >= 0.01],disabled)
rene at frodo:~/LibreOffice/git/libreoffice-7-4$
was disabling EOT intended? Should it be enableable? (Because right now
it is not, see above)? Should it be removed alltogether for clarity?
More information about the LibreOffice