On 01/21/2011 08:47 AM, Andreas Pakulat wrote:
On 21.01.11 01:37:41, Michael Hertling wrote:
So, what's your conclusion in this matter? Should the behavior in
question be considered as a bug or is it alright? IMO, such a subtle
side effect of a read operation on a subsequent write operation is
On 01/21/2011 04:41 PM, Alexander Neundorf wrote:
On Friday 21 January 2011, Michael Hertling wrote:
On 01/20/2011 07:01 PM, Alexander Neundorf wrote:
On Sunday 09 January 2011, Michael Hertling wrote:
...
I don't really understand why you want to get the LOCATION from your
target, anyway,
On Friday 21 January 2011, Michael Hertling wrote:
On 01/20/2011 07:01 PM, Alexander Neundorf wrote:
On Sunday 09 January 2011, Michael Hertling wrote:
...
I don't really understand why you want to get the LOCATION from your
target, anyway, the get_target_property works fine if you use
On Sunday 09 January 2011, Michael Hertling wrote:
On 01/09/2011 09:47 PM, Nizar Khalifa Sallem wrote:
At Sun, 09 Jan 2011 21:42:49 +0100,
Michael Hertling wrote:
On 01/09/2011 09:09 PM, Andreas Pakulat wrote:
On 09.01.11 21:05:21, Andreas Pakulat wrote:
On 09.01.11 14:24:16, Michael
On 01/20/2011 07:01 PM, Alexander Neundorf wrote:
On Sunday 09 January 2011, Michael Hertling wrote:
On 01/09/2011 09:47 PM, Nizar Khalifa Sallem wrote:
At Sun, 09 Jan 2011 21:42:49 +0100,
Michael Hertling wrote:
On 01/09/2011 09:09 PM, Andreas Pakulat wrote:
On 09.01.11 21:05:21, Andreas
On 21.01.11 01:37:41, Michael Hertling wrote:
So, what's your conclusion in this matter? Should the behavior in
question be considered as a bug or is it alright? IMO, such a subtle
side effect of a read operation on a subsequent write operation is at
least highly surprising. Besides, does one
Hi,
I'm having a bit of a problem here changing the runtime output directory
for a binary. Its an executable target named 'setup' and I'd like to put it
into the top-level directory. Unfortunately it always ends up in the bin/
directory, which is what CMAKE_RUNTIME_OUTPUT_DIRECTORY is being set
On 01/09/2011 12:58 PM, Andreas Pakulat wrote:
Hi,
I'm having a bit of a problem here changing the runtime output directory
for a binary. Its an executable target named 'setup' and I'd like to put it
into the top-level directory. Unfortunately it always ends up in the bin/
directory, which
On 09.01.11 14:24:16, Michael Hertling wrote:
On 01/09/2011 12:58 PM, Andreas Pakulat wrote:
Hi,
I'm having a bit of a problem here changing the runtime output directory
for a binary. Its an executable target named 'setup' and I'd like to put it
into the top-level directory.
On 09.01.11 21:09:37, Andreas Pakulat wrote:
On 09.01.11 21:05:21, Andreas Pakulat wrote:
On 09.01.11 14:24:16, Michael Hertling wrote:
On 01/09/2011 12:58 PM, Andreas Pakulat wrote:
Hi,
I'm having a bit of a problem here changing the runtime output directory
for a binary.
At Sun, 9 Jan 2011 21:09:37 +0100,
Andreas Pakulat wrote:
[1 text/plain; us-ascii (7bit)]
On 09.01.11 21:05:21, Andreas Pakulat wrote:
On 09.01.11 14:24:16, Michael Hertling wrote:
On 01/09/2011 12:58 PM, Andreas Pakulat wrote:
Hi,
I'm having a bit of a problem here changing
At Sun, 09 Jan 2011 21:42:49 +0100,
Michael Hertling wrote:
On 01/09/2011 09:09 PM, Andreas Pakulat wrote:
On 09.01.11 21:05:21, Andreas Pakulat wrote:
On 09.01.11 14:24:16, Michael Hertling wrote:
On 01/09/2011 12:58 PM, Andreas Pakulat wrote:
Hi,
I'm having a bit of a problem here
On 01/09/2011 09:32 PM, Nizar Khalifa Sallem wrote:
At Sun, 9 Jan 2011 21:09:37 +0100,
Andreas Pakulat wrote:
[1 text/plain; us-ascii (7bit)]
On 09.01.11 21:05:21, Andreas Pakulat wrote:
On 09.01.11 14:24:16, Michael Hertling wrote:
On 01/09/2011 12:58 PM, Andreas Pakulat wrote:
Hi,
I'm
On 01/09/2011 09:47 PM, Nizar Khalifa Sallem wrote:
At Sun, 09 Jan 2011 21:42:49 +0100,
Michael Hertling wrote:
On 01/09/2011 09:09 PM, Andreas Pakulat wrote:
On 09.01.11 21:05:21, Andreas Pakulat wrote:
On 09.01.11 14:24:16, Michael Hertling wrote:
On 01/09/2011 12:58 PM, Andreas Pakulat
Thanks, Michael.
Hmm. I wonder what it is then, and why just today?
mm
-Original Message-
From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf Of
Michael Hertling
Sent: Sunday, January 09, 2011 4:27 PM
To: cmake@cmake.org
Subject: Re: [CMake] Restrictions on
Sorry, Nizar - I unintentionally hijacked the thread. I wasn't commenting
on your problem.
My bad,
mm
-Original Message-
From: Nizar Khalifa Sallem [mailto:nksal...@laas.fr]
Sent: Sunday, January 09, 2011 4:49 PM
To: Martin O'Brien
Cc: cmake@cmake.org
Subject: Re: [CMake] Restrictions
At Sun, 9 Jan 2011 16:50:35 -0500,
Martin O'Brien wrote:
Sorry, Nizar - I unintentionally hijacked the thread. I wasn't commenting
on your problem.
My bad,
mm
-Original Message-
From: Nizar Khalifa Sallem [mailto:nksal...@laas.fr]
Sent: Sunday, January 09, 2011 4:49 PM
On 09.01.11 22:48:34, Nizar Khalifa Sallem wrote:
I don't really understand why you want to get the LOCATION from your
target, anyway, the get_target_property works fine if you use
set_target_properties before it. [...]
...but SET_TARGET_PROPERTIES() doesn't work fine if it's used
18 matches
Mail list logo