Added conan-based dependency management for the package.

[cwolfe2]

No description provided.

[cwolfe2]

• would need to modify appveyor environment to have conan installed
• would need to have conan install step added, or done with external command in CMakeLists.txt
• probably doesn't work out of the gate for x86, but x64 builds fine.
• if you're interested, i can flesh out the other targets.

[nlohmann]

I like the idea of having the possibility to use Conan, but it should not be a prerequisite. Is it possible to have a CMakeLists.txt that uses Conan if it is available, but falls back to the current behavior if not?

[cwolfe2]

Sure. This is kinda lower priority for me right now, but I hope to circle back to it in the coming weeks. I’ll send you another PR then. ~Chris From: Niels Lohmann <notifications@github.com> Sent: Thursday, April 4, 2019 11:53 AM To: nlohmann/crow <crow@noreply.github.com> Cc: Christopher Wolfe <cwolfe@sizestream.com>; Author <author@noreply.github.com> Subject: Re: [nlohmann/crow] Added conan-based dependency management for the package. (#37) I like the idea of having the possibility to use Conan, but it should not be a prerequisite. Is it possible to have a CMakeLists.txt that uses Conan if it is available, but falls back to the current behavior if not? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#37 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/Au-Zeu9_4JRkaGlREbJgqwQWqyjsq9Pmks5vdh_RgaJpZM4cbrV_>.

[nlohmann]

Thanks a lot!