![]() Want to adapt find_package - just add any CMake variables to toolchain file. (Other alternatives are make or mingw-w64-x8664-make, for building with GNU Make running either as a MSYS2 or MinGW process.) Building. DCMAKE_TOOLCHAIN_FILE=/./64bit.toolchain If you want to build your 3rd party ExternalProject_Add with 64 bit architecture - just pass toolchain to CMAKE_ARGS: ExternalProject_Add(ĬMAKE_ARGS. If you want to build two projects - just use same toolchain: cmake -Hproj-1 -B_builds/proj-1 -DCMAKE_TOOLCHAIN_FILE=/./64bit.toolchainĬmake -Hproj-2 -B_builds/proj-2 -DCMAKE_TOOLCHAIN_FILE=/./64bit.toolchain a tool chain (-DCMAKE_TOOLCHAIN_FILE=64bit.toolchain).When you choose Manage Configurations from the build configuration dropdown in the main toolbar, a dialog appears that shows the default CMake configurations available in Visual Studio. It's not possible to do it with CMAKE_BUILD_TYPE (at least, again, in a scalable fashion). In a CMake project, build configurations are stored in a CMakeSettings.json file. Also I'm sure you have to adapt find_package behaviour by setting some *_ROOT CMake variables. But in my opinion you're mixing unrelated stuff. ![]() ![]() build types (-DCMAKE_BUILD_TYPE=release32).So what if you want to build N projects? You have to add N options. Another question is shouldn’t the instructions for building tell the user to build the 圆4 and x86 Library binaries for the Audacity-fork-of-WX, since most people are going to be building Audacity 64 bit That would mean that they should check that \wx\lib\vc圆4dll folder exists as well. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |