Site:
>Build name: (empty)
> Create new tag: 20150130-2000 - Experimental
> Cannot find file:
> /home/fe/atlassian/bamboo_builds/131076/FE-MP88-UT/build/DartConfiguration.tcl
> Test project /home/fe/atlassian/bamboo_builds/131076/FE-MP88-UT/build
> Start 1: Test_UI_List
file:
/home/fe/atlassian/bamboo_builds/131076/FE-MP88-UT/build/DartConfiguration.tcl
Site:
Build name: (empty)
Create new tag: 20150130-2000 - Experimental
Cannot find file:
/home/fe/atlassian/bamboo_builds/131076/FE-MP88-UT/build/DartConfiguration.tcl
Test project /home/fe/atlassian/bamboo_b
>
> Ok. In that case you must be doing something different to the testcase:
> http://www.cmake.org/gitweb?p=cmake.git;a=commitdiff;h=6e1c359fe9
> If you have a http://sscce.org/ please add it to
> http://public.kitware.com/Bug/view.php?id=15074
The issue report you linked indicates that the fix
Do you have a CTestConfig.cmake file in your source tree?
If you do, then ctest will load that instead of looking for the
DartConfiguration.tcl file in your build tree... Even if it's empty
because you don't submit to a CDash server, the presence of
CTestConfig.cmake in your top level source tree
Here, to generate XML for Jenkins' xUnit plugin, we run "ctest -T Test -j2"
which has never complained about missing DartConfiguration.tcl.
--
Daniel Schepler
From: CMake [cmake-boun...@cmake.org] on behalf of Robert Dailey
[rcdailey.li...@gmail.com]
Sent
Norbert Pfeiler wrote:
>>
>> > When i use qt5_add_resources and some of my resources change they get
>> > recompiled during the next invocation of my build tool. Whereas when i
>> use
>> > cmakes autorcc this is not the case.
>> This was fixed in CMake 3.1.
>
>
> Well, I’m using CMake 3.1.1, so
I run ctest on my build server *just* to run the test executables and
get result XML. I use a separate tool to parse the XML and upload it
to an unrelated server (not CDash)
I get errors like below:
Cannot find file: /sourcerepo/build/DartConfiguration.tcl
Can someone explain what CTest is doing
On 1/29/15 1:34 PM, Stephen Kelly wrote:
Chris Green wrote:
this library is found with
find_library as part of a config.cmake file invoked as part of
find_package()
Consider reading
http://www.cmake.org/cmake/help/v3.1/manual/cmake-packages.7.html
at some point.
find_library and config
Ah, I found the problem. I had the output file listed in the custom
command's DEPEND clause.
Thank you very much for all the help!
On Fri, Jan 30, 2015 at 11:07 AM, Chris Johnson wrote:
> I'm trying to use the method outlined in your #2, with the list of files.
> But I get circular dependency
I'm trying to use the method outlined in your #2, with the list of files.
But I get circular dependency errors, with messages like this one (for each
file):
make[2]: Circular validate/X12_Standards/997_5010.x12 <-
validate/X12_Standards/997_5010.x12 dependency dropped.
On Fri, Jan 30, 2015 at 10:
I believe the classic "driving target" approach could be used here. Add a
custom target which will drive the custom commands by depending on their
outputs:
add_custom_target(
RunMyProg ALL
DEPENDS
${CMAKE_CURRENT_BINARY_DIR}/file001.out
${CMAKE_CURRENT_BINARY_DIR}/file002.out
#...
On 1/30/2015 10:40 AM, Chris Johnson wrote:
Petr, thanks. That makes a lot of sense.
Now I am struggling with causing all of these files to be generated when
I do the default build target, e.g. just "make" in the build directory.
That is, I want myprog to be compiled, and then all of the files
Petr, thanks. That makes a lot of sense.
Now I am struggling with causing all of these files to be generated when I
do the default build target, e.g. just "make" in the build directory. That
is, I want myprog to be compiled, and then all of the files processed by it
with just one build command.
file(GLOB ... ) might be of interest to get the list of files
--
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, plea
As you say, **make** is fairly powerful at this. Other build tools may not
be, it might even be an alien concept to them. AFAIK, Ninja requires an
explicit list of files & dependencies, for example. Visual Studio solutions
can only contain explicitly listed files too.
CMake projects are supposed t
Great! I would certainly like this functionality to be officially added to
CMake and in the mean time will use your module... speaking of which, it
seems that it was scrubbed from the digest email, or not originally
attached. Can you please send it to me?
On Thu, Jan 29, 2015 at 8:42 PM wrote:
>
Unfortunately it would take more than one run of CPack, but you may
find useful something like:
in CMakeLists.txt:
set( CPACK_PROJECT_CONFIG_FILE
"${CMAKE_CURRENT_SOURCE_DIR}/CMakeCPackOptions.cmake" )
in CMakeCPackOptions.cmake:
set( CPACK_PACKAGE_FILE_NAME "${CPACK_PACKAGE_NAME}" )
which woul
That does clarify a few things yes. Thank you.
By "configure" time I had meant the first two items you listed as Configure
and Generate. By "run" time I had meant what you called Build.
One place I am unclear on is exactly which commands in CMakeLists.txt get
translated into Build time commands
On 01/29/2015 11:24 PM, Iosif Neitzke wrote:
Where for a single run of CPack, each component name produces a
corresponding named .deb file or ...?
Yes. Exactly.
Have you tried using CPACK_PROJECT_CONFIG_FILE [0]? This allows you
to set a few options at packaging time which can change the final
It's not clear to me what you mean with "run" time. There are the following
"times" involved in a CMake-based project:
* Configure time:
CMake is parsing CMakeLists.txt files and files included from those and
executing ALL CMake commands found in them. Variables expansion takes
place. Data structu
20 matches
Mail list logo
