[cmake-developers] Python bindings for CTest
Hi, I have created some Python bindings for CTest. The goal was to create an easy way for Python projects that I work with to be able to wrap their Python compilation log (if there was one), dynamically generate CTests and/or wrap their existing testing commands, do any additional testing analysis (in Python), etc. and then submit the logs, notes, plots, etc. to CDash without requiring them to overhaul any of their existing build or testing systems. Is there any interest in this development? Jonathan -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake-developers
Re: [CMake] CopyOfCMakeCache.txt
Hi Frank, What version of CMake are you running (cmake --version) and what is are you running on? Is this on the Windows Subsystem for Linux? Older CMake versions had similar trouble there that was resolved with more recent releases. - Chuck On Thu, Oct 18, 2018, 17:04 Jean-Christophe Fillion-Robin wrote: > Hi Frank, > > Out of curiosity, did you explicitly pass CMAKE_SYSTEM_NAME variable when > configuring your project ? > > Jc > > On Wed, Oct 17, 2018 at 6:38 PM Frank Tocci wrote: > >> Hello, >> >> I was using the CMake GUI when I came across the following message: >> >> System is unknown to cmake, create: >> Platform/Ubuntu to use this system, please send your config file to >> cm...@www.cmake.org so it can be added to cmake >> >> Your CMakeCache.txt file was copied to CopyOfCMakeCache.txt. Please send >> that file to cm...@www.cmake.org. >> >> Performing Test HAVE_POLL_FINE >> >> System is unknown to cmake, create: >> Platform/Ubuntu to use this system, please send your config file to >> cm...@www.cmake.org so it can be added to cmake >> >> Performing Test HAVE_POLL_FINE - Failed >> >> Configuring done >> >> Generating done >> >> >> CopyOfCMakeCache.txt is attached. >> >> >> Thank you, >> >> Frank >> -- >> >> Powered by www.kitware.com >> >> Please keep messages on-topic and check the CMake FAQ at: >> http://www.cmake.org/Wiki/CMake_FAQ >> >> Kitware offers various services to support the CMake community. For more >> information on each offering, please visit: >> >> CMake Support: http://cmake.org/cmake/help/support.html >> CMake Consulting: http://cmake.org/cmake/help/consulting.html >> CMake Training Courses: http://cmake.org/cmake/help/training.html >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Follow this link to subscribe/unsubscribe: >> https://cmake.org/mailman/listinfo/cmake >> > -- > > Powered by www.kitware.com > > Please keep messages on-topic and check the CMake FAQ at: > http://www.cmake.org/Wiki/CMake_FAQ > > Kitware offers various services to support the CMake community. For more > information on each offering, please visit: > > CMake Support: http://cmake.org/cmake/help/support.html > CMake Consulting: http://cmake.org/cmake/help/consulting.html > CMake Training Courses: http://cmake.org/cmake/help/training.html > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Follow this link to subscribe/unsubscribe: > https://cmake.org/mailman/listinfo/cmake > -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake
Re: [CMake] CopyOfCMakeCache.txt
Hi Frank, Out of curiosity, did you explicitly pass CMAKE_SYSTEM_NAME variable when configuring your project ? Jc On Wed, Oct 17, 2018 at 6:38 PM Frank Tocci wrote: > Hello, > > I was using the CMake GUI when I came across the following message: > > System is unknown to cmake, create: > Platform/Ubuntu to use this system, please send your config file to > cm...@www.cmake.org so it can be added to cmake > > Your CMakeCache.txt file was copied to CopyOfCMakeCache.txt. Please send > that file to cm...@www.cmake.org. > > Performing Test HAVE_POLL_FINE > > System is unknown to cmake, create: > Platform/Ubuntu to use this system, please send your config file to > cm...@www.cmake.org so it can be added to cmake > > Performing Test HAVE_POLL_FINE - Failed > > Configuring done > > Generating done > > > CopyOfCMakeCache.txt is attached. > > > Thank you, > > Frank > -- > > Powered by www.kitware.com > > Please keep messages on-topic and check the CMake FAQ at: > http://www.cmake.org/Wiki/CMake_FAQ > > Kitware offers various services to support the CMake community. For more > information on each offering, please visit: > > CMake Support: http://cmake.org/cmake/help/support.html > CMake Consulting: http://cmake.org/cmake/help/consulting.html > CMake Training Courses: http://cmake.org/cmake/help/training.html > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Follow this link to subscribe/unsubscribe: > https://cmake.org/mailman/listinfo/cmake > -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake
Re: [CMake] ctest_submit CDASH_UPLOAD causes "Not a valid project" error on a valid project
Discussion continues here: https://github.com/Kitware/CDash/issues/736 -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake
[CMake] Cross-compilation, CMake and Symlinks
So I'm using this guide to cross-compile OpenCV for Raspberry Pi: https://visualgdb.com/tutorials/raspberry/opencv/build/ I'm doing that mainly because building anything on RPi is much slower than on Windows, and because I need the remote debugging tools of Visual Studio. Everything worked as expected especially with the advanced CMake subsystem of VisualGDB. However, when I reached the deployment step I faced some annoyances. First, SmarTTY could not upload to the /usr directory because there is no way to apply the sudo command in the application. I could copy everything to the /home/pi directory and then I copied everything recursively to /usr, which worked like a charm! I got remote debugging working and compiled applications picked up all the required dependencies. I don't know if there is an alternative to manually copying the files though. The second annoyance was when I did used the ldconfig command: pi@raspberrypi:~ $ sudo ldconfig ldconfig: /usr/lib/libopencv_calib3d.so.4.0 is not a symbolic link . pi@raspberrypi:/usr/lib $ ls libopencv_calib3d.* -al -rwxr-xr-x 1 root root 9832912 Oct 17 18:16 libopencv_calib3d.so -rwxr-xr-x 1 root root 9832912 Oct 17 18:17 libopencv_calib3d.so.4.0 -rwxr-xr-x 1 root root 9832912 Oct 17 18:16 libopencv_calib3d.so.4.0.0 As you can see, instead of creating one .so file and several symbolic links, it creates multiple copies of the same file. This is basically because Windows does not support symlinks. Now there are several adhoc solutions, like scripts that convert duplicate files to symlinks but this doesn't really look like a reliable approach. How do you solve this kind of problem in your day to day cross-compilation tasks? -- Sent from: http://cmake.3232098.n2.nabble.com/ -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake
Re: [cmake-developers] Generalized verbose option for cmake --build.
Am Donnerstag, 18. Oktober 2018, 17:48:28 CEST schrieb Ray Donnelly: > Hi CMake developers, > > Why do I need to know the necessary verbose flag to make each back-end > that cmake --build calls emit more information? If forces my build > script to switch on the platform in a really ugly way for something > I'd consider a very important feature (you already hardcode various > things to enable cmake --build to work, so why not this as well?) > Something like cmake --build --verbose would be good. I had the same problem with our automated builds, and I solved this by simply passing -D CMAKE_VERBOSE_MAKEFILE=On to the CMake run. Eike signature.asc Description: This is a digitally signed message part. -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake-developers
Re: [cmake-developers] Generalized verbose option for cmake --build.
On 10/18/2018 11:48 AM, Ray Donnelly wrote: > Why do I need to know the necessary verbose flag to make each back-end > that cmake --build calls emit more information? If forces my build > script to switch on the platform in a really ugly way for something > I'd consider a very important feature (you already hardcode various > things to enable cmake --build to work, so why not this as well?) > Something like cmake --build --verbose would be good. There is work on that here: https://gitlab.kitware.com/cmake/cmake/merge_requests/2129 but it has stalled. -Brad -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake-developers
[cmake-developers] Generalized verbose option for cmake --build.
Hi CMake developers, Why do I need to know the necessary verbose flag to make each back-end that cmake --build calls emit more information? If forces my build script to switch on the platform in a really ugly way for something I'd consider a very important feature (you already hardcode various things to enable cmake --build to work, so why not this as well?) Something like cmake --build --verbose would be good. Best regards, Ray. -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake-developers
[Cmake-commits] CMake branch, release, updated. v3.13.0-rc1-26-g09daee0
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, release has been updated via 09daee07806a75e98afa2a80472de7909c961476 (commit) via 3aa258db0e90cf242852a5f62e4a44953b3f74b1 (commit) via c9493939ea4d294ffdb3cfce680f7da9be018db5 (commit) from 2646fd8e03869e2254514f43b0c2a07d89c26076 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log - --- Summary of changes: Auxiliary/vim/extract-upper-case.pl | 25 +- Auxiliary/vim/syntax/cmake.vim | 2229 +-- 2 files changed, 2148 insertions(+), 106 deletions(-) hooks/post-receive -- CMake ___ Cmake-commits mailing list Cmake-commits@cmake.org https://cmake.org/mailman/listinfo/cmake-commits
[Cmake-commits] CMake branch, master, updated. v3.13.0-rc1-147-g1771ec8
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via 1771ec85b6475c10566026ad7813eb74f732d507 (commit) via 071588414ae0bf197af7bc8fc27884b39e98a324 (commit) via 09daee07806a75e98afa2a80472de7909c961476 (commit) via 3aa258db0e90cf242852a5f62e4a44953b3f74b1 (commit) via c9493939ea4d294ffdb3cfce680f7da9be018db5 (commit) from cb5015fb9f91a062fc1c92b698833ee84a71ea50 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log - https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=1771ec85b6475c10566026ad7813eb74f732d507 commit 1771ec85b6475c10566026ad7813eb74f732d507 Merge: 0715884 09daee0 Author: Brad King AuthorDate: Thu Oct 18 07:58:05 2018 -0400 Commit: Brad King CommitDate: Thu Oct 18 07:58:05 2018 -0400 Merge branch 'release-3.13' https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=071588414ae0bf197af7bc8fc27884b39e98a324 commit 071588414ae0bf197af7bc8fc27884b39e98a324 Merge: cb5015f 3aa258d Author: Brad King AuthorDate: Thu Oct 18 11:56:25 2018 + Commit: Kitware Robot CommitDate: Thu Oct 18 07:56:30 2018 -0400 Merge topic 'update-vim-syntax' 3aa258db0e Merge branch 'upstream-vim-cmake-syntax' into update-vim-syntax c9493939ea vim-cmake-syntax 2018-10-18 (64ff4bd7) Acked-by: Kitware Robot Merge-request: !2500 --- Summary of changes: Auxiliary/vim/extract-upper-case.pl | 25 +- Auxiliary/vim/syntax/cmake.vim | 2229 +-- 2 files changed, 2148 insertions(+), 106 deletions(-) hooks/post-receive -- CMake ___ Cmake-commits mailing list Cmake-commits@cmake.org https://cmake.org/mailman/listinfo/cmake-commits
[Cmake-commits] CMake branch, master, updated. v3.13.0-rc1-142-gcb5015f
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via cb5015fb9f91a062fc1c92b698833ee84a71ea50 (commit) via 2646fd8e03869e2254514f43b0c2a07d89c26076 (commit) via fc675057e4b2135e8381e7ae45801e64c4767e75 (commit) via 56c85d9429b1374bd5072763201ecb1e02598745 (commit) via 1d5c8b81db1cbba79927cc251421b2786ce02866 (commit) from 5b47557c82c24e916c7926d210c9b72ad39c9d2e (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log - https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=cb5015fb9f91a062fc1c92b698833ee84a71ea50 commit cb5015fb9f91a062fc1c92b698833ee84a71ea50 Merge: 56c85d9 2646fd8 Author: Brad King AuthorDate: Thu Oct 18 07:39:32 2018 -0400 Commit: Brad King CommitDate: Thu Oct 18 07:39:32 2018 -0400 Merge branch 'release-3.13' https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=56c85d9429b1374bd5072763201ecb1e02598745 commit 56c85d9429b1374bd5072763201ecb1e02598745 Merge: 5b47557 1d5c8b8 Author: Brad King AuthorDate: Thu Oct 18 11:38:09 2018 + Commit: Kitware Robot CommitDate: Thu Oct 18 07:38:15 2018 -0400 Merge topic 'rel-doc-qthelp' 1d5c8b81db Utilities/Release: Add qthelp docs to binary archives Acked-by: Kitware Robot Merge-request: !2497 --- Summary of changes: Help/release/3.13.rst| 3 +++ Utilities/Release/create-cmake-release.cmake | 2 +- 2 files changed, 4 insertions(+), 1 deletion(-) hooks/post-receive -- CMake ___ Cmake-commits mailing list Cmake-commits@cmake.org https://cmake.org/mailman/listinfo/cmake-commits
[Cmake-commits] CMake branch, release, updated. v3.13.0-rc1-23-g2646fd8
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, release has been updated via 2646fd8e03869e2254514f43b0c2a07d89c26076 (commit) via fc675057e4b2135e8381e7ae45801e64c4767e75 (commit) via 1d5c8b81db1cbba79927cc251421b2786ce02866 (commit) via 284a38e42f0416edbfe14813413049fd695cfac0 (commit) from ab0edaabccc16bb568974051ee1e50b10993874a (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log - --- Summary of changes: Help/manual/cmake-server.7.rst | 7 - Help/release/3.13.rst| 3 + Source/cmJsonObjectDictionary.h | 1 - Source/cmJsonObjects.cxx | 214 +-- Source/cmServerProtocol.cxx | 7 +- Utilities/Release/create-cmake-release.cmake | 2 +- 6 files changed, 44 insertions(+), 190 deletions(-) hooks/post-receive -- CMake ___ Cmake-commits mailing list Cmake-commits@cmake.org https://cmake.org/mailman/listinfo/cmake-commits
[Cmake-commits] CMake branch, master, updated. v3.13.0-rc1-137-g5b47557
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".
The branch, master has been updated
via 5b47557c82c24e916c7926d210c9b72ad39c9d2e (commit)
via 284a38e42f0416edbfe14813413049fd695cfac0 (commit)
from aab69ccd9b20a7560d2c656bc1a53a4afa587240 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=5b47557c82c24e916c7926d210c9b72ad39c9d2e
commit 5b47557c82c24e916c7926d210c9b72ad39c9d2e
Merge: aab69cc 284a38e
Author: Brad King
AuthorDate: Thu Oct 18 11:31:09 2018 +
Commit: Kitware Robot
CommitDate: Thu Oct 18 07:31:18 2018 -0400
Merge topic 'revert-server-iface-sources'
284a38e42f cmake-server: Revert "Support codemodel filegroups for
INTERFACE_SOURCES"
Acked-by: Kitware Robot
Merge-request: !2495
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=284a38e42f0416edbfe14813413049fd695cfac0
commit 284a38e42f0416edbfe14813413049fd695cfac0
Author: Brad King
AuthorDate: Wed Oct 17 13:45:16 2018 -0400
Commit: Brad King
CommitDate: Wed Oct 17 14:02:39 2018 -0400
cmake-server: Revert "Support codemodel filegroups for INTERFACE_SOURCES"
Revert commit v3.13.0-rc1~144^2 (cmake-server: Support codemodel
filegroups for INTERFACE_SOURCES, 2018-08-10). The changes activate
code paths not meant to be used with interface libraries. Another
approach will be needed to expose this information later.
This revert has to be done by hand because the code in question has been
changed somewhat since the changes were made, and was also factored out
to another source file.
Fixes: #18463
diff --git a/Help/manual/cmake-server.7.rst b/Help/manual/cmake-server.7.rst
index b4c1436..25d364c 100644
--- a/Help/manual/cmake-server.7.rst
+++ b/Help/manual/cmake-server.7.rst
@@ -308,9 +308,6 @@ which will result in a response type "reply"::
indicating that the server is ready for action.
-Protocol version 1.3 introduces an optional flag on the target filegroup
-that indicates if the filegroup represents :prop_tgt:`INTERFACE_SOURCES`.
-
Type "globalSettings"
^
@@ -527,8 +524,6 @@ FileGroups are used to group sources using similar settings
together.
Each fileGroup object may contain the following keys:
-"isInterfaceSources"
- true if the fileGroup represents :prop_tgt:`INTERFACE_SOURCES`.
"language"
contains the programming language used by all files in the group.
"compileFlags"
@@ -543,8 +538,6 @@ Each fileGroup object may contain the following keys:
"defines"
with a list of defines in the form "SOMEVALUE" or "SOMEVALUE=42". This
value is encoded in the system's native shell format.
-"isGenerated"
- true if the files were generated.
"sources"
with a list of source files.
diff --git a/Source/cmJsonObjectDictionary.h b/Source/cmJsonObjectDictionary.h
index a4d41f3..8a2b529 100644
--- a/Source/cmJsonObjectDictionary.h
+++ b/Source/cmJsonObjectDictionary.h
@@ -43,4 +43,3 @@ static const std::string kCTEST_COMMAND = "ctestCommand";
static const std::string kCTEST_INFO = "ctestInfo";
static const std::string kMINIMUM_CMAKE_VERSION = "minimumCMakeVersion";
static const std::string kIS_GENERATOR_PROVIDED_KEY = "isGeneratorProvided";
-static const std::string kIS_INTERFACE_SOURCES_KEY = "isInterfaceSources";
diff --git a/Source/cmJsonObjects.cxx b/Source/cmJsonObjects.cxx
index a7db75f..4148894 100644
--- a/Source/cmJsonObjects.cxx
+++ b/Source/cmJsonObjects.cxx
@@ -150,8 +150,6 @@ Json::Value cmDumpCMakeInputs(const cmake* cm)
return array;
}
-const std::string kInterfaceSourcesLanguageDataKey =
- "INTERFACE_SOURCES_LD_KEY";
class LanguageData
{
public:
@@ -184,12 +182,6 @@ void LanguageData::SetDefines(const std::set&
defines)
Defines = std::move(result);
}
-struct FileGroupSources
-{
- bool IsInterfaceSources;
- std::vector Files;
-};
-
namespace std {
template <>
@@ -217,35 +209,31 @@ struct hash
} // namespace std
static Json::Value DumpSourceFileGroup(const LanguageData& data,
- bool isInterfaceSource,
const std::vector& files,
const std::string& baseDir)
{
Json::Value result = Json::objectValue;
- if (isInterfaceSource) {
-result[kIS_INTERFACE_SOURCES_KEY] = true;
- }
if (!data.Language.empty()) {
result[kLANGUAGE_KEY] = data.Language;
- }
- if (!data.Flags.empty()) {
-result[kCOMPILE_FLAGS_KEY] = data.Flags;
- }
- if (!data.IncludePathList.empty()) {
-Json::Value includes = Json::arrayValue;
-for (auto const& i : data.IncludePathList) {
-
[CMake] ctest_submit CDASH_UPLOAD causes "Not a valid project" error on a valid project
Hi,
I'm trying to use 'ctest_coverage_collect_gcov(TARBALL gcov.tar)' along
with 'ctest_submit(CDASH_UPLOAD gcov.tar CDASH_UPLOAD_TYPE GcovTar)' to
upload gcov files to our cdash server. Although this succeeds to upload
"normal" results to the server,
ctest_start(${CTEST_DASHBOARD_TYPE})
ctest_configure(BUILD "${CTEST_BINARY_DIRECTORY}")
ctest_build(BUILD "${CTEST_BINARY_DIRECTORY}")
ctest_test(BUILD "${CTEST_BINARY_DIRECTORY}")
ctest_coverage(BUILD "${CTEST_BINARY_DIRECTORY}" QUIET)
ctest_submit()
using the same CTestConfig.cmake,
this command ctest_submit(CDASH_UPLOAD gcov.tar CDASH_UPLOAD_TYPE GcovTar)
leads to
Request upload response: [
ERROR
Not a valid project.
]
Any idea what I'm doing wrong here? I tried to look around forums and docs,
but I couldn't find much help about the CDash Upload API...
Thanks in advance
Vincent
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake
