Because cmake's package management (particularly when used with hunter) correctly manages dependencies for cross-compiled environments and for all toolchains. When using the same code base for 6 different compile targets as I do (unix, mac, windows, iOS, android, emscripten) it's a godsend. On Mon, 19 Jun 2017 at 10:58, Olaf van der Spek via Boost < boost@lists.boost.org> wrote:
It would be nice to not just support cmake, but pkgconfig as well. There are many times I need to use boost in non-cmake projects, so having
On Sat, Jun 17, 2017 at 3:36 PM, P F via Boost <boost@lists.boost.org> wrote: pkgconfig would be helpful as well.
I don't really get find_package and pkgconfig etc.
I use package management to install the dependencies I need. I then include and link to the stuff I need. It'd be nice if the linking was automatic like it is on MSVC but okay.
Why does one need all kinds of extra complexity in every single make file for things like find_package or pkgconfig?
-- Olaf
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost