Trouble Shooting Guide
Here you find answers to soome frequently asked questions. For more, please visit our Questions & Answers page, http://confluence.mercurydpm.org/questions/.
I CREATED A NEW CODE BUT I CANNOT BUILD IT
Sometimes cmake does not detect new codes being created and hence it does not automatically add the new file to the build targets. To fix this problem simply type
I GET TESTS CALLED .SVN THAT FAIL
This is not really a problem at all and only happens if you are using an svn version older that 1.7. If you want to get rig of these failed tests please update your version of svn and type
XBALLS RELATED PROBLEMS (I.E. X11 INSTALLATION WHICH IS ONLY REQUIRED FOR XBALLS)
ON MY MAC IT FINDS X11 BUT XBALLS STILL DOES NOT WORK
This is only a problem if you upgraded your mac from OSX 10.8 to a version after 10.8. This would have required you to install XQuartz to get X11 to work. However, this leaves you will two versions of X11 installed and cmake find the old non working versions by default.
To fix this turn in cmake turn on advance mode click the X11 tab and change all the locations to start /opt/X11 not /local/X11 is will be currently stated.
X11_XRES_INCLUDE_PATH OR X11_XRES_LIB NOT FOUND
You are missing the X11_XRes library; in Ubuntu, you can install them by opening a terminal and type
X11_XRT_INCLUDE_PATH OR X11_XT_LIB NOT FOUND
You are missing the X11_Xt library; in Ubuntu, you can install them by opening a terminal and typing (note, both of these X11 libraries are required)
MANY OF MY SELFTESTS FAIL WHEN I COMPILE ON A MAC:
: The latest update of the Mac compiler suite causes MercuryDPM tests to fail when the optimisation flag -O3 is used. We recommend Mac users to compile in Debug mode (change CMAKE_BUILD_TYPE to Debug in cmake-gui), or switch to the compile flag -O2 in Release mode.
MAKE FULLTEST NOT ALL TESTS PASSING ON WINDOWS 10