Problem with installation on macOS

Hello team,
I was trying to install the Collision Checker on my laptop but I ran into a problem with “Full Installation with Anaconda”.

I’ve installed all the third party library according to the instructions of manual, but when I ran the command ‘cmake -DADD_PYTHON_BINDINGS=TRUE -DPATH_TO_PYTHON_ENVIRONMENT="/path/to/your/anaconda3/envs/commonroad-py36" -DPYTHON_VERSION=“3.6” -DCMAKE_BUILD_TYPE=Release …’, it could not find the fcl library and printed “Could NOT find required library libfcl”. I then tried to install fcl again from GitHub repo and from Homebrew but the error didn’t change.

I can’t figure out what the cause is. Thank you very much for your answers!

Hi,
According to your description, it seems that you did not substitute “/path/to/your/anaconda3/envs/commonroad-py36” with your own path to anaconda environment.

Sorry for the confusion, but I did substitute the path as “/Users/xichen/anaconda3/envs/commonroad-py36”.

It seems like a compiler issue. What compiler are using? Are you using the latest version of that compiler?

Sometimes it also helps to delete all files from your build folder after an error occurred.
And in your post your cmake command ends with “…” instead of “…”.

If that doesn’t help you could paste all commands which you used to install libccd, fcl and the collision checker.

Hi, I’ve tried to clean the build folder and reran the cmake command, but it doesn’t work, unfortunately.

The command I ran and output are as follows:

(commonroad-py36) Xis-MacBook-Pro:build xichen$ cmake -DADD_PYTHON_BINDINGS=TRUE -DPATH_TO_PYTHON_ENVIRONMENT="/Users/xichen/anaconda3/envs/commonroad-py36" -DPYTHON_VERSION="3.6" -DCMAKE_BUILD_TYPE=Release ..
-- The C compiler identification is AppleClang 11.0.0.11000033
-- The CXX compiler identification is AppleClang 11.0.0.11000033
-- Check for working C compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/cc
-- Check for working C compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/c++
-- Check for working CXX compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
--
-- Found PythonInterp: /Users/xichen/anaconda3/envs/commonroad-py36/bin/python3.6m (found version "3.6.9")
-- Found PythonLibs: /Users/xichen/anaconda3/envs/commonroad-py36/lib/libpython3.6m.so
-- Performing Test HAS_CPP14_FLAG
-- Performing Test HAS_CPP14_FLAG - Success
-- pybind11 v2.2.4
-- Performing Test HAS_FLTO
-- Performing Test HAS_FLTO - Success
-- LTO enabled
-- Found PkgConfig: /usr/local/bin/pkg-config (found version "0.29.2")
-- Checking for module 'fcl>=0.3.1'
--   Found fcl, version 0.6.0
-- Found FCL: fcl;ccd;m;octomap;octomath
-- Checking for module 'ccd>=2.0'
--   Found ccd, version 2.0
-- Found CCD: ccd;m
CMake Error at cpp/CMakeLists.txt:64 (message):
  Could NOT find required library libfcl


-- Configuring incomplete, errors occurred!
See also "/Users/xichen/Downloads/commonroad-collision-checker/build/CMakeFiles/CMakeOutput.log".

Here is the generated CMakeCache.txt in /build.

I think there is something wrong with my compiler on Mojave 10.14.6, after I switched to Ubuntu there are no problems anymore. Thanks for your help.

It could also be because of activated anaconda, we saw a similar problem on some MacOSX versions. One possible solution could be to build the collision checker outside of anaconda, with no anaconda activated for the current shell.
On the many versions of MacOSX we tested on, the build was successful. But all *nix distributions are different, some come without a configured compiler.

For example, using sh shell for which no anaconda is active,
sh
cmake … (two dots)

The easiest workaround could be to specify the path manually:

cmake -Dfcl_DIR=/path/to/fcl -Dccd_DIR=/path/to/ccd