[Cmake-commits] CMake branch, master, updated. v3.13.3-982-gc902e77
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 c902e775ec3fc2f3c6f6c4273142bfe6f73f4c57 (commit) from a61c061b6143cb6d8920b1b5796a867c0f104556 (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=c902e775ec3fc2f3c6f6c4273142bfe6f73f4c57 commit c902e775ec3fc2f3c6f6c4273142bfe6f73f4c57 Author: Kitware Robot AuthorDate: Sat Jan 19 00:01:07 2019 -0500 Commit: Kitware Robot CommitDate: Sat Jan 19 00:01:07 2019 -0500 CMake Nightly Date Stamp diff --git a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake index 245bd71..acaeacf 100644 --- a/Source/CMakeVersion.cmake +++ b/Source/CMakeVersion.cmake @@ -1,5 +1,5 @@ # CMake version number components. set(CMake_VERSION_MAJOR 3) set(CMake_VERSION_MINOR 13) -set(CMake_VERSION_PATCH 20190118) +set(CMake_VERSION_PATCH 20190119) #set(CMake_VERSION_RC 1) --- Summary of changes: Source/CMakeVersion.cmake | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/post-receive -- CMake ___ Cmake-commits mailing list Cmake-commits@cmake.org https://cmake.org/mailman/listinfo/cmake-commits
Re: [CMake] Issue with qt5_add_resources with unit tests
That was it. I wound up finding a slightly different solution. I create a
static library of the resources, and then have the unit tests link in that lib.
Which gets the same dependency tree the custom target.
My question, that I'm still confused about is why this is necessary.
I have two projects, that depens on the output of a single input
But this works
~~Scott
Original message
From: "Alan W. Irwin"
Date: 1/18/19 19:11 (GMT-08:00)
To: Scott Bloom
Cc: cmake Mailing List
Subject: Re: [CMake] Issue with qt5_add_resources with unit tests
On 2019-01-19 00:09- Scott Bloom wrote:
> I use qt + google test to run tests in my build environment.
>
> The problem I have, is in some (most) of my unit test directories, there will
> be multiple test executables created, all dependent on the same output file
> from the add_resources step.
>
> Typically its something like
>
> qt_add_resource( resourceVar resource.qrc )
>
> add_executable( test1 test1main.cpp ${resourceVar} )
> add_executable( test2 test2main.cpp ${resourceVar} )
>
> On windows (running the build from cmake through visual studio with parallel
> building turned on) this sometimes (1 out of 20 or 30 builds or so) causes a
> race condition, where the dependency on the qrc_resource.cpp is attempted to
> be generated by both executable dependencies at once.
>
> Not sure what is going on, but wondering if there was any advice out there
> for this problem
Hi Scott:
I could find no google hits for qt_add_resource (except for your
question). But that search did ask is "qt5_add_resources" what
you meant?
If so there is a rather old but still useful
discussion at
for what appears to be exactly the problem you describe. See
especially the CMake code associated with this comment:
"The workaround is to add a custom target and add explicit depends on that".
Actually, regardless of causes and whether you were refererring to
qt5_add_resources or not I think that workaround will work to solve
your issue since in a parallel build environment a custom target and
relevant dependencies on that target always assures just one build
(rather than multiple builds which race with each other) of whatever
it refers to.
Alan
__
Alan W. Irwin
Programming affiliations with the FreeEOS equation-of-state
implementation for stellar interiors (freeeos.sf.net); the Time
Ephemerides project (timeephem.sf.net); PLplot scientific plotting
software package (plplot.sf.net); the libLASi project
(unifont.org/lasi); the Loads of Linux Links project (loll.sf.net);
and the Linux Brochure Project (lbproject.sf.net).
__
Linux-powered Science
__
--
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] Issue with qt5_add_resources with unit tests
On 2019-01-19 00:09- Scott Bloom wrote:
I use qt + google test to run tests in my build environment.
The problem I have, is in some (most) of my unit test directories, there will
be multiple test executables created, all dependent on the same output file
from the add_resources step.
Typically its something like
qt_add_resource( resourceVar resource.qrc )
add_executable( test1 test1main.cpp ${resourceVar} )
add_executable( test2 test2main.cpp ${resourceVar} )
On windows (running the build from cmake through visual studio with parallel
building turned on) this sometimes (1 out of 20 or 30 builds or so) causes a
race condition, where the dependency on the qrc_resource.cpp is attempted to be
generated by both executable dependencies at once.
Not sure what is going on, but wondering if there was any advice out there for
this problem
Hi Scott:
I could find no google hits for qt_add_resource (except for your
question). But that search did ask is "qt5_add_resources" what
you meant?
If so there is a rather old but still useful
discussion at
for what appears to be exactly the problem you describe. See
especially the CMake code associated with this comment:
"The workaround is to add a custom target and add explicit depends on that".
Actually, regardless of causes and whether you were refererring to
qt5_add_resources or not I think that workaround will work to solve
your issue since in a parallel build environment a custom target and
relevant dependencies on that target always assures just one build
(rather than multiple builds which race with each other) of whatever
it refers to.
Alan
__
Alan W. Irwin
Programming affiliations with the FreeEOS equation-of-state
implementation for stellar interiors (freeeos.sf.net); the Time
Ephemerides project (timeephem.sf.net); PLplot scientific plotting
software package (plplot.sf.net); the libLASi project
(unifont.org/lasi); the Loads of Linux Links project (loll.sf.net);
and the Linux Brochure Project (lbproject.sf.net).
__
Linux-powered Science
__
--
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] Issue with qt5_add_resources with unit tests
I use qt + google test to run tests in my build environment.
The problem I have, is in some (most) of my unit test directories, there will
be multiple test executables created, all dependent on the same output file
from the add_resources step.
Typically its something like
qt_add_resource( resourceVar resource.qrc )
add_executable( test1 test1main.cpp ${resourceVar} )
add_executable( test2 test2main.cpp ${resourceVar} )
On windows (running the build from cmake through visual studio with parallel
building turned on) this sometimes (1 out of 20 or 30 builds or so) causes a
race condition, where the dependency on the qrc_resource.cpp is attempted to be
generated by both executable dependencies at once.
Not sure what is going on, but wondering if there was any advice out there for
this problem
Scott
--
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] Fwd: CMake fails with message requesting to send cache file
Hey, sending as requested; please find attached file... my os: Win10 (updated) build env. (msys2, updated) project: spdlog (FOSS, last release) The result was observed as follow: - clone project - mkdir build && cd build - ccmake -G"MSYS Makefiles" .. Thanks, Lubomir. # This is the CMakeCache file. # For build in directory: /home/lubom/work/spdlog/build # It was generated by CMake: /usr/bin/cmake.exe # You can edit this file to change values found and used by cmake. # If you do not want to change any of the values, simply exit the editor. # If you do want to change a value, simply edit, save, and exit the editor. # The syntax for the file is as follows: # KEY:TYPE=VALUE # KEY is the name of a variable in the cache. # TYPE is a hint to GUIs for the type of VALUE, DO NOT EDIT TYPE!. # VALUE is the current value for the KEY. # EXTERNAL cache entries # INTERNAL cache entries //This is the directory where this CMakeCache.txt was created CMAKE_CACHEFILE_DIR:INTERNAL=/home/lubom/work/spdlog/build //Major version of cmake used to create the current loaded cache CMAKE_CACHE_MAJOR_VERSION:INTERNAL=3 //Minor version of cmake used to create the current loaded cache CMAKE_CACHE_MINOR_VERSION:INTERNAL=13 //Patch version of cmake used to create the current loaded cache CMAKE_CACHE_PATCH_VERSION:INTERNAL=2 //Path to CMake executable. CMAKE_COMMAND:INTERNAL=/usr/bin/cmake.exe //Path to cpack program executable. CMAKE_CPACK_COMMAND:INTERNAL=/usr/bin/cpack.exe //Path to ctest program executable. CMAKE_CTEST_COMMAND:INTERNAL=/usr/bin/ctest.exe //Path to CMake installation. CMAKE_ROOT:INTERNAL=/usr/share/cmake-3.13.2 -- 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
