11/20/2023 0 Comments Cmake vs cmake install![]() One solution is to use a language-agnostic build system such as Bazel or Meson to build your project and all of its dependencies. "Is it already installed? Use that." → "Is a pre-built binary available? Use that." → "I give up, build this sucker from source." ![]() It makes sense to offer that as an option, falling back on "build from source" as the absolute last resort because it's so complicated. My point was that downloading and linking a pre-built binary for libraries is less complex than orchestrating an entire external project build, almost certainly faster, and a hell of a lot more convenient. But if your system is not in shape to build that dependency, it just makes things worse. ![]() Which sucks for various reasons.īuilding from source (which sometimes involves CMake) is a convenience shortcut, in that provided your system is in shape to build the dependency, it doesn't matter if you have it installed, if it's even available for your system via package management, or how you're supposed to find it ( i.e. The minimum-effort solution is to just tell the user it's their problem, and they need to install it globally so the linker can find it. The original problem isn't so much an issue with CMake specifically, as it is a problem with getting and linking non-Rust dependencies. So don’t we still have the original problem? The solution that seems the most effective would be to install CMake with Rust, though I have no idea how practical that would be to do (or if CMake is even a common enough dependency to justify doing so).Īny thoughts on this issue? Is this something that other people have run into? Or am I making I a fuss about a minor inconvenience?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |