OpenCascade/occt
1
0
Fork 0
mirror of https://git.dev.opencascade.org/repos/occt.git synced 2025-04-03 17:56:21 +03:00
Code Packages Releases Activity
occt/dox/dev_guides/building/building.md
ibs 9f33b387e2 0024888: Refactoring of OCCT CMake meta-project 
user sees just dirs of libs, shared libs and headers of 3rdparty products
documentation updated

3rdparty search priority was fixed: 1. user paths; 2. system paths
3rdparty debug usage fixed
vtk search introduced
occt information, generated by wok, was divided onto two files: occt_toolkits.cmake and occt_inc_toolkits.cmake
additional behavior of cmake search for freetype 2.5.1 and above

CMake (version < 3.0) don't know about new place of config/ftheader.h in freetype 2.5.1. There are cases when cmake seeks config/ftheader.h in defined place (3RDPARTY_FREETYPE_DIR variable), doesn't find it and start new search in system places. If system has own freetype header- cmake will find it and 3RDPARTY_FREETYPE* variables will point to different places. This situation is avoided

tcl, freetype, vtk are checked before usage of it (CSF variables usage)
tbb search mechanism was refactored
freetype search is processed by default cmake mechanism
tcl search is processed by default cmake mechanism

3rdparty macro seeks debug libraries (and release if debug ones aren't found); 3rdparty dll is sought in win case only

ADD_SUBDIRECTORY preferred to SUBDIRS

gendoc.bat search for tclsh.exe in user's system

0025141: CMake / MinGW: link recipe fails due to long command

0025146: Porting to Android

OCCT documentation updated. "Building with CMake and ADT for Android" article added

[CMAKE] custom.sh.in uses library variables instead unused dll ones.

-DDEBUG remove from CMAKE_CXX_FLAGS_DEBUG and CMAKE_C_FLAGS_DEBUG

hide unused 3rdparty in android case

also messages of freetype search mechanism slightly updated
2014-09-18 15:22:41 +04:00

1.7 KiB
Raw Blame History

Building OCCT from sources

In order to build OCCT libraries from these sources for use in your program, you need to:

  1. Make sure you have all required third-party libraries installed (check software requirements in \ref OCCT_OVW_SECTION_5 "Overview").

    See the following documents for short guide to installation of third-party libraries on different platforms:

    • \subpage occt_dev_guides__building_3rdparty_windows
    • \subpage occt_dev_guides__building_3rdparty_linux
    • \subpage occt_dev_guides__building_3rdparty_osx

  2. If you use bare OCCT sources from Git repository or made some changes affecting CDL files or dependencies of OCCT toolkits, you need to update header files generated from \ref occt_dev_guides__cdl "CDL", and regenerate build scripts for your environment using WOK. See \subpage occt_dev_guides__building_wok for details.

    Skip to step 3 if you use complete source package (e.g. official OCCT release) without changes in CDL.

  3. Build using your preferred build tool.

    • \subpage occt_dev_guides__building_automake "Building on Linux with Autotools"
    • \subpage occt_dev_guides__building_cmake "Building with CMake (cross-platform)"
    • \subpage occt_dev_guides__building_android "Building with CMake and ADT for Android (cross-platform)"
    • \subpage occt_dev_guides__building_code_blocks "Building on Mac OS X with Code::Blocks"
    • \subpage occt_dev_guides__building_msvc "Building on Windows with MS Visual Studio"
    • \subpage occt_dev_guides__building_xcode "Building on Mac OS X with Xcode"

The current version of OCCT can be consulted in the file src/Standard/Standard_Version.hxx