[vtkusers] Building VTK on a BlueGene/P

[David E DeMarle]

Refer to:
http://paraview.org/Wiki/ParaView/Users_Guide/Parallel_Rendering
And try:
VTK_USE_COCOAOFFMac only.VTK_USE_XOFFVTK_USE_OFFSCREENON
VTK_OPENGL_HAS_OSMESAONTurn this to ON to enable Off Screen MESA.
OSMESA_INCLUDE_DIR<mesa include dir>Set this to the include directory for
MESA.OPENGL_INCLUDE_DIR<mesa include dir>Set this to the include directory
for MESA. OPENGL_gl_LIBRARY<empty>Set this to empty.OPENGL_glu_LIBRARYlibGLUSet
this to the libGLU.a or libGLU.so file.OSMESA_LIBRARY libOSMesaSet this to
the libOSMesa.a or libOSMesa.so file.

David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909


On Tue, Sep 10, 2013 at 10:07 PM, François Bissey
<fbissey at slingshot.co.nz>wrote:

> Hi again,
>
> I am finding myself stuck at a strange point. I have installed mesa 9.2.0
> (cross compilation was effectively broken from 7.11 till 9.2.0). And I have
> build libosmesa but not libGL. Building libGL seem to require building a
> lot
> of bit of X11 that I don't really want if I can help it.
>
> But vtk is looking for libGL specifically is it really necessary to have
> both libGL and libOSMesa? I haven't found anything that would turn it off.
>
> Francois
>
>
> On 2013-09-06 02:15, David E DeMarle wrote:
>
>> Hello Francois,
>>
>> You best place to learn about cross compilation is chapter 8 of the
>> CMake book (Mastering CMake fifth edition). It explains cross
>> compilation in detail and uses VTK as an example project.
>>
>> The gist of what you are missing is that for a complex project like
>> VTK, in which the build process itself creates and runs compile time
>> executables that generate code and do system introspection, you need
>> to compile twice. The first compile runs on and produces executables
>> that run on the host system. The second compile runs on (using the
>> compile time executables produced in the first pass) the host but
>> produces executables that run on the target system.
>>
>> In your case you are doing the second pass and have not added the
>> location of the first pass into your CMAKE_PREFIX_PATH, so CMake can
>> not find the compile time executables it needs.
>>
>> After that, you will also need to provide the results of the compile
>> time system introspection queries that the host side can not
>> determine. It can't because it has to submit and run those compile
>> time executable on the target system in order to determine the nature
>> of the target system. To do that you provide a TryRunResults file. It
>> turns out not to be too hard to generate that, CMake tells you exactly
>> what to run and what to fill in. But most likely you can just use the
>> one in the ParaView superbuild project (bgp_xlc) or the one in
>> VTK/CMake/TryRunResults-VTK-**bgl-gcc.cmake.
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.vtk.org/pipermail/vtkusers/attachments/20130910/be81392e/attachment.htm>