Hello David,
On Sun, Oct 12, 2014 at 4:31 AM, David Cole wrote:
> Does your dashboard script call ctest_read_custom_files after
> ctest_configure?
>
> You should do that, as the CMake and VTK (and other) dashboards do:
>
>
> http://www.cmake.org/gitweb?p=cmake.git;a=blob;f=cmake_common.cmake;h=5
Does your dashboard script call ctest_read_custom_files after ctest_configure?
You should do that, as the CMake and VTK (and other) dashboards do:
http://www.cmake.org/gitweb?p=cmake.git;a=blob;f=cmake_common.cmake;h=576db9a98725503b53e0a6e29f4db7682cfaf1a2;hb=182b93635464ee35100522dec811abb76b55
With CPack enabled, "make help" will show all the valid targets. The
"package_source" target should be one of those targets.
A simple project on Linux built with "make package_source" gives me:
${CMAKE_BINARY_DIR}/_CPack_Packages/Linux-Source/{TZ,TGZ,TBZ2}/CPack_Example-0.1.1-Linux.tar.{bz2,gz,Z
Hello,
What is the CMake equivalent for autotools "make dist" ?
By autotools "make dist", I mean a way to wrap all sources and test
files needed to build and test the package and / or to be ready for dev.
I googled this question : I heard about CPack (and "make package"),
but, I am not sure t
Hi all,
Can anyone explain me how to filter out the below warning from dashboard?
warning: #warning "deprecated"
./vcl_deprecated_header.h:10:3: warning: #warning "deprecated" [-Wcpp]
# warning "deprecated"
So far I tried having below in CTestCustom.cmake
set(CTEST_CUSTOM_WARNING_EXCEPTION