On 09/03/2011 12:11 PM, Alain Didierjean wrote:
>
> ----- Mail original -----
>> De: "Richard Heck" <rgh...@comcast.net>
>> À: "alain didierjean" <alain.didierj...@free.fr>
>> Cc: lyx-users@lists.lyx.org
>> Envoyé: Samedi 3 Septembre 2011 16:13:36
>> Objet: Re: Bug ?
>>
>> On 09/03/2011 03:27 AM, alain.didierj...@free.fr wrote:
>>> I recompiled lyx yesterday (on a gentoo system), adding support to
>>> luatex and xetex.
>>>
>> Recompilation should not be required, unless you were upgrading to
>> 2.0.0 or something of the sort.
> using gentoo linux, packages are compiled localy. Adding luatex and xetex
> support means recompiling lyx.
>
Last I knew, Pavel was using gentoo, so perhaps he can help.
But nonetheless, someone on gentoo who did not previously have xetex
support, but who has compiled 2.0.0 already, can add it by acquiring the
xetex binary (however they might do that) and doing Tools>Reconfigure in
LyX. There's no compilation setting in LyX for this, as there is, e.g.,
for libx264 support in ffmpeg. LyX has no sort of compilation dependency
upon xetex (there are no headers that it needs, e.g.), but only uses it
as a completely external tool.
Indeed, you could create a script /usr/bin/xe(?:la)?tex whose entire
code was:
#!/bin/bash
exit 0;
and LyX would happily let you use XeTeX. (Not that it would work very
well....) All LyX cares is that there is some program called
"xe(?:la)?tex" in the path, and that is checked during LyX's
configuration process, not during the autotools configuration.
Richard
PS Security issues anyone?
