_VERSION_MINOR 7)
-set(CMake_VERSION_PATCH 20161219)
+set(CMake_VERSION_PATCH 20161220)
#set(CMake_VERSION_RC 1)
---
Summary of changes:
Source/CMakeVersion.cmake |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/
On 12/18/2016 8:57 AM, David Cole via CMake wrote:
This "compare" view on GitHub shows the difference between the
regular/upstream ninja and the Kitware patched ninja:
https://github.com/ninja-build/ninja/compare/master...Kitware:features-for-fortran
The ReadMe explains the high-level
Are you able to send me the CMakeError.log and CMakeOutput.log from
your build/CMakeFiles/ directory.
On Mon, Dec 19, 2016 at 4:51 AM, James Turner wrote:
>
>> On 16 Dec 2016, at 22:59, Robert Maynard wrote:
>>
>> That is odd. Inside your
On Tue, Nov 8, 2016 at 10:28 AM, wrote:
>
>
> - On Nov 8, 2016, at 8:13 AM, Taylor Braun-Jones tay...@braun-jones.org
> wrote:
>
>> On Fri, Nov 4, 2016 at 2:55 PM, Brad King wrote:
>>>
>>> On 11/03/2016 06:04 PM, John Drescher wrote:
>>> > I
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 934289dd5dce80d4f8e53b5dfdb3c300e3dbf5b2 (commit)
via
> On 16 Dec 2016, at 22:59, Robert Maynard wrote:
>
> That is odd. Inside your build/CMakeFiles should be a file called
> feature_tests.cxx, and that file is how we determine what features the
> clang compiler supports.
>
> I would use that to determine why feature
Hi,
I'm using ExternalProject_Add to handle this situation with multiple
platforms/targets.
https://cmake.org/cmake/help/v3.7/module/ExternalProject.html
Hope this works for you.
On Mon, Dec 19, 2016 at 1:41 AM, Harshal Singhal wrote:
> Hello,
>
> I have a VS2013 project