On Tue, Nov 04, 2014 at 12:53:07AM -0500, Ben Boeckel wrote:
On Mon, Nov 03, 2014 at 16:22:56 -0800, Peter Collingbourne wrote:
This patch exposes the Ninja console pool feature via the add_custom_command
and add_custom_target commands. Specifically, it introduces a USE_CONSOLE
flag which
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=15233
==
Reported By:Bill Torpey
Assigned To:
stage/fix-gcc-hppa
Add -mlong-calls for gcc on HPPA. Merged to next for testing.
- Chuck
--
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
Hello,
I added some tests for the continue command but ran into a
problem when matching stdout output:
302: Expected stdout to match:
302:
302:expect-out a
302:expect-out aa
302:expect-out
302:expect-out a
302:
302: Actual stdout:
302:
302:actual-out Not
Original patch by Doug Barbieri.
Signed-off-by: Gregor Jasny gja...@googlemail.com
---
Help/command/continue.rst | 7 ++
Source/cmBootstrapCommands1.cxx | 2 ++
Source/cmContinueCommand.cxx| 21
Source/cmContinueCommand.h | 55
On 11/04/2014 03:10 PM, Gregor Jasny wrote:
302: Expected stdout to match:
302:
302:expect-out a
302:expect-out aa
302:expect-out
302:expect-out a
The message(STATUS) output lines start with -- so you need to
add that to your expected output in order to match
Hi all,
I was trying to generate the assembly listing for some Fortran code and while
searching for how to do it in CMake, I came across an email thread from a few
years ago from somebody asking how to do it in C/C++ by running `make
file.s`. I vaguely remembered knowing this at one point so I
Hello,
could you please point me to some documentation regarding C++ coding
style? Or do you have a checkpatch script?
Google was not very helpful.
Thanks,
Gregor
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
On 11/04/2014 03:19 PM, Tim Gallagher wrote:
I looked through the CMake source code and it didn't seem that
hard to make it work correctly for Fortran also. I made the
changes on my local branch and it works great for the Intel
and GNU compiler suites on Linux (those are the only ones I
have
On 11/04/2014 03:37 PM, Gregor Jasny wrote:
could you please point me to some documentation regarding C++ coding
style? Or do you have a checkpatch script?
It's never been formalized to that level. Basically:
- Don't exceed 79 columns.
- Align {} with the code inside them.
- CamelCase class
Am Dienstag, 4. November 2014, 11:27:24 schrieb Chuck Atkins:
stage/fix-gcc-hppa
Add -mlong-calls for gcc on HPPA. Merged to next for testing.
Sorry,
saw this mail only after I mailed you privately because I looked into the
commit log first. For general consumption, here are the relevant
Hi Brad,
Thanks for the info.
What does the CMAKE_EXPORT_COMPILE_COMMANDS do? Or maybe more precisely, what
output should I expect when it is set to ON instead of OFF? I tried it with my
changes and nothing breaks, but I also don't see any difference in outputs with
it set to ON so maybe I
Scratch that, I found it. Wasn't looking in the right places!
The export command works for Fortran, so that's not an issue.
I'll take a look at the testing and see if I can get that going. I'll send
along a patch when I get it worked out.
Thanks,
Tim
- Original Message -
From: Tim
Please make sure you also add these to bootstrap.sh.
Will do.
And please see the very end of
CompileFlags.cmake where we already added workarounds for HPPA. Until now
we
have not seen the problem on HP-UX, so this has been restricted to Linux
until
now.
I considered putting it in
Am Dienstag, 4. November 2014, 16:17:08 schrieb Chuck Atkins:
Please make sure you also add these to bootstrap.sh.
Will do.
And please see the very end of
CompileFlags.cmake where we already added workarounds for HPPA. Until now
we have not seen the problem on HP-UX, so this has been
just a matter of taste if this will be narrowed to Linux or not. In any
case
please try if you can just drop the existing workarounds. The best would
probably to just replace their set() with yours and see if it works. If it
does you can remove the if(Linux) and only match for the processor.
On 10/31/14, Gilles Khouzam gilles.khou...@microsoft.com wrote:
We actually have a couple if extra changes that are not fully ready to be
pushed upstream yet.
~Gilles
Sent from my Windows Phone
Since I have your attention, using CMakeMS, I hit what looks like a
bug in the generation for the
Hi Brad,
I have attached the patch to enable the targets for Fortran. It includes
updates to 2 tests to make sure that it works as expected. Both of the tests
pass for me with Intel and GNU but that's all I have access to.
Let me know if I messed anything up or if you have any suggestions on
On 11/4/14, Gilles Khouzam gilles.khou...@microsoft.com wrote:
Hi Eric,
Can you send me a little more details or an example that exhibits the
problem? I'd be happy to take a look.
Sure. I'll respond offlist for this.
Thanks,
Eric
--
Powered by www.kitware.com
Please keep messages
Hi Eric,
Can you send me a little more details or an example that exhibits the problem?
I'd be happy to take a look.
-Original Message-
From: Eric Wing [mailto:ewmail...@gmail.com]
Sent: Tuesday, November 4, 2014 15:21
To: Gilles Khouzam
Cc: Brad King; Robert Maynard; CMake
20 matches
Mail list logo