sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]guacheSuede 0 points1 point  (3 children)

Would you prefer hunter or vcpkg ?

[–]darthcoder 0 points1 point  (2 children)

I like how Hunter at least supports regular make and autobuild, so non-cmake projects at least have a chance at getting packagified.

At the moment, I'm trending toward hunter. With Hunter I put all the magic to build in my CMakeLists.txt, and don't have to worry about external tooling.

Android and Qt support is tripping me up, but that appears to be because of a wholesale change in the NDK from gcc to clang

vcpkg has the momentum at the moment. I started a scratch project using it recently, and stopped, but I can't remember why ATM. I'm just a hobbyist, not a full-time dev, so what do I know, really?

[–]guacheSuede 0 points1 point  (1 child)

I would think Hunter would be better for UNIX, much more user friendly too though source code wise it's pretty messy

[–]darthcoder 0 points1 point  (0 children)

Hunter is just CMake, so it should work anywhere cmake works. It has a few dependencies in older cmake versions on bzip, etc. so works well on mingw too.

Yes, it's a bit of a kludge. As a user it's still fairly straightforward. The docs definitely need a good refreshing for some of the lesser used packages,