[vtk-developers] VTK CVS broken: vtkInformationExecutivePortVectorKey and vtkExecutive link error in Debug only

[Sean McBride]

On 10/18/07 11:38 AM, David C Thompson said:

>> Oddly, I do not see this problem on any dashboard.  But we have reproed
>> this on two machine, with fresh checkouts and fresh builds.
>I certainly never saw it before I committed the move but perhaps I
>didn't build static libraries? Could all of this be caused by
>vtkSetObjectMacro() calling GetClassName() inside a vtkDebugMacro()?
>With VTK_DEBUG_LEAKS turned on, does the vtkExecutive::Register() call
>(also in vtkSetObjectMacro) also ask for the class name of the
>vtkExecutive object? If so, it might be more difficult.

Normally, I do build both as static libs and with VTK_DEBUG_LEAKS.  As a
test, I tried also as shared libs, and without VTK_DEBUG_LEAKS, and
without VTK_LEGACY_REMOVE, but I still get the same link error.

-- 
____________________________________________________________
Sean McBride, B. Eng                 sean at rogue-research.com
Rogue Research                        www.rogue-research.com 
Mac Software Developer              Montréal, Québec, Canada