[Paraview] Problem with cross-compile

[Sean Ziegeler]

Well, I was following the cross compiling page at:
http://paraview.org/ParaView3/index.php/Cross_compiling_ParaView3_and_VTK

But, in looking over the page you sent, it's pretty much the same thing. 
  I do a native build first, then an MPI build (on Cray it would be the 
Catamount build).  I point the "compile tools" to my native build. 
Unfortunately, the paths to the compile tools don't get set to the 
native build.

Thanks,
Sean

Kent Eschenberg wrote:
> FYI there is some information about cross compiling on the Wiki page 
> "Compiling ParaView3 for Cray supercomputers" at
> 
>   http://www.paraview.org/Wiki/Compiling_ParaView3_for_Cray_supercomputers
> 
> I don't know if there is anything there will help with your issue.
> 
> Kent
> Pittsburgh Supercompuing Center
> 
> Sean Ziegeler wrote:
>> I am cross compiling an MPI version of ParaView3 CVS (updated 
>> yesterday)  for AIX on Power5.  I've successfully built a serial 
>> version, but the cross compile hits a snag in the cmake/make process.  
>> I'm using CMake CVS also updated yesterday.
>>
>> The problem is that CMake (either CMake itself or the PV cmake 
>> scripts) are generating incorrect dependencies for the Compile Tools.  
>> I am setting -DParaView3CompileTools_DIR to my serial build directory, 
>> but the path to the executables (e.g., vtkmkg3states) in the 
>> */build.make files somehow are set to the source directory.
>>
>> Does that sound familiar?  If that isn't enough information, I can 
>> post excerpts of the relevant files.
>>
>> Thanks,
>> Sean
>