On 29.05.2013 22:59, Matthew Woehlke wrote:
On 2013-05-28 21:23, Wojciech Knapik wrote:
On Fri, May 24, 2013 at 11:21:57AM -0400, Matthew Woehlke wrote:
[...]
I do understand the distinction between calling cmake and make and I
understood from the start when variables are evaluated and such,
On Wednesday 29 May 2013, Matthew Woehlke wrote:
On 2013-05-28 19:50, Wojciech Knapik wrote:
Files don't just happen to be lying around in directories. You have to
create them in a specific path, with a specific name. Even if the act of
creation was performed by another developer, on
Brad King wrote:
On 05/10/2013 06:41 AM, Stephen Kelly wrote:
* http://thread.gmane.org/gmane.comp.programming.tools.cmake.devel/5680
(New INTERFACE_LINK_LIBRARIES policy approach)
I remember being quite happy with the proposal I made at the start of
that thread. Let's see if we can
To illustrate the problem on Linux:
wine@raven touch test1; cmake -E touch test2; touch test3
wine@raven ls -lrt --time-style=full-iso test[123]
-rw-r--r-- 1 wine wine 0 2013-05-30 04:18:25.0 -0700 test2
-rw-r--r-- 1 wine wine 0 2013-05-30 04:18:25.761281846 -0700 test1
-rw-r--r-- 1 wine
Steve,
I think we're pretty close to agreement here!
On 05/30/2013 05:31 AM, Stephen Kelly wrote:
This will give projects a choice on whether they want to populate the
old properties explicitly or ask CMake to do it for them.
Rather than offer so much choice for something which is pure
On 05/30/2013 08:26 AM, Alan W. Irwin wrote:
To illustrate the problem on Linux:
wine@raven touch test1; cmake -E touch test2; touch test3
wine@raven ls -lrt --time-style=full-iso test[123]
-rw-r--r-- 1 wine wine 0 2013-05-30 04:18:25.0 -0700 test2
-rw-r--r-- 1 wine wine 0
On Wed, May 29, 2013 at 04:59:22PM -0400, Matthew Woehlke wrote:
On 2013-05-28 21:23, Wojciech Knapik wrote:
On Fri, May 24, 2013 at 11:21:57AM -0400, Matthew Woehlke wrote:
GLOB is just one of many things that will surprise you when working with
CMake if you don't understand the
Hi Folks,
Putting on my list moderation hat, I'd like to terminate the debate
in this thread. Arguments on both sides have been hashed out a few
times. Whether we all agree or not, some people find source globs
useful and it will not be disruptive to CMake to add an option to
add dependencies
Brad King wrote:
Steve,
I think we're pretty close to agreement here!
On 05/30/2013 05:31 AM, Stephen Kelly wrote:
This will give projects a choice on whether they want to populate the
old properties explicitly or ask CMake to do it for them.
Rather than offer so much choice for
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=14179
==
Reported By:azdagron
Assigned To:
The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=14178
==
Reported By:nob
Assigned To:
Hi
I want to write several self-contained modules that would each hijack a
standard CMake function in order to execute some CMake code when
necessary, without requiring the user to alter their existing
CMakeLists.
The idea is that including the module will provide functionality with no
other
On 05/30/2013 10:50 AM, Stephen Kelly wrote:
I'm not convinced that a policy to disallow the old and new signatures
together is actually better though. It preserves the historical behavior
even if the policy is NEW, and will be a bit confusing for anyone attempting
to use a new signature
On 05/30/2013 11:14 AM, Wojciech Knapik wrote:
The problem is, that you can't redefine, say, add_executable more than
once, as discussed here:
http://www.cmake.org/pipermail/cmake/2011-March/043320.html
The command-override feature is meant for local debugging only.
Allowing recursive
On 2013-05-30 08:47, Wojciech Knapik wrote:
Working with make taught me once and for all, that functions like
[execute_process] should be avoided whenever possible. A build tool
creates files from files via the means of targets. So if you want to
use a tool like this effectively, you should use
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=14180
==
Reported By:mwoehlke
Assigned To:
Hi Folks,
Being able to activate the dynamic globing on a per-directory or per-target
or per-glob call basis would be nice. Coupled with automoc feature of Qt,
that would simplify things greatly.
I would be happy to test patches on our large scale project 3DSlicer.
See
On Thu, May 30, 2013 at 11:39:01AM -0400, Brad King wrote:
On 05/30/2013 11:14 AM, Wojciech Knapik wrote:
The problem is, that you can't redefine, say, add_executable more than
once, as discussed here:
http://www.cmake.org/pipermail/cmake/2011-March/043320.html
The command-override
On 2013-05-30 08:28-0400 Brad King wrote:
On 05/30/2013 08:26 AM, Alan W. Irwin wrote:
To illustrate the problem on Linux:
wine@raven touch test1; cmake -E touch test2; touch test3
wine@raven ls -lrt --time-style=full-iso test[123]
-rw-r--r-- 1 wine wine 0 2013-05-30 04:18:25.0 -0700
On Thu, May 30, 2013 at 08:01:16PM +0200, Wojciech Knapik wrote:
On Thu, May 30, 2013 at 11:39:01AM -0400, Brad King wrote:
On 05/30/2013 11:14 AM, Wojciech Knapik wrote:
PS. I know you can achieve this by providing a wrapper for the user to
use instead of the standard function, but
The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=14181
==
Reported By:Wojciech Knapik
Assigned To:
21 matches
Mail list logo
