Look at symbol resolution for conflicting libraries

[Richard Roberts]

When MATLAB has built-in libraries, even when we reference libraries with absolute paths, somehow versions in MATLAB get called. Perhaps this is related to this: http://stackoverflow.com/questions/6538501/linking-two-shared-libraries-with-some-of-the-same-symbols

e.g. moving matlab's libtbb out of the way resolves an error on mac.

[Richard Roberts]

Putting a check in cmake for conflicting libraries, but still need to verify the built-in library paths on linux

[Richard Roberts]

@fdellaert did the link error you got with TBB happen when trying to run a GTSAM command in MATLAB, after successfully compiling the wrapper? If so, it's due to a conflict with built-in matlab libs. I put a check in cmake for this that prints a warning telling you which files are conflicting and which directory to move them out of. If you have this error again, update the code and take a look whether you get this cmake message, and if so, follow the instructions it gives (or let me know if the instructions are unclear).