Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create CMakeLists.txt #2

Merged
merged 1 commit into from Aug 12, 2019
Merged

Conversation

syntheticmagus
Copy link
Contributor

First CMake build file, necessary for UWP support because Arcana's UWP offerings aren't header-only.

First CMake build file, necessary for UWP support because Arcana's UWP offerings aren't header-only.
@syntheticmagus syntheticmagus merged commit 1815d86 into master Aug 12, 2019
@syntheticmagus syntheticmagus deleted the syntheticmagus-initial-cmake branch August 12, 2019 22:39
@ryantrem
Copy link
Member

ryantrem commented Aug 13, 2019

Because Arcana's UWP offerings aren't header-only

@syntheticmagus If memory serves, it shouldn't be too much work to make it header-only, which would also make it considerably more portable and easy to consume.

@syntheticmagus
Copy link
Contributor Author

syntheticmagus commented Aug 13, 2019

@ryantrem That makes sense, I'm just not sure quite yet that we want to go down that road. We should probably convert the existing code to be header-only -- I'll open an issue for that -- but even after that we may add additional non-header-only capabilities, or we might need a CMakeLists.txt if we want to make the tests cross-plat. It's pretty easy to consume through CMake, too, though certainly not as easy as a truly header-only library.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants