mirror of
https://git.dev.opencascade.org/repos/occt.git
synced 2025-09-08 14:17:06 +03:00
0024943: Port MFC samples to UNICODE for compatibility with VS2013
Add vc12 project files for MFC samples. CMake - add Unicode option for MFC samples CMake - do not set MFC option globally Update description of Cmake building procedure for MFC sample Correction of cmake.md and automake.md 0024943: Port MFC sample to UNICODE for compatibility with VS2013 The formatting of developer guides about OCCT building with various build systems has been improved. automake article clean up
This commit is contained in:
kgv
bugmaster
@@ -1,71 +1,72 @@
|
||||
Building with Automake {#occt_dev_guides__building_automake}
|
||||
======================
|
||||
|
||||
This file describes steps to build OCCT libraries from complete source
|
||||
archive on Linux with GNU build system (Autotools).
|
||||
This file describes steps to build OCCT libraries from a complete source
|
||||
archive on Linux with **Autotools** GNU build system.
|
||||
|
||||
If you are building OCCT from bare sources (as in Git repository), or do some
|
||||
If you build OCCT from bare sources (as in Git repository), or do some
|
||||
changes affecting CDL files, you need to use WOK to re-generate header files
|
||||
and build scripts / projects. See paragraph 1 \ref occt_dev_guides__building_wok for instructions.
|
||||
|
||||
Before building OCCT, you need to install required third-party libraries; see paragraph 1 of
|
||||
Before building OCCT, you need to install the required third-party libraries; see paragraph 1 of
|
||||
\ref occt_dev_guides__building for instructions.
|
||||
|
||||
Note that during compilation by makefiles on some Linux OS on a station with
|
||||
Note that during compilation by makefiles on Linux station with
|
||||
NVIDIA video card you may experience problems because the installation
|
||||
procedure of NVIDIA video driver removes library libGL.so included in package
|
||||
libMesaGL from directory /usr/X11R6/lib and places this library libGL.so in
|
||||
directory /usr/lib. However, libtool expects to find the library in directory
|
||||
/usr/X11R6/lib, which causes compilation crash (See /usr/X11R6/lib/libGLU.la).
|
||||
procedure of NVIDIA video driver removes library *libGL.so* included in package
|
||||
*libMesaGL* from directory <i>/usr/X11R6/lib</i> and places this library *libGL.so* in
|
||||
directory <i>/usr/lib</i>. However, *libtool* expects to find the library in directory
|
||||
<i>/usr/X11R6/lib</i>, which causes compilation crash (See <i>/usr/X11R6/lib/libGLU.la </i>).
|
||||
|
||||
To prevent this, suggest making links:
|
||||
To prevent this, it is suggested to make links:
|
||||
|
||||
ln -s /usr/lib/libGL.so /usr/X11R6/lib/libGL.so
|
||||
ln -s /usr/lib/libGL.la /usr/X11R6/lib/libGL.la
|
||||
|
||||
1.In OCCT root folder, launch build_configure script
|
||||
ln -s /usr/lib/libGL.so /usr/X11R6/lib/libGL.so
|
||||
ln -s /usr/lib/libGL.la /usr/X11R6/lib/libGL.la
|
||||
|
||||
This will generate files configure and Makefile.in for your system.
|
||||
|
||||
2.Go to the directory where OCCT will be built, and run configure to generate
|
||||
makefiles.
|
||||
1.In OCCT root folder, launch *build_configure* script to generate files *configure* and *Makefile.in* for your system.
|
||||
|
||||
$CASROOT/configure \<FLAGS\>
|
||||
2.Go to the directory, where OCCT will be built, and run *configure* to generate makefiles.
|
||||
|
||||
Where \<FLAGS\> is a set of options.
|
||||
|
||||
$CASROOT/configure \<FLAGS\>
|
||||
|
||||
Where <i> \<FLAGS\> </i> is a set of options.
|
||||
The following flags are mandatory:
|
||||
|
||||
* --with-tcl= defines location of tclConfig.sh
|
||||
* --with-tk= defines location of tkConfig.sh
|
||||
* --with-freetype= defines location of installed FreeType product
|
||||
* --prefix= defines location for the installation of OCCT binaries
|
||||
* <i> --with-tcl= </i> defines the location of *tclConfig.sh*;
|
||||
* <i> --with-tk= </i> defines location of *tkConfig.sh*;
|
||||
* <i> --with-freetype= </i> defines location of installed **FreeType** product
|
||||
* <i> --prefix= </i> defines the location for installation of OCCT binaries
|
||||
|
||||
Additional flags:
|
||||
|
||||
* --with-gl2ps= defines location of installed gl2ps product
|
||||
* --with-freeimage= defines location of installed FreeImage product
|
||||
* --with-tbb-include= defines location of tbb.h
|
||||
* --with-tbb-library= defines location of libtbb.so
|
||||
* --with-opencl-include= defines location of cl.h
|
||||
* --with-opencl-library= defines location of libOpenCL.so
|
||||
* --enable-debug= yes: includes debug information, no: does not include debug information
|
||||
* --enable-production= yes: switches code optimization, no: switches off code optimization
|
||||
* --disable-draw - allows OCCT building without Draw.
|
||||
* <i> --with-gl2ps= </i> defines the location of installed **gl2ps** product;
|
||||
* <i> --with-freeimage= </i> defines the location of installed **FreeImage** product;
|
||||
* <i> --with-tbb-include= </i> defines the location of *tbb.h*;
|
||||
* <i> --with-tbb-library= </i> defines the location of *libtbb.so*;
|
||||
* <i> --with-opencl-include= </i> defines the location of *cl.h*;
|
||||
* <i> --with-opencl-library= </i> defines the location of *libOpenCL.so*;
|
||||
* <i> --enable-debug= yes: </i> includes debug information, no: does not include debug information;
|
||||
* <i> --enable-production= yes: </i> switches code optimization, no: switches off code optimization;
|
||||
* <i> --disable-draw </i> allows OCCT building without Draw.
|
||||
|
||||
If location of FreeImage, TBB, gl2ps or OpenCL is not specified, OCCT will be
|
||||
built without these optional libraries.
|
||||
If location of **FreeImage, TBB, gl2ps** or **OpenCL** is not specified, OCCT will be built without these optional libraries.
|
||||
|
||||
|
||||
Attention: 64-bit platforms are detected automatically.
|
||||
Attention: 64-bit platforms are detected automatically.
|
||||
|
||||
Example:
|
||||
Example:
|
||||
|
||||
|
||||
> ./configure -prefix=/PRODUCTS/occt-6.5.5 --with-tcl=/PRODUCTS/tcltk-8.5.8/lib --with-tk=/PRODUCTS/tcltk-8.5.8/lib --with-freetype=/PRODUCTS/freetype-2.4.10 --with-gl2ps=/PRODUCTS/gl2ps-1.3.5 --with-freeimage=/PRODUCTS/freeimage-3.14.1 --with-tbb-include=/PRODUCTS/tbb30_018oss/include --with-tbb-library=/PRODUCTS/tbb30_018oss/lib/ia32/cc4.1.0_libc2.4_kernel2.6.16.21 --with-opencl-include=/PRODUCTS/opencl-icd-1.2.11.0/include --with-opencl-library=/PRODUCTS/opencl-icd-1.2.11.0/lib
|
||||
\> ./configure -prefix=/PRODUCTS/occt-6.5.5 --with-tcl=/PRODUCTS/tcltk-8.5.8/lib --with-tk=/PRODUCTS/tcltk-8.5.8/lib --with-freetype=/PRODUCTS/freetype-2.4.10 --with-gl2ps=/PRODUCTS/gl2ps-1.3.5 --with-freeimage=/PRODUCTS/freeimage-3.14.1 --with-tbb-include=/PRODUCTS/tbb30_018oss/include --with-tbb-library=/PRODUCTS/tbb30_018oss/lib/ia32/cc4.1.0_libc2.4_kernel2.6.16.21 --with-opencl-include=/PRODUCTS/opencl-icd-1.2.11.0/include --with-opencl-library=/PRODUCTS/opencl-icd-1.2.11.0/lib
|
||||
|
||||
3.If configure exits successfully, you can build OCCT with make command.
|
||||
|
||||
> make -j8 install
|
||||
3.If configure exits successfully, you can build OCCT with *make* command.
|
||||
|
||||
To start DRAW, launch
|
||||
\> make -j8 install
|
||||
|
||||
> draw.sh
|
||||
4.To start *DRAW*, launch
|
||||
|
||||
\> draw.sh
|
||||
|
||||
@@ -3,24 +3,23 @@ Building with CMake {#occt_dev_guides__building_cmake}
|
||||
|
||||
@tableofcontents
|
||||
|
||||
This file describes steps to build OCCT libraries from complete source package
|
||||
with CMake. CMake is free software that can create GNU Makefiles, KDevelop,
|
||||
XCode, and Visual Studio project files. Version 2.6 or above of CMake is
|
||||
This file describes the steps to build OCCT libraries from a complete source package
|
||||
with **CMake**. CMake is free software that can create GNU Makefiles, KDevelop,
|
||||
XCode, and Visual Studio project files. **CMake** version 2.6 or above is
|
||||
required.
|
||||
|
||||
If you are building OCCT from bare sources (as in Git repository), or do some
|
||||
If you build OCCT from bare sources (as in Git repository) or make some
|
||||
changes affecting CDL files, you need to use WOK to re-generate header files
|
||||
and build scripts / projects. See \ref occt_dev_guides__building_wok for instructions.
|
||||
|
||||
Before building OCCT, you need to install required third-party libraries; see
|
||||
Before building OCCT, you need to install the required third-party libraries; see the
|
||||
instructions for your platform in @ref occt_dev_guides__building.
|
||||
|
||||
## Decide on location of build and install directories.
|
||||
## Define the location of build and install directories.
|
||||
|
||||
The build directory is the one where intermediate files will be created (projects / makefiles, objects, binaries).
|
||||
Each configuration to be built should have its own build directory.
|
||||
The build directory is where intermediate files (projects / makefiles, objects, binaries) will be created. Each built configuration should have its own build directory.
|
||||
|
||||
The install directory is the one where binaries will be installed after build, along with header files and resources required for OCCT use in applications.
|
||||
The install directory is where binaries will be installed after build, along with header files and resources required for OCCT use in applications.
|
||||
It is possible to install several configurations of OCCT (differentiated by platform, bitness, compiler, and build type) into the same directory.
|
||||
|
||||
It is recommended to separate build and install directories from OCCT source directory, for example:
|
||||
@@ -31,120 +30,123 @@ It is recommended to separate build and install directories from OCCT source dir
|
||||
|
||||
## CMake usage
|
||||
|
||||
Run CMake indicating path to OCCT sources ($CASROOT) and selected build directory.
|
||||
Run CMake indicating the path to OCCT sources <i>($CASROOT)</i> and selected build directory.
|
||||
|
||||
It is recommended to use GUI tools provided by CMake: cmake-gui on Windows and Mac, ccmake or cmake-gui on Linux.
|
||||
It is recommended to use GUI tools provided by CMake: *cmake-gui* on Windows and Mac, *ccmake* or *cmake-gui* on Linux.
|
||||
|
||||
### Windows:
|
||||
|
||||
Specify the root folder of OCCT ($CASROOT, it contains CMakelists.txt file) by clicking Browse Source.
|
||||
Specify the root folder of OCCT (<i>$CASROOT</i>, which contains *CMakelists.txt* file) by clicking **Browse Source**.
|
||||
|
||||
@figure{/dev_guides/building/cmake/images/cmake_image001.png}
|
||||
|
||||
Specify location (build folder) for Cmake generated project files by clicking Browse Build.
|
||||
Each configuration of the project should be built in its own directory.
|
||||
When building multiple configurations it is recommended to compose name of build directories including system, bitness, compiler, and build type (e.g., d:/occt/build/win32-vc9-debug).
|
||||
Specify the location (build folder) for Cmake generated project files by clicking **Browse Build**.
|
||||
|
||||
Configure opens the window with a drop-down list of generators supported by CMake project. Select the required generator (e.g., Visual Studio 2008) and click Finish.
|
||||
Each configuration of the project should be built in its own directory. When building multiple configurations it is recommended to indicate in the name of build directories the system, bitness, compiler, and build type (e.g., <i>d:/occt/build/win32-vc9-debug</i> ).
|
||||
|
||||
**Configure** opens the window with a drop-down list of generators supported by CMake project. Select the required generator (e.g., Visual Studio 2008) and click **Finish**.
|
||||
|
||||
@figure{/dev_guides/building/cmake/images/cmake_image002.png}
|
||||
|
||||
### Linux (ccmake variant):
|
||||
|
||||
In the console, change to the build directory and call ccmake with the path to the source directory of the project:
|
||||
In the console, change to the build directory and call *ccmake* with the path to the source directory of the project:
|
||||
|
||||
> cd ~/occt/build/debug
|
||||
> ccmake ~/occt
|
||||
|
||||
@figure{/dev_guides/building/cmake/images/cmake_image003.png}
|
||||
|
||||
Press "c" to configure.
|
||||
Press *c* to configure.
|
||||
|
||||
Use of *cmake-gui* is the same as described above for Windows.
|
||||
*cmake-gui* is used in the same way as described above for Windows.
|
||||
|
||||
### Mac OS:
|
||||
|
||||
Use cmake-gui (Applications -> CMake 2.8-10.app) to generate project files for the chosen build environment (e.g., XCode).
|
||||
Use *cmake-gui* **Applications -> CMake 2.8-10.app** to generate project files for the chosen build environment (e.g., XCode).
|
||||
|
||||
@figure{/dev_guides/building/cmake/images/cmake_image004.png}
|
||||
|
||||
## OCCT Configuration
|
||||
|
||||
The error message which appears at the end of configuration process, informs you about the required variables
|
||||
The error message, which appears at the end of configuration process, informs you about the required variables,
|
||||
which need to be defined. This error will appear until all required variables are defined correctly.
|
||||
Note: In cmake-gui there is "grouped" option, which groups variables with a common prefix.
|
||||
|
||||
### Selection of components to be built
|
||||
Note: In *cmake-gui* there is "grouped" option, which groups variables with a common prefix.
|
||||
|
||||
The variables with "BUILD_" prefix allow specifying OCCT components and
|
||||
### Selection of the components to be built
|
||||
|
||||
The variables with <i>BUILD_</i> prefix allow specifying OCCT components and
|
||||
configuration to be built:
|
||||
|
||||
* BUILD_CONFIGURATION - defines configuration to be built (Release by default).
|
||||
* BUILD_<MODULE> - specify whether corresponding OCCT module should be
|
||||
built (all toolkits). Note that even if whole module is not
|
||||
* *BUILD_CONFIGURATION* - defines configuration to be built (Release by default).
|
||||
* <i>BUILD_<MODULE></i> - specifies whether the corresponding OCCT module should be
|
||||
built (all toolkits). Note that even if the whole module is not
|
||||
selected for build, its toolkits used by other toolkits
|
||||
selected for build will be included automatically.
|
||||
* BUILD_TOOLKITS - allows including additional toolkits from non-selected
|
||||
* *BUILD_TOOLKITS* - allows including additional toolkits from non-selected
|
||||
modules (should be list of toolkit names separated by a
|
||||
space or a semicolon).
|
||||
* BUILD_SAMPLES - specify whether OCCT MFC samples should be built.
|
||||
* BUILD_PATCH_DIR - optionally specify additional folder containing patched OCCT source files.
|
||||
* *BUILD_SAMPLES* - specifies whether OCCT MFC samples should be built.
|
||||
* *BUILD_PATCH_DIR* - optionally specifies additional folder containing patched OCCT source files.
|
||||
The patch may contain arbitrary subset of OCCT source files (including CMake scripts, templates, etc.), organized in the same structure of folders as OCCT.
|
||||
The projects generated by CMake will use files found in the patch folder instead of corresponding files of OCCT.
|
||||
The projects generated by CMake will use files found in the patch folder instead of the corresponding files of OCCT.
|
||||
|
||||
Check variables with "USE_" prefix (USE_FREEIMAGE, USE_GL2PS, USE_TBB, and
|
||||
USE_OPENCL) if you want to enable use of the corresponding optional 3rd-party
|
||||
Check variables with <i>USE_</i> prefix (<i>USE_FREEIMAGE, USE_GL2PS, USE_TBB,</i> and
|
||||
<i>USE_OPENCL</i>) if you want to enable use of the corresponding optional 3rd-party
|
||||
library.
|
||||
|
||||
### 3rd-party configuration (The variables with 3RDPARTY_ prefix)
|
||||
### 3rd-party configuration (The variables with <i>3RDPARTY_</i> prefix)
|
||||
|
||||
If you have 3rd-party libraries in a non-default location
|
||||
(e.g., on Windows, binaries downloaded from "http://www.opencascade.org/getocc/download/3rdparty/"),
|
||||
specify 3RDPARTY_DIR variable that points to the folders of 3rdparty libraries (some or all).
|
||||
At the next configuration step the 3rd-party libraries will be searched for in 3RDPARTY_DIR directory, and stored in 3RDPARTY_\<LIBRARY\>_DIR variables.
|
||||
(e.g., on Windows, binaries downloaded from http://www.opencascade.org/getocc/download/3rdparty/")
|
||||
specify *3RDPARTY_DIR* variable that points to the folders of 3rd-party libraries (some or all).
|
||||
|
||||
At the next configuration step the 3rd-party libraries will be searched for in *3RDPARTY_DIR* directory, and stored in *3RDPARTY_\<LIBRARY\>_DIR* variables.
|
||||
|
||||
The procedure expects to find binary and header files of each 3rd-party library in its own sub-directory, separated by sub-directories *bin*, *lib*, and *include*.
|
||||
|
||||
Press "Configure" ("c" key for ccmake).
|
||||
Press **Configure** (**c** key for ccmake).
|
||||
|
||||
The result of the 3rdparty product search will be recorded in the corresponding variables:
|
||||
|
||||
* 3RDPARTY_\<PRODUCT\>_DIR - path to the product directory (with directory name) (e.g., D:/3rdparty/Tcl-8.5.12.0-32)
|
||||
* 3RDPARTY_\<PRODUCT\>_LIBRARY - path to the .lib libraries (with the library name) (e.g., D:/3rdparty/Tcl-8.5.12.0-32/lib/tcl85.lib).
|
||||
In non-windows case, this variable is the same as 3RDPARTY_\<PRODUCT\>_DLL.
|
||||
* 3RDPARTY_\<PRODUCT\>_INCLUDE - path to the include directory that contains the required header file (with "include" name) (e.g., D:/3rdparty/Tcl-8.5.12.0-32/include including tcl.h)
|
||||
* 3RDPARTY_\<PRODUCT\>_DLL - path to the .dll/.so/.dylib library (with the library name) (e.g., D:/3rdparty/Tcl-8.5.12.0-32/bin/tcl85.dll)
|
||||
* *3RDPARTY_\<PRODUCT\>_DIR* - path to the product directory (with directory name) (e.g. <i>D:/3rdparty/Tcl-8.5.12.0-32</i>)
|
||||
* *3RDPARTY_\<PRODUCT\>_LIBRARY* - path to .lib libraries (with the library name) (e.g. <i>D:/3rdparty/Tcl-8.5.12.0-32/lib/tcl85.lib</i>).
|
||||
In non-windows case, this variable is the same as *3RDPARTY_\<PRODUCT\>_DLL*.
|
||||
* *3RDPARTY_\<PRODUCT\>_INCLUDE* - path to the include directory that contains the required header file (with "include" name) (e.g., <i>D:/3rdparty/Tcl-8.5.12.0-32/include including tcl.h</i>)
|
||||
* *3RDPARTY_\<PRODUCT\>_DLL* - path to <i>.dll/.so/.dylib</i> library (with the library name) (e.g., <i>D:/3rdparty/Tcl-8.5.12.0-32/bin/tcl85.dll</i>)
|
||||
|
||||
The search process is as follows:
|
||||
|
||||
1. Common path: 3RDPARTY_DIR
|
||||
2. Path to particular 3rd-party library: 3RDPARTY_\<PRODUCT\>_DIR
|
||||
1. Common path: *3RDPARTY_DIR*
|
||||
2. Path to a particular 3rd-party library: *3RDPARTY_\<PRODUCT\>_DIR*
|
||||
3. Paths to headers and binaries:
|
||||
1. 3RDPARTY_\<PRODUCT\>_INCLUDE
|
||||
2. 3RDPARTY_\<PRODUCT\>_LIBRARY
|
||||
3. 3RDPARTY_\<PRODUCT\>_DLL
|
||||
1. *3RDPARTY_\<PRODUCT\>_INCLUDE*
|
||||
2. *3RDPARTY_\<PRODUCT\>_LIBRARY*
|
||||
3. *3RDPARTY_\<PRODUCT\>_DLL*
|
||||
|
||||
If a variable of any level is not defined (empty or \<variable name\>-NOTFOUND)
|
||||
If a variable of any level is not defined (empty or <i> \<variable name\>-NOTFOUND </i>)
|
||||
and the upper level variable is defined, the content of the non-defined variable
|
||||
will be searched for at the next configuration step. If search process in level 3
|
||||
does not find the required files, it searches in default places also.
|
||||
|
||||
**Note**: the names of searched libraries and header files are hardcoded.
|
||||
Freetype search process tries to find ft2build.h file in 3RDPARTY_FREETYPE INCLUDE dir
|
||||
and after that adds "3RDPARTY_FREETYPE_INCLUDE /freetype2" path to common includes if it exists.
|
||||
**Note**: the names of searched libraries and header files are hard-coded.
|
||||
Freetype search process tries to find *ft2build.h* file in *3RDPARTY_FREETYPE INCLUDE* directory
|
||||
and after that adds *3RDPARTY_FREETYPE_INCLUDE /freetype2* path to common includes if it exists.
|
||||
|
||||
Important: If BUILD_CONFIGURATION variable is changed - at the next configuration
|
||||
3RDPARTY_ variables will be replaced by the search process result, except for the 3RDPARTY_DIR variable.
|
||||
Important: If *BUILD_CONFIGURATION* variable is changed, at the next configuration
|
||||
*3RDPARTY_ variables* will be replaced by the search process result, except for the *3RDPARTY_DIR* variable.
|
||||
|
||||
*Note*: CMake will produce an error after the configuration step until all required variables are defined correctly.
|
||||
If the search result (include path, or library path, or dll path) does not meet your expectations -
|
||||
you can change 3RDPARTY_\<PRODUCT\>_DIR variable, clear (if they are not empty)
|
||||
3RDPARTY_\<PRODUCT\>_DLL, 3RDPARTY_\<PRODUCT\>_INCLUDE_DIR and 3RDPARTY_\<PRODUCT\>_LIBRARY variables
|
||||
*Note* : CMake will produce an error after the configuration step until all required variables are defined correctly.
|
||||
If the search result (include path, or library path, or dll path) does not meet your expectations,
|
||||
you can change *3RDPARTY_\<PRODUCT\>_DIR variable*, clear (if they are not empty)
|
||||
*3RDPARTY_\<PRODUCT\>_DLL, 3RDPARTY_\<PRODUCT\>_INCLUDE_DIR* and 3RDPARTY_\<PRODUCT\>_LIBRARY variables
|
||||
(or clear one of them) and run the configuration process again.
|
||||
|
||||
At this time the search will be performed in the new identified directory
|
||||
At this time the search will be performed in the newly identified directory
|
||||
and the result will be recorded to empty variables (non-empty variables will not be replaced).
|
||||
|
||||
For example, (Linux case) 3RDPARTY_FREETYPE_DIR variable
|
||||
For example, (Linux case) *3RDPARTY_FREETYPE_DIR* variable
|
||||
|
||||
/PRODUCTS/maintenance/Mandriva2010/freetype-2.3.7
|
||||
|
||||
@@ -152,74 +154,81 @@ can be changed to
|
||||
|
||||
/PRODUCTS/maintenance/Mandriva2010/freetype-2.4.10
|
||||
|
||||
and the related variables: 3RDPARTY_FREETYPE_DLL, 3RDPARTY_FREETYPE_INCLUDE_DIR and 3RDPARTY_FREETYPE_LIBRARY will be cleared.
|
||||
and the related variables *3RDPARTY_FREETYPE_DLL, 3RDPARTY_FREETYPE_INCLUDE_DIR* and *3RDPARTY_FREETYPE_LIBRARY* will be cleared.
|
||||
|
||||
@figure{/dev_guides/building/cmake/images/cmake_image005.png}
|
||||
|
||||
During configuration process the cleaned variables will be filled with new found values.
|
||||
During the configuration process the cleaned variables will be filled with new found values.
|
||||
|
||||
###The variables with INSTALL_ prefix:
|
||||
|
||||
Define in INSTALL_DIR variable the path where will be placed built OCCT files (libraries, executables and headers).
|
||||
If INSTALL_\<PRODUCT\> variable is checked - 3rd-party products will be copied to the install directory.
|
||||
Define in *INSTALL_DIR* variable the path, where the built OCCT files (libraries, executables and headers) will be placed.
|
||||
If <i>INSTALL_\<PRODUCT\></i> variable is checked, 3rd-party products will be copied to the install directory.
|
||||
|
||||
#### At the end of the configuration process "configuring done" message will be shown and the generation process can be started.
|
||||
At the end of the configuration process "configuring done" message will be shown and the generation process can be started.
|
||||
|
||||
## OCCT Generation
|
||||
|
||||
This will create makefiles or project files for your build system.
|
||||
This procedure will create makefiles or project files for your build system.
|
||||
|
||||
### Windows
|
||||
|
||||
Click Generate button and wait until the generation process is finished.
|
||||
Then the project files will appear in the build folder (e.g., d:/occt/build/win32-vc9-release).
|
||||
Click **Generate** button and wait until the generation process is finished.
|
||||
Then the project files will appear in the build folder (e.g. <i> d:/occt/build/win32-vc9-release </i>).
|
||||
|
||||
### Linux
|
||||
|
||||
When the configuration is complete, start the generation process by pressing "g".
|
||||
When the configuration is complete, start the generation process by pressing **g**.
|
||||
|
||||
@figure{/dev_guides/building/cmake/images/cmake_image006.png}
|
||||
|
||||
### Mac OS X
|
||||
|
||||
Click Generate button and wait until the generation process is finished.
|
||||
Then the project files will appear in the build folder (e.g., /Developer/occt/build/XCode).
|
||||
Click **Generate** button and wait until the generation process is finished.
|
||||
Then the project files will appear in the build folder (e.g. <i> /Developer/occt/build/XCode </i>).
|
||||
|
||||
## OCCT Building
|
||||
|
||||
The install folder contains bin, inc, lib and res folders and a script to run DRAWEXE (draw.bat or draw.sh).
|
||||
"bin" contains executables, DLL (Windows) style shared libraries and pdb-files in OCCT debug version,.
|
||||
"lib" contains the import parts of DLL libraries.
|
||||
"inc" contains header files.
|
||||
"res" contains all required source files for OCCT.
|
||||
The install folder contains *bin, inc, lib* and *res* folders and a script to run *DRAWEXE* (*draw.bat* or *draw.sh*).
|
||||
* **bin** contains executables, DLL (Windows) style shared libraries and pdb-files in OCCT debug version.
|
||||
* **lib** contains the import parts of DLL libraries.
|
||||
* **inc** contains header files.
|
||||
* **res** contains all required source files for OCCT.
|
||||
|
||||
### Windows (Visual studio)
|
||||
|
||||
Go to the build folder, start the Visual Studio solution (OCCT.sln) and build it by clicking Build - Build Solution.
|
||||
When the building process finished, build the INSTALL project
|
||||
(by default the build solution process skips the building of the INSTALL project) to move the above files to INSTALL_DIR.
|
||||
For this in the solution explorer right click on the INSTALL project and select Project Only - Build Only INSTALL.
|
||||
Go to the build folder, start the Visual Studio solution *OCCT.sln* and build it by clicking **Build -> Build Solution**.
|
||||
|
||||
When the building process is finished, build the *INSTALL* project (by default the build solution process skips the building of the INSTALL project) to move the above files to *INSTALL_DIR*.
|
||||
|
||||
For this, right-click on the *INSTALL* project and select **Project Only -> Build Only** -> *INSTALL* in the solution explorer.
|
||||
|
||||
### Linux (make)
|
||||
Change directory to binary dir and run make command
|
||||
|
||||
Change directory to the directory with binaries and run *make* command
|
||||
|
||||
> make
|
||||
|
||||
To copy all libraries, executables and chosen 3rd-party libraries run "make" command with "install" argument
|
||||
To copy all libraries, executables and chosen 3rd-party libraries run *make* command with *install* argument
|
||||
|
||||
> make install
|
||||
|
||||
This command will move the above files to INSTALL_DIR.
|
||||
This command will move the above files to *INSTALL_DIR*.
|
||||
|
||||
### Mac OS X (XCode)
|
||||
|
||||
Go to the build folder, start the XCode solution (OCCT.xcodeproj)
|
||||
and build it by clicking Build -> Build.
|
||||
Please notice that XCode may have worst responsibility to user actions
|
||||
due to sources processing at first start.
|
||||
Go to the build folder, start XCode solution *OCCT.xcodeproj* and build it by clicking **Build -> Build**.
|
||||
Please notice that XCode may lag because it processes sources at the first start.
|
||||
|
||||
When the building process finished, build the INSTALL project
|
||||
(by default the build solution process skips the building of the INSTALL project)
|
||||
to move the above files to INSTALL_DIR.
|
||||
Notice that env.sh (configure PATH and DYLD_LIBRARY_PATH environment variables
|
||||
as well as Draw Harness extra variables) and draw.sh (to launch DRAWEXE) will be created in target directory.
|
||||
When the building process has finished, build the *INSTALL* project (by default the build solution process skips the building of *INSTALL* project) to move the above files to *INSTALL_DIR*.
|
||||
Notice that *env.sh* (which configures *PATH* and *DYLD_LIBRARY_PATH* environment variables
|
||||
as well as Draw Harness extra variables) and *draw.sh* (to launch *DRAWEXE* ) will be created in the target directory.
|
||||
|
||||
### MFC samples
|
||||
|
||||
On Windows you can also build binaries of MFC samples together with OCCT. For this, activate **BUILD_Samples** check-box in CMake configuration dialog.
|
||||
|
||||
@figure{/dev_guides/building/cmake/images/cmake_image007.png}
|
||||
|
||||
Please take into account that MFC sample binaries will be installed in the same folder as OCCT binaries during building of *INSTALL* project.
|
||||
To run an MFC sample use *sample.bat* launcher. The command format is: <i>sample.bat <SampleName></i> (e.g. <i>sample.bat ImportExport</i>).
|
||||
|
||||
BIN
dox/dev_guides/building/cmake/images/cmake_image007.png
Normal file
BIN
dox/dev_guides/building/cmake/images/cmake_image007.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 22 KiB |
@@ -1,64 +1,70 @@
|
||||
Building with Code::Blocks on Mac OS X {#occt_dev_guides__building_code_blocks}
|
||||
======================================
|
||||
|
||||
This file describes steps to build OCCT libraries from complete source package
|
||||
on Mac OS X with Code::Blocks.
|
||||
This file describes steps to build OCCT libraries from a complete source package
|
||||
on Mac OS X with **Code::Blocks**.
|
||||
|
||||
If you are building OCCT from bare sources (as in Git repository), or do some
|
||||
If you build OCCT from bare sources (as in Git repository) or do some
|
||||
changes affecting CDL files, you need to use WOK to re-generate header files
|
||||
and build scripts / projects. See \ref occt_dev_guides__building_wok for instructions.
|
||||
|
||||
Before building OCCT, you need to install required third-party libraries; see
|
||||
Before building OCCT, you need to install the required third-party libraries; see
|
||||
paragraph 1 of \ref occt_dev_guides__building for details.
|
||||
|
||||
1. Add paths to the mandatory 3rd-party products (Tcl/Tk and FreeType) in file
|
||||
custom.sh located in \<OCCT_ROOT_DIR\>. For this:
|
||||
1. Add paths to the mandatory 3rd-party products (**Tcl/Tk** and **FreeType**) in file
|
||||
*custom.sh* located in <i>\<OCCT_ROOT_DIR\></i>. For this:
|
||||
|
||||
1.1. Add paths to the includes in variable "CSF_OPT_INC";
|
||||
1.1. Add paths to the includes in variable *CSF_OPT_INC*;
|
||||
|
||||
1.2. Add paths to the binary libraries in variable "CSF_OPT_LIB64";
|
||||
1.2. Add paths to the binary libraries in variable *CSF_OPT_LIB64*;
|
||||
|
||||
All paths should be separated by ":" symbol.
|
||||
|
||||
2. Add paths to the optional 3rd-party libraries (TBB, gl2ps and FreeImage)
|
||||
in the aforementioned environment variables "CSF_OPT_INC" and
|
||||
"CSF_OPT_LIB64" from file custom.sh.
|
||||
2. Add paths to the optional 3rd-party libraries (**TBB, gl2ps** and **FreeImage**)
|
||||
in the aforementioned environment variables *CSF_OPT_INC* and
|
||||
*CSF_OPT_LIB64* from file *custom.sh*.
|
||||
|
||||
If you want to build OCCT without the optional libraries perform the
|
||||
following steps:
|
||||
|
||||
2.1 Disable unnecessary library in custom.sh by setting the corresponding
|
||||
variable HAVE_\<LIBRARY_NAME\> to "false".
|
||||
variable <i>HAVE_\<LIBRARY_NAME\></i> to *false*.
|
||||
|
||||
export HAVE_GL2PS=false
|
||||
~~~~~
|
||||
export HAVE_GL2PS=false
|
||||
~~~~~
|
||||
|
||||
2.2 Remove this library from Linker settings in Code::Blocks for each project
|
||||
that uses it: right click on the required project, choose "Build options",
|
||||
go to "Linker settings" tab in the opened window , select unnecessary
|
||||
libraries and click "Delete" button.
|
||||
2.2 Remove this library from Linker settings in **Code::Blocks** for each project
|
||||
that uses it: right click on the required project, choose **Build options**,
|
||||
go to **Linker settings** tab in the opened window , select unnecessary
|
||||
libraries and click **Delete** button.
|
||||
|
||||
3. Open Terminal application
|
||||
|
||||
4. Enter \<OCCT_ROOT_DIR\>:
|
||||
4. Enter <i> \<OCCT_ROOT_DIR\></i>:
|
||||
|
||||
~~~~~
|
||||
cd \<OCCT_ROOT_DIR\>
|
||||
~~~~~
|
||||
|
||||
5. To start Code::Blocks, run the command /codeblocks.sh
|
||||
5. To start **Code::Blocks**, run the command <i>/codeblocks.sh</i>
|
||||
|
||||
6. To build all toolkits, click "Build->Build workspace" in the menu bar.
|
||||
6. To build all toolkits, click **Build->Build workspace** in the menu bar.
|
||||
|
||||
|
||||
To start DRAWEXE, which has been built with Code::Blocks on Mac OS X, perform
|
||||
To start *DRAWEXE*, which has been built with **Code::Blocks** on Mac OS X, perform
|
||||
the following steps:
|
||||
|
||||
1. Open Terminal application
|
||||
1.Open Terminal application
|
||||
|
||||
2. Enter \<OCCT_ROOT_DIR\>:
|
||||
2.Enter <i>\<OCCT_ROOT_DIR\></i>:
|
||||
|
||||
~~~~~
|
||||
cd \<OCCT_ROOT_DIR\>
|
||||
~~~~~
|
||||
|
||||
3. Run script
|
||||
|
||||
3.Run the script
|
||||
~~~~~
|
||||
./draw_cbp.sh cbp [d]
|
||||
|
||||
Option "d" is used if OCCT has been built in Debug mode.
|
||||
~~~~~
|
||||
Option *d* is used if OCCT has been built in **Debug** mode.
|
||||
|
||||
@@ -1,31 +1,31 @@
|
||||
Building with MS Visual C++ {#occt_dev_guides__building_msvc}
|
||||
===========================
|
||||
|
||||
This file describes steps to build OCCT libraries from complete source
|
||||
archive on Windows with MS Visual C++.
|
||||
This file describes steps to build OCCT libraries from a complete source
|
||||
archive on Windows with <b>MS Visual C++</b>.
|
||||
|
||||
If you are building OCCT from bare sources (as in Git repository), or do some
|
||||
If you build OCCT from bare sources (as in Git repository) or do some
|
||||
changes affecting CDL files, you need to use WOK to re-generate header files
|
||||
and build scripts / projects. See \ref occt_dev_guides__building_wok for instructions.
|
||||
|
||||
Before building OCCT, you need to install required third-party libraries; see
|
||||
Before building OCCT, you need to install the required third-party libraries; see
|
||||
paragraph 1 of \ref occt_dev_guides__building for instructions.
|
||||
|
||||
1. Edit file custom.bat to define environment:
|
||||
1. Edit file *custom.bat* to define the environment:
|
||||
|
||||
- VCVER - version of Visual Studio (vc8, vc9, vc10, vc11 or vc12),
|
||||
and relevant VCVARS path
|
||||
- ARCH - architecture (32 or 64), affects only PATH variable for execution
|
||||
- HAVE_* - flags to enable or disable use of optional third-party products
|
||||
- *VCVER* - version of Visual Studio (vc8, vc9, vc10, vc11 or vc12),
|
||||
and relevant *VCVARS* path
|
||||
- *ARCH* - architecture (32 or 64), affects only *PATH* variable for execution
|
||||
- <i>HAVE_*</i> - flags to enable or disable use of optional third-party products
|
||||
- CSF_OPT_* - paths to search for includes and binaries of all used
|
||||
third-party products
|
||||
|
||||
2. Launch msvc.bat to start Visual Studio with all necessary environment
|
||||
2. Launch *msvc.bat* to start Visual Studio with all necessary environment
|
||||
variables defined.
|
||||
|
||||
Note: the MSVC project files are located in folders adm\\msvc\\vc[9-12].
|
||||
Binaries are produced in win32 or win64 folders.
|
||||
Note: the MSVC project files are located in folders <i>adm\\msvc\\vc[9-12]</i>.
|
||||
Binaries are produced in *win32* or *win64* folders.
|
||||
|
||||
3. Build with Visual Studio
|
||||
|
||||
To start DRAW, launch draw.bat.
|
||||
To start DRAW, launch *draw.bat*.
|
||||
|
||||
@@ -1,71 +1,70 @@
|
||||
Building with Xcode {#occt_dev_guides__building_xcode}
|
||||
===================
|
||||
|
||||
This file describes steps to build OCCT libraries from complete source package
|
||||
on Mac OS X with Xcode.
|
||||
This file describes steps to build OCCT libraries from a complete source package
|
||||
on Mac OS X with **Xcode**.
|
||||
|
||||
If you are building OCCT from bare sources (as in Git repository), or do some
|
||||
If you build OCCT from bare sources (as in Git repository) or do some
|
||||
changes affecting CDL files, you need to use WOK to re-generate header files
|
||||
and build scripts / projects. See \ref occt_dev_guides__building_wok for instructions.
|
||||
|
||||
Before building OCCT, you need to install required third-party libraries; see
|
||||
Before building OCCT, you need to install the required third-party libraries; see
|
||||
paragraph 1 of \ref occt_dev_guides__building for details.
|
||||
|
||||
1. Add paths to the mandatory 3rd-party products (Tcl/Tk and FreeType)
|
||||
in file custom.sh located in \<OCCT_ROOT_DIR\>. For this:
|
||||
1. Add paths to the mandatory 3rd-party products (**Tcl/Tk** and **FreeType**)
|
||||
in file *custom.sh* located in <i>\<OCCT_ROOT_DIR\> </i>. For this:
|
||||
|
||||
1.1. Add paths to the includes in variable "CSF_OPT_INC";
|
||||
1.1. Add paths to the includes in variable *CSF_OPT_INC*;
|
||||
|
||||
1.2. Add paths to the binary libraries in variable "CSF_OPT_LIB64";
|
||||
1.2. Add paths to the binary libraries in variable *CSF_OPT_LIB64*;
|
||||
|
||||
All paths should be separated by ":" symbol.
|
||||
|
||||
2. Add paths to the optional 3rd-party libraries (TBB, gl2ps and FreeImage)
|
||||
in the aforementioned environment variables "CSF_OPT_INC" and
|
||||
"CSF_OPT_LIB64" from file custom.sh.
|
||||
2. Add paths to the optional 3rd-party libraries (**TBB, gl2ps** and **FreeImage**)
|
||||
in the aforementioned environment variables *CSF_OPT_INC* and *CSF_OPT_LIB64* from file *custom.sh*.
|
||||
|
||||
If you want to build OCCT without the optional libraries perform the
|
||||
following steps:
|
||||
|
||||
2.1 Disable unnecessary library in custom.sh by setting the corresponding
|
||||
variable HAVE_<LIBRARY_NAME> to "false".
|
||||
If you want to build OCCT without the optional libraries perform the following steps:
|
||||
|
||||
2.1 Disable unnecessary library in *custom.sh* by setting the corresponding
|
||||
variable <i>HAVE_<LIBRARY_NAME></i> to *false*.
|
||||
~~~~~
|
||||
export HAVE_GL2PS=false
|
||||
|
||||
~~~~~
|
||||
2.2 Remove this library from Project navigator in Xcode for each project that
|
||||
uses it: choose the required project, right click on the unnecessary
|
||||
library and select "Delete" button.
|
||||
library and select **Delete** button.
|
||||
|
||||
3. Open Terminal application.
|
||||
|
||||
4. Enter \<OCCT_ROOT_DIR\>:
|
||||
|
||||
4. Enter <i>\<OCCT_ROOT_DIR\></i>:
|
||||
~~~~~
|
||||
cd \<OCCT_ROOT_DIR\>
|
||||
~~~~~
|
||||
5. To start **Xcode**, run command <i>/xcode.sh</i>
|
||||
|
||||
5. To start Xcode, run the command /xcode.sh
|
||||
6. To build a certain toolkit, select it in **Scheme** drop-down list in Xcode
|
||||
toolbar, press **Product** in the menu and click **Build** button.
|
||||
|
||||
6. To build a certain toolkit, select it in "Scheme" drop-down list in Xcode
|
||||
toolbar, press "Product" in the menu and click "Build" button.
|
||||
|
||||
To build the entire OCCT, create a new empty project (select "File ->
|
||||
New -> Project -> "Empty project" in the menu. Input the project name,
|
||||
e.g. "OCCT", click "Next" and "Create" buttons). Drag and drop the "OCCT"
|
||||
folder in the created "OCCT" project in the Project navigator. Select
|
||||
"File -> New -> Target -> Aggregate" in the menu. Enter the project name
|
||||
(e.g. "OCCT") and click "Finish". The "Build Phases" tab will open.
|
||||
To build the entire OCCT, create a new empty project (select **File ->
|
||||
New -> Project -> "Empty project** in the menu. Input the project name,
|
||||
e.g. *OCCT*, click **Next** and **Create** buttons). Drag and drop the *OCCT*
|
||||
folder in the created *OCCT* project in the Project navigator. Select
|
||||
**File -> New -> Target -> Aggregate** in the menu. Enter the project name
|
||||
(e.g. <i>OCCT</i>) and click **Finish**. The **Build Phases** tab will open.
|
||||
Click "+" button to add the necessary toolkits to the target project.
|
||||
It is possible to select all toolkits by pressing "Command+A" combination.
|
||||
It is possible to select all toolkits by pressing **Command+A** combination.
|
||||
|
||||
To start DRAWEXE, which has been built with Xcode on Mac OS X, perform the following steps:
|
||||
To start *DRAWEXE*, which has been built with Xcode on Mac OS X, perform the following steps:
|
||||
|
||||
1. Open Terminal application
|
||||
|
||||
2. Enter \<OCCT_ROOT_DIR\>:
|
||||
1.Open Terminal application
|
||||
|
||||
2.Enter <i>\<OCCT_ROOT_DIR\></i>:
|
||||
~~~~~
|
||||
cd \<OCCT_ROOT_DIR\>
|
||||
~~~~~
|
||||
|
||||
3. Run script
|
||||
|
||||
3.Run the script
|
||||
~~~~~
|
||||
./draw_cbp.sh xcd [d]
|
||||
|
||||
Option "d" is used if OCCT has been built in Debug mode.
|
||||
~~~~~
|
||||
Option *d* is used if OCCT has been built in **Debug** mode.
|
||||
|
||||
Reference in New Issue
Block a user