3 ms·

They are still general very easy to install. Also, C programmers don't seem to use any package managers other than the default system package manager and maybe

They are still general very easy to install. Also, C programmers don't seem to use any package managers other than the default system package manager and maybe git sub-modules (at least, not that I know of).

shortrounddev2 2y ago
Yeah C programmers tend to be stuck in the late 90s
NullPrefix 2y ago
conan also works with C language, not just C++
mananaysiempre 2y ago
C on Unices is very well served by pkg-config[1] and its reimplementations[2,3]. (The last of these should also work well with MSYS2 on Windows, but it’s not—yet?—widely used in that environment.) The nice thing is that it has no opinions on your build system or even package manager, it’s purely for package discovery at build time. [1] https://www.freedesktop.org/wiki/Software/pkg-config/ https://www.freedesktop.org/wiki/Software/pkg-config/ [2] http://pkgconf.org/ http://pkgconf.org/ [3] https://nullprogram.com/blog/2023/01/18/ https://nullprogram.com/blog/2023/01/18/
hgs3 2y ago
> Also, C programmers don't seem to use any package managers other than the default system package manager and maybe git sub-modules (at least, not that I know of). For what it's worth, as someone who primarily writes C, not C++, I use the system package manager, vendoring, and sometimes Git submodules, depending on the project. On Windows, when I'm using MSYS2, I use the pacman package manager. If I'm targeting MSVC, I use CMake. For CMake, on Windows, I create my own directory where I place prebuilt dependencies for CMake to find [1]. With this approach, I can rely on CMake's builtin find_package behavior (no need for vcpkg and configure-time toolchain flags). [1] https://cmake.org/cmake/help/latest/command/find_package.html#config-mode-search-procedure https://cmake.org/cmake/help/latest/command/find_package.htm...

3 ms·

They are still general very easy to install. Also, C programmers don't seem to use any package managers other than the default system package manager and maybe

by atiedebee 2y ago

shortrounddev2 2y ago
Yeah C programmers tend to be stuck in the late 90s
NullPrefix 2y ago
conan also works with C language, not just C++
mananaysiempre 2y ago
C on Unices is very well served by pkg-config[1] and its reimplementations[2,3]. (The last of these should also work well with MSYS2 on Windows, but it’s not—yet?—widely used in that environment.) The nice thing is that it has no opinions on your build system or even package manager, it’s purely for package discovery at build time. [1] https://www.freedesktop.org/wiki/Software/pkg-config/ https://www.freedesktop.org/wiki/Software/pkg-config/ [2] http://pkgconf.org/ http://pkgconf.org/ [3] https://nullprogram.com/blog/2023/01/18/ https://nullprogram.com/blog/2023/01/18/
hgs3 2y ago
> Also, C programmers don't seem to use any package managers other than the default system package manager and maybe git sub-modules (at least, not that I know of). For what it's worth, as someone who primarily writes C, not C++, I use the system package manager, vendoring, and sometimes Git submodules, depending on the project. On Windows, when I'm using MSYS2, I use the pacman package manager. If I'm targeting MSVC, I use CMake. For CMake, on Windows, I create my own directory where I place prebuilt dependencies for CMake to find [1]. With this approach, I can rely on CMake's builtin find_package behavior (no need for vcpkg and configure-time toolchain flags). [1] https://cmake.org/cmake/help/latest/command/find_package.html#config-mode-search-procedure https://cmake.org/cmake/help/latest/command/find_package.htm...