search

build-cpp / cmkr

Modern build system based on CMake and TOML.
https://cmkr.build
MIT License
423 stars 28 forks source link

Allow using local vcpkg #119

Closed kem0x closed 9 months ago

kem0x commented 10 months ago

As the title implies, there's no option to use locally installed vcpkg, instead of reinstalling vcpkg in every project.

ZehMatt commented 9 months ago

This ensures that everyone is on the same version and I believe this is intentional.

kem0x commented 9 months ago

This ensures that everyone is on the same version and I believe this is intentional.

this should be optional as it's really inconvenient with mutliple projects, lets say im using LLVM while i already have it compiled on my local vcpkg clone why would i have to compile for another 8 hours everytime i create a project that uses llvm with cmkr?

mrexodia commented 9 months ago

You should just use find-package directly in that case and set the right CMAKE_PREFIX_PATH.

kem0x commented 9 months ago

i still believe it's redundant and disk consuming to have the same vcpkg packages installed in every project too 🤷‍♂️

mrexodia commented 9 months ago

Yeah you’re not wrong, but it’s a fundamental design decision of manifest mode. CMake provides functionality to reuse precompiled packages. Unfortunately vcpkg doesn’t integrate with it properly.

It’s also possible to use the toolchain file with vcpkg, but this isn’t really something for cmkr to handle.