... | @@ -45,7 +45,7 @@ vcpkg supports several of them officially, for which the ports undergo strict CI |
... | @@ -45,7 +45,7 @@ vcpkg supports several of them officially, for which the ports undergo strict CI |
|
|
|
|
|
[Neither macOS nor Linux](https://vcpkg.io/en/docs/examples/overlay-triplets-linux-dynamic.html) currently have _official_ *dynamic* build support, and so the default triplets – `x64-osx` and `x64-linux`, respectively – default to *static* linkage.
|
|
[Neither macOS nor Linux](https://vcpkg.io/en/docs/examples/overlay-triplets-linux-dynamic.html) currently have _official_ *dynamic* build support, and so the default triplets – `x64-osx` and `x64-linux`, respectively – default to *static* linkage.
|
|
|
|
|
|
On the other hand, vcpkg on Windows officially supports both *shared* linkage triplets (`x64-windows`, `x86-windows`, `arm64-windows`, etc.), _as well as_ the *static* ones (`x64-windows-static`), leaving you with a [choice] (Compilation#static-vs-dynamic-linkage).
|
|
On the other hand, vcpkg on Windows officially supports both *shared* linkage triplets (`x64-windows`, `x86-windows`, `arm64-windows`, etc.), _as well as_ the *static* ones (`x64-windows-static`), leaving you with a [choice](Compilation#static-vs-dynamic-linkage).
|
|
|
|
|
|
This all means that, depending on the platform you will be working on, a triplet used will cause different linkage, which, in effect, will require different set of CMake parameters to be passed when compiling KMyMoney. Refer to the [CMake switches](Compilation#cmake-switches) section for details on that.
|
|
This all means that, depending on the platform you will be working on, a triplet used will cause different linkage, which, in effect, will require different set of CMake parameters to be passed when compiling KMyMoney. Refer to the [CMake switches](Compilation#cmake-switches) section for details on that.
|
|
|
|
|
... | | ... | |