Export toml.hpp for downstream consumers - #47
Merged
Conversation
jholloc
marked this pull request as ready for review
August 27, 2026 13:33
jholloc
self-requested a review
August 27, 2026 13:33
jholloc
approved these changes
Aug 27, 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.
Summary
Export the bundled
toml.hppalongside libtokamap's other public third-party headers.Motivation
libtokamap already uses toml++ internally, but does not install its header. Downstream projects that need TOML
parsing must therefore either vendor another copy of the same header or introduce a separate parser dependency.
Adding
ext_include/toml.hpptoEXT_HEADERSlets consumers use libtokamap's existing copy without duplication.The immediate consumer is the optional Python data-source configuration in
mapping-plugin.