Fails to build / run the example

[henrikmidtiby]

I would like to experiment with your ChromaTags and have thus tried to run your code.
I have followed your guide in the readme and is now stuck on this error related to the lcm library.

git clone https://github.com/CogChameleon/ChromaTag.git
cd ChromaTag
mkdir build
cd build
cmake -DCMAKE_BUILD_TYPE=Release ..

The cmake command shows this message

ChromaTag :: Looking for Library lcm: Miss

It seems to be an optional library, so I continue to run make

make -j

Which throws the error

/home/henrik/localbuild/ChromaTag/Run_JMD_ChromaTag_Detector.cpp:62:27: fatal error: lcm/lcm-cpp.hpp: No such file or directory
compilation terminated.
CMakeFiles/Run_ChromaTag_Detector.dir/build.make:62: recipe for target 
'CMakeFiles/Run_ChromaTag_Detector.dir/Run_JMD_ChromaTag_Detector.cpp.o' failed
make[2]: *** [CMakeFiles/Run_ChromaTag_Detector.dir/Run_JMD_ChromaTag_Detector.cpp.o] Error 1
CMakeFiles/Makefile2:79: recipe for target 'CMakeFiles/Run_ChromaTag_Detector.dir/all' failed
make[1]: *** [CMakeFiles/Run_ChromaTag_Detector.dir/all] Error 2
Makefile:83: recipe for target 'all' failed
make: *** [all] Error 2

My operating system is Ubuntu 16.04.

[Ojaswi]

Hi,

I faced the same issue and it was resolved after installing liblcm.

Run the following commands:

git clone https://github.com/lcm-proj/lcm.git
cd lcm
mkdir build
cd build
cmake ..
make -j4
sudo make install

Now liblcm has been installed. In the Chromatag source folder, remove the build folder and create again. Before you run cmake, make sure that your path variable points to /usr/local/lib where liblcm.so is kept.

All this worked for me on Ubuntu 16.04, but on 17.10 I couldn't get the program to run, it gave a index out of bounds error.

[Merwanski]

Hi

I am getting the following error when I try to run one of the examples

bash Run_ChromaTag.sh
../build/bin/Run_ChromaTag_Detector: error while loading shared libraries: liblcm.so.1: cannot open shared object file: No such file or directory

any idea how I can solve this issue?
Do you have a python wrapper around your package?

Thank you
Merwan