Note that using OGDF-release causes a crash - the ‘this’ pointer becomes NULL, which indicates a possible stack corruption: note that this happens on the thread-based scanner rather than the non-thread-based one, so it might be due to a short stack. Disabling the OGDF code completely does not fix the problem and neither does moving the OGDF objects off the stack. It is likely that the OGDF-release library provides an entry point that conflicts with something critical, which the OGDF-debug does not, or that the linker gets confused. Note also that moving the OGDF library to the end of the link order has no effect. Note that there is a different flag for the debug library, OGDF_DEBUG, and it results in different object layouts!!!!
But changing the OGDF builds to use the same value for OGDF_DEBUG, and the projects as well, doesn't fix the problem, so executables will be linked with libOGDFDebug.a only.