Add initial support for building using CMake #249
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
CMake builds all tests into a single executable. So, naming these two classes the same is an ODR violation, which also causes segmentation fault on my machine when I try to run tests. With this patch, test executable do not crash anymore. However, there are still 13 failing tests, which require further investigation.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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).