This adds limited support for building project using CMake and, crucially for me, support for building code as a shared library.
Feel free to close the PR if the maintenance burden for the CMake build will be too high. Honestly, I just haven't felt like troubleshooting autotools after configuring failed with some obscure error.
For some context, I want to use DVI parser from here in my attempt to speed up LaTeX live previews (in Sublime Text). The current idea is to fork latex process right before it reads \begin{document} (this part is simple and already done); use the fork to produce dvi file with a rendered preview; split it into glyphs using dvisvgm; and then rerender changed parts (probably, using this library).
This adds limited support for building project using CMake and, crucially for me, support for building code as a shared library.
Feel free to close the PR if the maintenance burden for the CMake build will be too high. Honestly, I just haven't felt like troubleshooting autotools after configuring failed with some obscure error.
For some context, I want to use DVI parser from here in my attempt to speed up LaTeX live previews (in Sublime Text). The current idea is to fork
latexprocess right before it reads\begin{document}(this part is simple and already done); use the fork to produce dvi file with a rendered preview; split it into glyphs usingdvisvgm; and then rerender changed parts (probably, using this library).