From d5db8fc2919e6cdfc7981b38ffe8884b5ff01205 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Vladim=C3=ADr=20Vondru=C5=A1?= Date: Mon, 22 Jan 2018 10:28:52 +0100 Subject: [PATCH] doc: improve vcpkg documentation. Thanks, Doxygen. https://bugzilla.gnome.org/show_bug.cgi?id=792774 --- doc/building.dox | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/doc/building.dox b/doc/building.dox index b8b2cd907..5ab099967 100644 --- a/doc/building.dox +++ b/doc/building.dox @@ -70,11 +70,20 @@ vcpkg install corrade --head vcpkg install magnum --head @endcode +This by default installs a 32-bit dynamic version of the package, you can use +@cb{.bat} vcpkg install magnum:x64-windows[-static] @ce to install a 64-bit +(static) version instead. See the +vcpkg triplet documentation +for more information. + Packages installed using Vcpkg can be used straight away in Visual Studio --- all you need to do is to @cpp #include @ce the headers you want, the buildsystem will do all needed library linking and setup behind the scenes automatically. (Cool, isn't it?) +@note If Visual Studio doesn't find the packages, check its verbose output, it + might point to a mismatch of the triplet above or broken vcpkg integration. + In order to make Magnum projects installed using Vcpkg available to CMake-based projects, specify the Vcpkg toolchain file on the command line when invoking CMake in a fresh build directory, for example: