- #BUILD CMAKE LINUX INSTALL#
- #BUILD CMAKE LINUX FULL#
- #BUILD CMAKE LINUX MAC#
- #BUILD CMAKE LINUX WINDOWS#
Indicates whether VTK 3rd party is used or not. OCCT remains parallel even without TBB product TBB stands for Threading Building Blocks, the technology of Intel Corp, which comes with different mechanisms and patterns for injecting parallelism into your application. Indicates whether TBB 3rd party is used or not. Indicates whether RapidJSON product should be used in OCCT Data Exchange module for support of glTF mesh file format Indicates whether FreeImage product should be used in OCCT visualization module for support of popular graphics image formats (PNG, BMP, etc.) Possible values are Debug, Release and RelWithDebInfo Specifies the build type on single-configuration generators (such as make).
#BUILD CMAKE LINUX FULL#
The following table gives the full list of environment variables used at the configuration stage: Variable Note: There is "grouped" option, which groups variables with a common prefix. The new variables appeared after the pass of the configuration process are highlighted with red color by CMake GUI tool. The change of the state of some variables can lead to the appearance of new variables. This message will appear after each pass of the process until all required variables are specified correctly. The error message provides some information about these variables. If the command-line tool is used, run the tool from the build directory with a single argument indicating the source (relative or absolute path) directory: cd d:/tmp/occt-build-vc10-圆4 Solution and other intermediate files created during a CMake tool workingĭ:/occt-install - the installation directory that isĪble to contain several OCCT configurations It is however possible to choose one installation directory for several configurations of OCCT (differentiated by platform, bitness, compiler and build type), for example: d:/occt/ - the source directoryĭ:/tmp/occt-build-vc10-圆4 - the build directory with the generated Different configurations should be built in different build directories to avoid conflicts. The good practice is not to use the source directory as a build one.
#BUILD CMAKE LINUX INSTALL#
The installation directory is where binaries will be installed after building the INSTALL project that is created by CMake generation process, along with header files and resources required for OCCT use in applications.The mentioned process will be described below. The build or binary directory is where all files created during CMake configuration and generation process will be located.The source directory is where the sources of OCCT are located in your file system.A command-line alternative, ccmake can also be used.ĬMake deals with three directories: source, build or binary and installation.
#BUILD CMAKE LINUX MAC#
Visual Studio 2010).įor unexperienced users we recommend to start with cmake-gui – a cross-platform GUI tool provided by CMake on Windows, Mac and Linux. Note Before you start, make sure to have installed all 3-rd party products that you are going to use with OCCT see Building OCCT from sources.ĬMake is a tool that generates the actual project files for the selected target build system (e.g. However, CMake is cross-platform and can be used to build OCCT on Linux and OS X in essentially the same way.
#BUILD CMAKE LINUX WINDOWS#
Here we describe the build procedure on the example of Windows platform with Visual Studio 2010. At the same time this tool is quite intuitive, which is a significant advantage over the legacy WOK utilities.
Moreover, CMake gives you a powerful configuration tool, which allows to control many aspects of OCCT deployment. Note Compared to the previous (6.x) releases of Open CASCADE Technology, OCCT 7.x has a complete set of CMake scripts and projects, so that there is no need to use WOK anymore. OCCT requires CMake version 2.8.12 or later. This article describes the CMake-based build process, which is now suggested as a standard way to produce the binaries of Open CASCADE Technology from sources.
0 kommentar(er)
