[Paraview-developers] wrapping cmake dependency issue?

[Burlen Loring]

correction, I changed 5 cmake vars relating to OpenGL, including the 
include path, which should trigger some classes to re-compile and be 
re-wrapped. Still I don't think this should trigger the entirety of CS 
and Python wrapping.

755 //Path to a file.
  756 
OPENGL_INCLUDE_DIR:PATH=/usr/common/graphics/mesa/10.1.0/llvmpipe/shared/include
  757
  758 //Path to a library.
  759 
OPENGL_gl_LIBRARY:FILEPATH=/usr/common/graphics/mesa/10.1.0/llvmpipe/shared/lib/libOSMesa.so
  760
  764 //Path to a file.
  765 
OPENGL_xmesa_INCLUDE_DIR:PATH=/usr/common/graphics/mesa/10.1.0/llvmpipe/shared/include
  766
  767 //No help, variable specified on the command line.
  768 
OSMESA_INCLUDE_DIR:UNINITIALIZED=/usr/common/graphics/mesa/10.1.0/llvmpipe/shared/include
  769
  770 //No help, variable specified on the command line.
  771 
OSMESA_LIBRARY:UNINITIALIZED=/usr/common/graphics/mesa/10.1.0/llvmpipe/shared/lib/libOSMesa.so
On 02/26/2015 11:01 AM, Burlen Loring wrote:
> Hi All,
>
> This is in regard to what to me seems like a bug in dependency chain 
> of the CS and Python wrapping.  Yesterday I was debugging a segv on 
> 4.3.1 build on our Cray and I had to test a different a different 
> OpenGL build. So I opened up the CMakeCache of my build and changed 
> the one variable- namely the one specifying the OpenGL library. This 
> should have resulted in the executables and a few of the libs 
> re-linking, however in addition all of the CS and Python wrapping was 
> regenerated and those files recompiled and re linked. As a result what 
> should have been a 5min tweak took over an hour! I guess that the 
> wrappers are custom command/targets in CMake and that the dependency 
> is not set correctly. Am I right? I'm happy to file a bug report if 
> this something that you'd be willing to fix. ;-)
>
> Burlen