Hello,
I have a strange error. The issue is not very important, just a nice
to have.
I have a simple project building paraview-superbuild as external
project which includes applying two simple patches
(add building of the libs boost_filesystem and hdf5_cpp) and our
external plugin.
When run the project manually (cmake ..) it works reproducible
perfectly smooth on several Linux machines and Mac.
When I run the project via ctest for a nightly build I have errors
building qt5. When I do 'make' in my project or
the paraview-superbuild project all runs without any notice of a
error, simply in install/bin no paraview stuff built.
I diffed Testing/Temporary/LastBuild_20170118-1244.log with the output
from my manual build.
All is more or less the same but sometimes differently ordered due to
parallal building (which I don't trigger actively)
The real difference start in the ctest log in line ~36500
with
-----------------------------
[ 88%] Performing install step for 'qt5'
In file included from
/home/fwein/code/cfs_paraview_build/build/superbuild/qt5/src/qtbase/src/corelib/tools/qlocale_tools.cpp:42:0:
/home/fwein/code/cfs_paraview_build/build/superbuild/qt5/src/qtbase/src/corelib/tools/qdoublescanprint_p.h:151:53:
fatal error: double-conversion/double-conversion.h: No such file or
directory
# include <double-conversion/double-conversion.h>
^
compilation terminated.
g++: error: .obj/qlocale_tools.o: No such file or directory
mv: cannot stat 'libQt5Core.so.5.7.1': No such file or directory
install: cannot stat '../../lib/libQt5Core.so.5.7.1': No such file or
directory
strip:
'/home/fwein/code/cfs_paraview_build/build/install/lib/libQt5Core.so.5.7.1':
No such file
/home/fwein/code/cfs_paraview_build/build/superbuild/qt5/src/qtbase/src/network/kernel/qnetworkproxy_libproxy.cpp:47:19:
fatal error: proxy.h: No such file or directory
#include <proxy.h>
^
compilation terminated.
g++: error: .obj/qnetworkproxy_libproxy.o: No such file or directory
mv: cannot stat 'libQt5Network.so.5.7.1': No such file or directory
...
----------------------------------------
In the manual built it is
----------------------------------------
[ 88%] Performing install step for 'qt5'
strip:/home/fwein/code/cfs_paraview_build/build/install/bin/fixqt4headers.pl:
File format not recognized
strip:/home/fwein/code/cfs_paraview_build/build/install/bin/syncqt.pl:
File format not recognized
Some of the required modules
(android|ios|winrt|osx_webview_experimental|qtHaveModule(webengine))
are not available.
Skipped.
[ 90%] Completed 'qt5'
[ 90%] Built target qt5
Scanning dependencies of target paraview
[ 90%] Creating directories for 'paraview'
[ 91%] Performing download step (download, verify and extract) for
'paraview'
-- verifying file...
...
------------------------------------------
I cannot see how this is caused by my ctest script
---------------------------------------------
SET(CTEST_SOURCE_DIRECTORY "$ENV{HOME}/code/cfs_paraview")
SET(CTEST_BINARY_DIRECTORY "$ENV{HOME}/code/cfs_paraview_build")
SET(CTEST_CMAKE_GENERATOR "Unix Makefiles")
SET(CTEST_PROJECT_NAME "Paraview metabuild")
set(CTEST_SITE "eamc061")
set(CTEST_BUILD_NAME "Paraview 5.2 metabuild")
set(BUILDNAME "Paraview 5.2 metabuild Buildname what for?")
# somehow CTEST_START_WITH_EMPTY_BINARY_DIRECTORY does not work?! So
do it also manually
file(REMOVE_RECURSE "${CTEST_BINARY_DIRECTORY}")
file(MAKE_DIRECTORY "${CTEST_BINARY_DIRECTORY}")
SET(CTEST_START_WITH_EMPTY_BINARY_DIRECTORY TRUE)
SET(BUILDTYPE "RELEASE")
message("Start dashboard...")
ctest_start(Experimental)
message(" Update")
find_program(CTEST_SVN_COMMAND NAMES svn)
set(CTEST_UPDATE_COMMAND "${CTEST_SVN_COMMAND}")
ctest_update(SOURCE "${CTEST_SOURCE_DIRECTORY}" RETURN_VALUE res)
message(" Configure")
ctest_configure(BUILD "${CTEST_BINARY_DIRECTORY}" RETURN_VALUE res)
message(" Build")
ctest_build(BUILD "${CTEST_BINARY_DIRECTORY}" RETURN_VALUE res)
message(" Test")
ctest_test(BUILD "${CTEST_BINARY_DIRECTORY}/build" RETURN_VALUE res)
message(" Submit")
-------------------------------------------------------------
The CMakeCache.txt in my build directory and the paraview-superbuild
build directory are identical
Anyone has any idea? I can live without nightly builds but it would be
nice for me to understand.
Fabian
_______________________________________________
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
Search the list archives at: http://markmail.org/search/?q=ParaView
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview
