Open the Command Palette (P (Windows, Linux Ctrl+Shift+P)) and run the CMake: Quick Start command: Enter a project name. It should be defined as specified but with straight slashes. The CMake Tools extension can create the files for a basic CMake project for you. Run CMake with -DINSTALL_DIR:STRING=D:\occt and with -DCMAKE_INSTALL_PREFIX:STRING=D:\occt and check the INSTALL_DIR value in cache. I expect that for VS2022 the path will be very similar. From here you can run: > where cmake C:Program Files (x86)Microsoft Visual Studio2019Communit圜ommon7IDECommonExtensionsMicrosoftCMakeCMakebincmake.exe. This should be fixed - it seems that TO_CMAKE_PATH function should be used when processing this variable.Īlso, as soon as Bug 1 is fixed, it will be necessary to check if Bug 2 is not reproduced with CMAKE_INSTALL_PREFIX (note: with standard way, without any customization, CMAKE_INSTALL_PREFIX is correctly processed by CMake). Launch the Native Tools Command Prompt (accessible via the Start Menu). On Windows, if INSTALL_DIR is specified in native Windows style - with back slashes, the configuration fails. So it should be safe to use CMAKESYSTEMPROCESSOR even if you're cross-compiling. Set (CMAKE_INSTALL_PREFIX "C:/opencascade-$")īug 2. According to the documentation, CMAKESYSTEMPROCESSOR returns the architecture of the CPU you're compiling for, while CMAKEHOSTSYSTEMPROCESSOR returns the achitecture of the CPU CMake is running on. # set default install directory for Windows which returns the same result This is not MSYS both in Windows cmd and MSYS2 shell. On Linux, this variable defaults to "/usr/local", while on Windows, it defaults to "C:/Program Files" ( ).Īll dependent installation directories (for includes, libs, executables, resources, docs, adm files etc) are inherited from CMAKE_INSTALL_PREFIX.īut 1: On Windows, OCCT hardcodes CMAKE_INSTALL_PREFIX to : With CMake, the standard way to specify installation directory is to use CMAKE_INSTALL_PREFIX variable:Ĭmake -DCMAKE_INSTALL_PREFIX=/path/to/the/install/dir. At the first project command the choices of compiler and target system are made and you cannot change the effects of this later. This is convenient to keep a source code and build results in different folders. Youre not supposed to write CMAKESYSTEMNAME after the first project () command is encountered by CMake. make command, executed after this, builds the program, using generated makefile (s) as an input. 0027355: Configuration, CMake: install path on Windows is incorrectly processed generates makefiles in the current directory, using.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |