Add README.md describing the fork's differences from upstream OpenCTM - #4
Merged
Conversation
Grantim
approved these changes
Sep 8, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Adds a Markdown README that GitHub shows on the landing page instead of the plain-text upstream
README.txt(kept verbatim for the original change log and credits).It states the fork point (upstream v1.0.3) and lists every difference: library-only scope, CMake build and export macro,
ctmRearrangeTriangles, thectmSaveCustomprogress/cancel callback, empty-mesh support,noexceptin the C++ wrapper, the two loader hardening fixes from the S9S disclosure (#2, #3), and the resulting file-format compatibility notes.Content was cross-checked against the commit history and the current headers.