Hi all.
I hope I don't derail the conversation, but since there's now discussion of
providing a new interface and perhaps behaviour-changing parameters for
cmake_parse_arguments(), I'd like to mention another behaviour switch I
would find useful.
I maintain a CMake framework for a large collectio
On 11/06/2013 03:45 PM, Pedro Navarro wrote:
> I'm debugging an issue with P4 updates and would like to get
> the output of all the p4 commands I issue, like the ones to
> get the old and new revisions. I'm interested in both the stdout
> and stderr output, which I'm capturing with OutputLoggers.
+1
I like the idea of the ["Apply Command Line Parameters" button appear
whenever -Dvar=value parameters were passed.]
Would also be nice if parameter like "-G" ... could also be considered for
the first configuration. Within some of our project, I envision user
downloading a "bat" script named "
Hi,
I'm debugging an issue with P4 updates and would like to get the output of
all the p4 commands I issue, like the ones to get the old and new
revisions. I'm interested in both the stdout and stderr output, which I'm
capturing with OutputLoggers. Is is enough to do -VV -O file.txt ?
Thanks!
Ped
On 11/06/2013 02:55 PM, physhh . wrote:
> How should we proceed? I think Mathew understood what's my problem.
This thread has covered use cases in which it makes sense to apply
(or not apply) command-line parameters in cmake-gui for various
cases. No one automatic behavior is going to satisfy eve
On 2013-11-06 13:57, Brad King wrote:
On 11/06/2013 01:32 PM, Alexander Neundorf wrote:
Adding proper named argument handling to cmake_parse_arguments() itself is
somewhat complicated since it can't make use of cmake_parse_arguments() ;-)
Since the need for this is so common, perhaps we should
Well I've tried to make the problem as clear as possible but somehow it
seems it still wasn't clear enough.
In my opinion the solution which was proposed by Mathew was also pretty
clear - also not absolutly complete as he stated himself.
How should we proceed? I think Mathew understood what's my p
On 11/06/2013 01:32 PM, Alexander Neundorf wrote:
> Adding proper named argument handling to cmake_parse_arguments() itself is
> somewhat complicated since it can't make use of cmake_parse_arguments() ;-)
Since the need for this is so common, perhaps we should provide a
C++-implemented command to
On Wednesday 06 November 2013, Daniele E. Domenichelli wrote:
> On 05/11/13 20:51, Alexander Neundorf wrote:
> >> I don't know if this is to be considered a change of behaviour though,
> >> but I'd rather consider it a bug, and I would like to see it fixed in
> >> the next bugfix release... what do
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=14548
==
Reported By:Steve Wolak
Assigned To:
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=14547
==
Reported By:Hajime Yoshimori
Assigned To:
On 05/11/13 20:51, Alexander Neundorf wrote:
>> I don't know if this is to be considered a change of behaviour though,
>> but I'd rather consider it a bug, and I would like to see it fixed in
>> the next bugfix release... what do you think?
>
> cmake_parse_arguments() is used in quite a few places
12 matches
Mail list logo
