Polygon Crucher SDK - Documentation
Documentation
Loading...
Searching...
No Matches
Compilation under Linux

Compilation environment

SDK is compiled with gcc (4.8.5 20150623) under Centos Linux 7 (kernel 3.10.0-514.el7.x86_64)

The SDK is provided as static library

The demo version of the SDK only contains the debug version.
As a result it is really much slower thant the release but allows to perform all implementation to make a POC.

Preprocessor directives

The code is encapsulated in mootools namespace. You may use USE_MOOTOOLS_NAMESPACE is you want to use that namespace automatically.

Otherwise mootools:: must be placed before any SDK name (ie mootools::C3DIo)

Link settings with or without file format support

If you don't need I/O support you may link with libPolygonCruncherSDKWithoutIO.a. In this case you'll get only Wavefront format support.

Common link settings

Your project must be compiled and link with -pthread -fopenmp settings.

Link with I/O support

Support of 3D formats is done through the static library libPolygonCruncherSDKIO.a.
If you need to have 3D I/O file support, you must link this library with your software.
This library involves several dependencies as it makes references to other libraries.
You must add these libraries to your link command (-l)
These libraries are included in the the linux Bin folder of the SDK.

Take care to have the path to the appropriate directory correctly configured in your link command (-L)

If one of these libraries is missing, you may add the package using yum. For example:

The class defines an x, y, z 3D point which can use int, float or double.
Definition 3DPoint.h:27

Link without I/O support

Minimal format support is done using the libPolygonCruncherSDKWithoutIO.a. Therefore, using that library includes wavefront and SDK 3D file format support.
You must add these libraries to your link command (-l)
This library is included in the the linux Bin folder of the SDK.
Take care to have the path to the appropriate directory correctly configured in your link command (-L)

Includes and namespace

The code is encapsulated in mootools namespace. You may use USE_MOOTOOLS_NAMESPACE is you want to use that namespace automatically.

Otherwise mootools:: must be placed before any SDK name (ie mootools::C3DIo)