Sven,
Attached is a patch that may resolve this issue. Can you give it a try?
Thanks
Utkarsh
On Tue, Apr 20, 2010 at 7:49 AM, Sven Buijssen
<[email protected]> wrote:
> Hi Paul,
>
>> Sven Buijssen wrote:
>>> (off the list for the moment while discussing some technical details)
>>>
>> [taking back to the list]
>>> I managed to compile PV 3.8 RC1
>>> (http://www.paraview.org/files/v3.8/ParaView-3.8.0-RC1.tar.gz) on a
>>> 32bit openSuSE 11.1 system, with any of cmake 2.6.4, 2.8.0 and 2.8.1.
>>> Here's my recipe:
>>>
>>> [...]
>>>
>>> % make -j 16
>>>
>>
>> Ouch, just for fun I tried to use make -j 2 instead of a single process
>> make and the problem went away, i.e. the compile succeeded. That's not
>> very good...
>> Out of interest, do you always build multi-process? I'm on a dual-core
>> machine and when building in the background make -j N isn't very
>> attractive.
>
> Yes, I usually build with N > 1.
> I just tested your hypothesis and I can confirm that (for a clean build)
> it does make a difference whether one compiles with 1 or more processes.
> The error > make[2]: *** No rule to make target
> `Applications/ParaView/../../Documentation/paraview.qch', needed by
> `Applications/ParaView/qrc_paraview_help.cxx'. Stop.
> does only occur when compiling sequentially (on 32 bit Linux). Funny to
> see that on my 3 different 64 bit Linux operating systems compilation
> always fails at this point, even with N > 1.
>
> Sven
> _______________________________________________
> 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://www.paraview.org/mailman/listinfo/paraview
>
diff --git a/Applications/ParaView/CMakeLists.txt b/Applications/ParaView/CMakeLists.txt
index ebba87b..6fab9fe 100644
--- a/Applications/ParaView/CMakeLists.txt
+++ b/Applications/ParaView/CMakeLists.txt
@@ -76,7 +76,7 @@ set (plugins_ini "${plugins_ini}</Plugins>\n")
FILE(WRITE "${EXECUTABLE_OUTPUT_PATH}/.plugins" "${plugins_ini}")
# This ensure that the paraview.qch file is generated.
-ADD_DEPENDENCIES(paraview
+ADD_DEPENDENCIES(${paraview_client_real_exe_name}
ParaViewOnlineHelp)
IF (BUILD_TESTING)
diff --git a/CMake/ParaViewBranding.cmake b/CMake/ParaViewBranding.cmake
index 451c9f0..de32f3c 100644
--- a/CMake/ParaViewBranding.cmake
+++ b/CMake/ParaViewBranding.cmake
@@ -301,4 +301,9 @@ FUNCTION(build_paraview_client BPC_NAME)
SET_TARGET_PROPERTIES(${pv_exe_name} PROPERTIES
MACOSX_BUNDLE_BUNDLE_NAME "${BPC_APPLICATION_NAME}")
ENDIF (APPLE)
+
+ # HACK. When employing shared forwarding, I need to expose the real target so
+ # that dependencies can be added correctly. This will go away once we remove
+ # VTK_USE_RPATH option all together.
+ set (paraview_client_real_exe_name ${pv_exe_name} PARENT_SCOPE)
ENDFUNCTION(build_paraview_client)
_______________________________________________
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://www.paraview.org/mailman/listinfo/paraview
