On Mon, Sep 2, 2019 at 4:16 PM Nicolas Holzschuch < [email protected]> wrote:
> Hi, > > > On 29 Aug 2019, at 23:40, Henri Menke <[email protected]> wrote: > > > > > > Dear list, (especially Hans and Luigi) > > > > Would it be possible to have the build system generate static libraries > > of the executables as well? That is to say, instead of generating > > luatex.exe, generate luatex.a which can then be turned into an > > executable in one linking step. > > > > The rationale is that I want to link additional static and/or dynamic > > libraries into LuaTeX but I don't want to go through the whole trouble > > of adding these libraries to the build system. If there was a single > > static library `lua(jit)tex.a' which I could be used like > > > > gcc -o myluatex luatex.a > > I did something similar: generate a dynamic library with minimal > modifications to the code: https://github.com/holzschu/lib-tex > > sure, this is the standard way to generate the dll windows exe. Under linux , --enable-shared --disable-native-texlive-build --disable-static should work without modifications (perhaps the linker flag -Wl,-rpath,'$ORIGIN/.' can be used to locate the libtexlua53.so.5 libkpathsea.so.6 in the same folder of the luatex dso) . -- luigi
