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, next has been updated
via 870d4341f25524a1c58a25e2289f8c00ed584845 (commit)
via
You’re doing it all wrong. You do not name source files as make targets, but
the target name (or project name, I have no idea, because it rarely makes sense
to name them differently). Try simply “foo” or “custom-command-target”. You
would never say “make foo.cpp”, not even in an ordinary GNU
Hello,
short description: I want to have a configuration header file per unit test.
For this purpose I wrote the following function, which creates a header file
in ${CURRENT_BINARY_DIR} and copy all test files into the binary
directory.
Howewer, I got it to work when I use
@kgt: Thank you for this great hint. :-)
I had overlooked this button in Visual Studio
@mjklaim: I didn't see this behavior in older CMake versions.
Roman
-Ursprüngliche Nachricht-
Von: Thompson, KT [mailto:k...@lanl.gov]
Gesendet: Dienstag, 02. Juni 2015 15:52
An: Roman Wüger;
The following issue has been SUBMITTED.
==
http://www.itk.org/Bug/view.php?id=15612
==
Reported By:tim blechmann
Assigned To:
Hello,
short description: I want to have a configuration header file per unit test.
For this purpose I wrote the following function, which creates a header file
in ${CURRENT_BINARY_DIR} and copy all test files into the binary
directory.
Howewer, I got it to work when I use
Hi!
I'm having some issues with Ninja on Windows with long custom commands (or
actually a long succession of short commands appended to the same target).
The problem is that they get concatenated in one single command using
and it is pretty easy to go over the 8k command line size limit on
The following issue has been SUBMITTED.
==
https://public.kitware.com/Bug/view.php?id=15611
==
Reported By:Valerii Kanunik
Assigned To:
The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=15613
==
Reported By:Xiaoming Wang
Assigned To:
Hooray! Thanks!
Could a future version of cmake provide a nicer way to do this, without these
error messages?
0 Fri 12:29:25 yost DaveBook ~/p/c++/cmake/custom-command-target/build
391 Z% make foo.cc
Scanning dependencies of target foo.cc
make[3]: Circular CMakeFiles/foo.cc - foo.cc dependency
The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=15614
==
Reported By:FlorianM
Assigned To:
Hello,
Is there a SOURCE_DIR property for targets? I wasn't able to find
anything in the documentation on this, however I thought I saw
something similar to this a few years ago. I'm using CMake 3.2.
Basically I want the equivalent of CMAKE_CURRENT_SOURCE_DIR, but for a
specific project.
20150612)
+set(CMake_VERSION_PATCH 20150613)
#set(CMake_VERSION_RC 1)
---
Summary of changes:
Source/CMakeVersion.cmake |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/post-receive
--
CMake
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=15615
==
Reported By:vinipsmaker
Assigned To:
Here's the updated patch file with tests added. Let me know if it's good to go.
-Original Message-
From: Brad King [mailto:brad.k...@kitware.com]
Sent: Thursday, June 11, 2015 8:55 AM
To: Robert Goulet
Cc: cmake-developers@cmake.org
Subject: Re: [cmake-developers] Generator expressions
Am 12. Juni 2015 16:46:47 MESZ, schrieb Matthew Karas mkarasc...@gmail.com:
This is probably and XY problem but...
I'm trying to install a systemd file in my cmake.
The service file needs to point at the installed destination of my
build after I make install.
I was trying to use
This is probably and XY problem but...
I'm trying to install a systemd file in my cmake.
The service file needs to point at the installed destination of my
build after I make install.
I was trying to use CONFIGURE_FILE
When I tried to do this - the variable is blank because the configure
file
If you run make help it will list targets it understands. And as you
pointed out there is no target for foo.cc. You can make foo but if you
really want a target for foo.cc you can add one yourself:
cmake_minimum_required(VERSION 3.0.0)
project(custom-command-target)
add_custom_command (
I’m having trouble determining the right way to enforce `-O0` optimization
level when the user selects a boolean cache entry to enable code coverage
with gcov. I tried something like:
if ( ENABLE_CODE_COVERAGE )
set ( CMAKE_Fortran_FLAGS “${CMAKE_Fortran_FLAGS} -fprofile-arcs
I’m not doing it wrong. Remember, this is a simplified example.
We want to be able to make foo.cc so we can look at it and compare it. Yes, we
could make foo and then look at foo.cc, but until foo.cc is right, we will
suffer a lot of compiler error clutter. When foo.cc looks right, then we will
20 matches
Mail list logo
