ftgl | fork from http : //sourceforge.net/projects/ftgl | 3D Animation library

Platforms generally have a common C ABI that dictate symbol naming, function calling conventions, and other low-level details. Compilers that target that ABI can interoperate with other compilers that do the same. Linux libraries and Windows libraries are incompatible, but it is usually possible to build a small handful of versions for each targeted platform: one for Linux, one for Windows, etc.

There's no such standard for C++ libraries. Name mangling varies from compiler to compiler. Compiled C++ libraries can typically only be used by the same compiler at the same version. Libraries compiled by different versions of the same compiler aren't even necessarily compatible. To pre-build a library you'd have to build with dozens of versions of g++, dozens of versions of clang, etc... It's not practical.

Distributing C++ libraries is difficult. Some common strategies are:

1. Make the library header-only so end users just #include library headers. No compilation required.

2. Distribute header and source files and require the end user to build the library.

3. Implement the library in C and provide C++ wrappers in header files. The library can be used by both C and C++ programs. The C portion can be pre-built if so desired.

4. Inverse of the previous bullet, implement the library in C++ and add C wrappers. The wrappers would define a bunch of freestanding extern "C" functions that call into the C++ code.

Boost, for example, uses a mix of strategies 1 and 2. If you only use the parts of Boost that are header-only then all you have to do is #include their headers in your program, super easy. If you use non-header-only pieces such as the threading or regex components then you have to compile them, which takes a while.

3 and 4 are useful for proprietary libraries where you don't want to distribute the code.

The package in EPEL. To enable it and install on Amazon Linux 2:

Those dependencies are not included in the package set of stackage (you can check it in https://www.stackage.org/lts-13.0). However, they are in the hackage repository (f.e. http://hackage.haskell.org/packages/search?terms=GLUtil) and you can make stack using them adding a extra-deps section in the stack.yaml config file:

My project is built with CMake, I finally fixed this issue by appending a -g in CMakeFiles.txt

Originally there is a

set (CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} ${ADDITIONAL_CFLAGS}")

this will build the project without extra info for debugging, after change it into

set (CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} ${ADDITIONAL_CFLAGS} -g")

the debugging will be allowed with extra info provided during building (the building process will be much slower than default as well).

You appear to have the compiler define __STRICT_ANSI__ set. Normally rgl doesn't set that. The latest version of rgl on R-forge (0.98.13) has this fixed in the platform.cpp file where you saw the error, but there may be other places where problems arise.

You can get the latest version on R-forge. It is not available on CRAN (or MRAN).