[Paraview] ParaView Superbuild - changing default Paraciew cmake option
Su, Simon M CTR USARMY ARL (US)
simon.m.su.ctr at mail.mil
Wed Oct 29 13:25:00 EDT 2014
Hi Utkarsh,
unfortunately I am still not able to pass both argument into ParaView superbuild cmake line using the -DPV_EXTRA_CMAKE_ARGS option that Ben suggested. Any help on this is much appreciated
thanks
-simon
________________________________________
From: Utkarsh Ayachit [utkarsh.ayachit at kitware.com]
Sent: Wednesday, October 29, 2014 12:20 PM
To: Su, Simon M CTR USARMY ARL (US)
Cc: ben.boeckel at kitware.com; paraview at paraview.org
Subject: Re: [Paraview] ParaView Superbuild - changing default Paraciew cmake option
Simon,
I am joining a little late to this conversation -- is this addressed yet?
Utkarsh
On Mon, Oct 20, 2014 at 11:57 AM, Su, Simon M CTR USARMY ARL (US)
<simon.m.su.ctr at mail.mil> wrote:
> Ben,
>
> Unfortunately, when I checked the CMakeCache.txt in the directory paraview/src/paraview-build after the cmake ran, I am still finding
>
> //Request building vtkIOXdmf3
> Module_vtkIOXdmf3:BOOL=OFF
>
> and Boost_NO_BOOST_CMAKE is none existence in the CMakeCache.txt
>
> I even tried both
> -DPV_EXTRA_CMAKE_ARGS:STRING="-DModule_vtkIOXdmf3:BOOL=ON -DBoost_NO_BOOST_CMAKE:BOOL=ON"
> and
> -DPV_EXTRA_CMAKE_ARGS:STRING="Module_vtkIOXdmf3:BOOL=ON Boost_NO_BOOST_CMAKE:BOOL=ON"
>
> thoughts?
>
> thanks
> -simon
>
> ________________________________________
> From: Ben Boeckel [ben.boeckel at kitware.com]
> Sent: Monday, October 20, 2014 11:43 AM
> To: Su, Simon M CTR USARMY ARL (US)
> Cc: paraview at paraview.org
> Subject: Re: [Paraview] ParaView Superbuild - changing default Paraciew cmake option
>
> On Mon, Oct 20, 2014 at 15:15:59 +0000, Su, Simon M CTR USARMY ARL (US) wrote:
>> I ran cmake with
>>
>> -DPV_EXTRA_CMAKE_ARGS:STRING="-DModule_vtkIOXdmf3:BOOL=ON -DBoost_NO_BOOST_CMAKE:BOOL=ON"
>>
>> and check it with ccmake. Looks like -DModule_vtkIOXdmf3:BOOL=ON
>> -DBoost_NO_BOOST_CMAKE:BOOL=ON made it into the variable
>> PV_EXTRA_CMAKE_ARGS
>>
>> It appears :STRING does the trick.
>
> Yep. This is a CMake parsing bug; the regular expression for this is too
> greedy (it allows '=' in the variable name). Compare:
>
>> -DPV_EXTRA_CMAKE_ARGS=-DModule_vtkIOXdmf3:BOOL=ON -DBoost_NO_BOOST_CMAKE:BOOL=ON
> |-------------------------------------| |--| |-------------------------------|
> variable type value
>
> versus:
>
>> -DPV_EXTRA_CMAKE_ARGS:STRING=-DModule_vtkIOXdmf3:BOOL=ON -DBoost_NO_BOOST_CMAKE:BOOL=ON
> |-----------------| |----| |--------------------------------------------------------|
> variable type value
>
> this works:
>
>> -DSOME_PATH=C:/path/to/file
> |-------| |-------------|
> variable value
>
> because paths with '=' are very rare:
>
>> -DSOME_PATH=C:/path/to/file/with/=/sign
> |---------| |-----------------| |---|
> variable type value
>
> --Ben
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
More information about the ParaView
mailing list