cmake-init-use-pkg-config

Using a dependency that does not support clients using CMake (by friendlyanon)

Cmake-init-use-pkg-config Alternatives

Similar projects and alternatives to cmake-init-use-pkg-config

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better cmake-init-use-pkg-config alternative or higher similarity.

cmake-init-use-pkg-config reviews and mentions

Posts with mentions or reviews of cmake-init-use-pkg-config. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-11-14.
  • Good reasons to NOT use CMake
    6 projects | /r/cpp | 14 Nov 2022
    You have to realize that the point of using CMake is not entirely about your project, but about downstream users who wish to use CMake as well. If you do not support clients using CMake (i.e. install a CMake package) you are forcing every downstream user to figure your requirements out by themselves, which even for a project with no dependencies is non-trivial: https://github.com/friendlyanon/cmake-init-use-pkg-config
  • cmake-init - The missing CMake project initializer, now with Conan and vcpkg templates!
    4 projects | /r/cpp | 2 Mar 2022
    See this example from the wiki. This one tries to use unofficial vcpkg package nd targets, then falls back to pkg config, then falls back to find_* commands. This is probably more than what you are asking, but you can put anything in the find module, even code that vendors projects, although I highly recommend against any form of vendoring (manual, git, FetchContent, etc). Vendoring only causes problems for packagers.

Stats

Basic cmake-init-use-pkg-config repo stats
2
4
2.6
about 2 years ago
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com