Mar 11, 2015  i will be happy to try the Cmake branch but I am not sure where can i find it. Can you give me more detail/help?

This document contains instructions for those who intend to build the Coin library from source and install it on their system.

It does not contain any information about installing binary distributions of Coin.

We encourage you to use the CMake build configuration in favor of Autotools as all development efforts are directed to this path. The Autotools build system is still maintained but at a significantly lower priority.

CMake

Coin uses CMake 3.0 or later for the configuration, building, and installation procedures.
This means you need a build tool and a C/C++ compiler that is supported by CMake.

On Microsoft Windows platforms, you don't need to install the Cygwin environment or something equivalent anymore to get through the build procedure.
CMake will generate native projects for the build tools like Ninja, Make, XCode, or Microsoft Visual Studio/MSBuild.

Mercurial

To get the sources you need a Mercurial client, Mercurial or TortoiseHg are a good choice.
The Mercurial command hg need to be available at the command line.
Downloading the compressed sources from the Downloads section of the project won't work as the subrepositories are not be properly populated.
Instead of doing so you need to clone the repository (using an optional commit id), e.g. calling hg clone -r 30674a9 https://bitbucket.org/Coin3D/coin.

Boost

Boost C++ libraries are needed (at least version 1.45.0 from boost).
Up to now Coin only uses the header only libraries, so downloading and installing the sources without building is sufficient.
Boost binary packages are provided for Windows on sourceforge. To find out how the Visual Studio version is related to the internal numbering have a look at Internal_version_numbering.
On Linux prebuilt binaries for your distribution should be provided by the package manager.

Doxygen

As the generation of the Coin documentation is enabled by default, Doxygen is required.

NSIS

If you intend to generate an installation package of the Coin library on Windows, NSIS is required.

XQuartz, OpenMotif

If you intend to build the Coin library on macOS using X11 an appropriate X11 implementation like XQuartz as well as OpenMotif are required. You may install the packages via homebrew or macports.

First you need to find out what generators are supported by CMake on your platform.
The command cmake --help on the command line provides you an extensive list of supported generators.
We strongly recommend you to specify the generator explicitly by using CMake's option -G as it makes your build behave deterministic.
E.g., when you install an additional development environment on Windows or a newer CMake version the default compiler for the platform selected by CMake may change.
Without the generator option CMake will pick up a different compiler by default. Otherwise CMake always uses the explicitly specified generator.

For additional configuration options not mentioned on the sample command lines see 'CMake configuration options' on this page.

Linux

or

1. Get the sources using Mercurial clone command.

2. Configure the build.
   If you just want a standard installation (or regenerate the Makefiles using cached options).
   You may omit the generator, then the default generator for the platform is used.
   CMake will create the build directory if it does not exist.
   Coin uses an Out-of-source build mode, i.e. you must not run the cmake command directly from the source directory. Instead you need to run it from a separate build directory, e.g. coin_build.
   On recent CMake versions (3.13 and later) the option -H has been superseded by -S.
   Or, if available, you can edit all options in a GUI like this
   cmake-gui ./coin

3. Build the Coin library using the default build tool on the platform.
   Or, alternatively use the CMake build tool mode. This uses coin_build as build directory, builds the target all for the Release configuration and passes -j4 (parallel building with 4 cores) to the underlying default build tool (the default build tool on Linux is make).

4. Install the Coin library using the default build tool on the platform.
   Or, alternatively again use the CMake build tool mode. This uses coin_build as build directory, builds the target install for the Release configuration and passes -j4 (parallel building with 4 cores) to the underlying default build tool (the default build tool on Linux is make).

5. Build installation packages of the Coin library (optional)
   This uses CPack, a packaging tool from the CMake suite.
   If something does not work you may need to add the --verbose --debug options to the call to figure out what went wrong or is missing.

6. Finally when you are done remove the build directory
   rm -rf coin_build

Windows

or

1. Get the sources using Mercurial clone command.

2. Configure the build.
   If you just want a standard installation (or regenerate the build files using cached options).
   You may omit the generator, then the default generator for the platform is used.
   CMake will create the build directory if it does not exist.
   Coin uses an Out-of-source build mode, i.e. you must not run the cmake command directly from the source directory. Instead you need to run it from a separate build directory, e.g. coin_build.
   On recent CMake versions (3.13 and later) the option -H has been superseded by -S.
   Or, if available, you can edit all options in a GUI like this
   cmake-gui ./coinOn Windows the Boost root directory need to be explicitly specified as it could not be found otherwise.

3. Build the Coin library
   Open Coin.sln in the build directory from Microsoft Visual Studio. Build the ALL_BUILD project from the Microsoft Visual Studio solution explorer.
   Or, alternatively use the CMake build tool mode. This uses coin_build as build directory, builds the target ALL_BUILD for the Release configuration and passes /nologo /verbosity:minimal /maxcpucount (parallel building with maximum number of cores available) to the underlying default build tool (the default build tool on Windows isMSBuild).
   Or, directly build the Coin library using the default build tool on the platform from the command line.

4. Install the Coin Library
   Build the INSTALL project from the Microsoft Visual Studio solution explorer.
   Or, alternatively again use the CMake build tool mode. This uses coin_build as build directory, builds the target INSTALL for the Release configuration and passes /nologo /verbosity:minimal /maxcpucount (parallel building with maximum number of cores available) to the underlying default build tool (the default build tool on Windows is MSBuild).
   Or, install the Coin library using the default build tool on the platform from the command line.

5. Build NSIS installation packages of the Coin library (optional)
   If something does not work you may need to add the --verbose --debug options to the call to figure out what went wrong or is missing.

6. Finally when you are done remove the build directory
   rmdir /s coin_build

macOS

or

1. Get the sources using Mercurial clone command.

2. Configure the build.
   If you just want a standard installation (or regenerate the Makefiles using cached options).
   You may omit the generator, then the default generator for the platform is used.
   CMake will create the build directory if it does not exist.
   Coin uses an Out-of-source build mode, i.e. you must not run the cmake command directly from the source directory. Instead you need to run it from a separate build directory, e.g. coin_build.
   On recent CMake versions (3.13 and later) the option -H has been superseded by -S.
   Or, if available, you can edit all options in a GUI like this
   cmake-gui ./coin

3. Build the Coin framework using the default build tool on the platform.
   Or, alternatively use the CMake build tool mode. This uses coin_build as build directory, builds the target all for the Release configuration and passes -j4 (parallel building with 4 cores) to the underlying default build tool (the default build tool on Linux is make).

4. Install the Coin framework using the default build tool on the platform.
   Or, alternatively again use the CMake build tool mode. This uses coin_build as build directory, builds the target install for the Release configuration and passes -j4 (parallel building with 4 cores) to the underlying default build tool (the default build tool on Linux is make).
   As you are like to install into system locations you need to prefix your command with sudo.
   By default the name of the Coin framework is Inventor.

5. Build installation packages of the Coin framework (optional)
   This uses CPack a packaging tool from the CMake suite.
   If something does not work you may need to add the --verbose --debug options to the call to figure out what went wrong or is missing.

6. Finally when you are done remove the build directory
   rm -rf coin_build

Probably the most common types are Debug and Release.
The Debug build will append a d to the target library name.

It also offers its own open-source, NTFS-3G, and commercial support with some additional features. The Tuxera NTFS Product Key has got the highest data transfer speeds in NTFS devices with data protection ability also smart caches layer. The Tuxera NTFS License Key designed to give our customers maximum performance when accessing NTFS drives while maintaining data security. Tuxera ntfs for mac mojave crack. Each operating system has its own advantages and a number of absences for its users.

Install path prefix, prepended onto install directories. If set to /tmp then the library will install into /tmp/lib.
When building and installing Coin as framework on macOS (e.g. add -DCOIN_BUILD_MAC_FRAMEWORK=OFF to the cmake call) you should set it to either~/Library/Frameworks, /Library/Frameworks, /System/Library/Frameworks, or /Network/Library/Frameworks

Semicolon separated list of directories specifying installation prefixes to be searched by CMake find_package, find_library, find_.. commands.
When CMake searches for config packages, e.g. for simage with find_package(simage), these directories are searched to find <PackageName>Config.cmake or <packagename>-config.cmake.
This can be used to specify non standard installation places for required package information, e.g. /opt/local/Boost;/opt/local/Qt5 or C:DatalocalBoost;C:DataQt-5.12.0.

Build shared library when ON, static when OFF. Default is ON.

Build HTML documentation on all platforms when ON, as well as man pages onplatforms other than Windows. Default is OFF. The latest version of the documentation can always be found on the Documentation page of the wiki.

Build Coin man pages when ON on platforms other than Windows. Default is OFF.

Build QtHelp documentation when ON (requires Qt installation https://www.qt.io )Default is OFF.

Build compressed HTML help manual on Windows platform when ON (requires Microsoft HTML Help Workshop download). Default is OFF.

Depends on COIN_BUILD_DOCUMENTATION to be ON. When OFF (the default) onlythe documentation regarding the public API will be built, and warnings forundocumented entities are turned on.
When ON the generated documentation will include internal classes, which canbe useful for Coin developers. Since it is less common to fully documentinternal entities, warnings for undocumented entities are turned off.

Build Coin as framework when ON, as library when OFF. Default is OFF.
On macOS, the default behavior is to install Coin as a framework so you can compile/link with it by using the compiler option -framework Inventor.
If you want to make a plain installation into ${CMAKE_INSTALL_PREFIX}/{lib,include} instead, set this option to OFF.

Link Coin to the X11 implementation of GL when ON, to OpenGL framework when OFF. Default is OFF.
You need to have OpenMotif and XQuartz installed.

Build the provided test cases when ON. Default is ON.

Forces the use of versioned paths for includes and documentation when ON, usual behavior otherwise.

Build only one library when ON, multiple when OFF. Default is ON for Windows, OFF for other platforms.

Enable build with multiple processes in Visual Studio. Default is ON.
(Only available when using Visual C++ compiler)

If you placed your Boost installation into a directory that is not known to CMake you may need to specify BOOST ROOT on the CMake command line, e.g. -DBOOST_ROOT=/opt/local/boost-1.56.0 on Linux and -DBOOST_ROOT=C:DataBoost-1.56.0 on Windows.

Building the GUI toolkits is very similar to the Coin build commands.
To build a GUI toolkit different from SoQt simply replace soqt with sowin, soxt or quarter as well as SOQT with SOWIN, SOXT or QUARTER in the build commands.

Linux

Windows

macOS

macOS and X11

To use X11 on macOS you need to provide X11/XQuartz and OpenMotif packages and build Coin with an additional option -DCOIN_BUILD_MAC_X11=ON.

CMake caches the build options and uses these as defaults during subsequent runs.
To clear the cache, delete the file CMakeCache.txt or empty the build directory completely.

If you build both Debug and Release configurations and don't want to make clean and reconfigure each time something changes, use a separate build directory for each type.

If you experience configure/build/install problems beyond what can be resolved by following the instructions in this file and the relevant README files and the FAQ, you can ask for help on the mailing list (subscription is needed for posting), or you can contact us per email for technical support.

Before asking, check that the subject hasn't been discussed and resolved already by looking through the coin-discuss mailing list or at the Coin issue tracker.

If you decide to send us an email about the problem or add an entry to the issue tracker, you should include allthe information that is relevant to the problem together with your description.

This includes the terminal output from CMake for the compilation that fails or at least the entire CMake error message.

A description of the build environment you use may also be helpful, e.g. the compilersuite and versions of libraries and any system customization that maybe relevant to the problem.

Updated

You are here: Home → Documentation

API documentation

The source code has been commented for auto-generation of class hierarchy documentation with Doxygen. The API documentation is available online:

This documentation can be generated for offline reading by anyone who has the Coin3D source code and the Doxygen utility.

Platform specific documentation

Building the libraries from source

On Linux, Unix, and *BSD environments, the recommended way to install Coin3D and SIM Voleon is the CMake build system. The old Autoconf/Automake build system has been deprecated.

Tutorials and HowTos

Tutorials can be found in different subsections of this website. Here you can find a list of all:

Books

Programming with Coin3D should be treated exactly like programming with Open Inventor, so all Open Inventor documentation that exists also applies to Coin3D.
Here is a list of books on programming with Open Inventor.

Updated