The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=15373
==
Reported By:Dimitri Merejkowsky
Assigned To:
The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=15376
==
Reported By:tron_thomas
Assigned To:
Ok, make sense. However, the generator is essentially the same for both Win32
and WinRT except for a very few properties. Turns out I was able to make a
patch, however I don't know if that's going to be rejected because of the way I
did it, but it works really well so far.
This allow me to set
If the flag would be wrong, compilation would fail.
-Original Message-
From: Brad King [mailto:brad.k...@kitware.com]
Sent: Tuesday, January 27, 2015 12:59 PM
To: Robert Goulet
Cc: cmake-developers@cmake.org
Subject: Re: [cmake-developers] Setting additional compile flags to .hlsl files?
On Monday 26 January 2015 18:22:41 Ben Boeckel wrote:
On Mon, Jan 26, 2015 at 22:39:00 +, Alex Merry wrote:
Maybe it's just my colour scheme - I'll have a play with the colour
settings when I have some free time.
FWIW, I use neverland-darker, a 256-color scheme. Looking at it with an
Guillaume Belz wrote:
Hi,
OpenSSL 1.0.2 was released last week and there is a little change in code,
which impact FindOpenSSL.cmake script. The script use a regex to read the
version of OpenSLL inside opensslv.h file. In the last commit, this file
was modified with a formatting tool and the
Rolf Eike Beer wrote:
Guillaume Belz wrote:
Hi,
OpenSSL 1.0.2 was released last week and there is a little change in code,
which impact FindOpenSSL.cmake script. The script use a regex to read the
version of OpenSLL inside opensslv.h file. In the last commit, this file
was
Hi,
OpenSSL 1.0.2 was released last week and there is a little change in code,
which impact FindOpenSSL.cmake script. The script use a regex to read the
version of OpenSLL inside opensslv.h file. In the last commit, this file
was modified with a formatting tool and the line 33 was changed from:
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=15374
==
Reported By:raspy
Assigned To:
The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=15377
==
Reported By:Ongun Kanat
Assigned To:
On 01/27/2015 01:22 PM, Robert Goulet wrote:
If the flag would be wrong, compilation would fail.
What if the flag is not added at all because the property is ignored?
The test needs to be something that would fail without this change.
Thanks,
-Brad
--
Powered by www.kitware.com
Please keep
On 01/19/2015 09:31 AM, Brad King wrote:
Most of the RunCMake tests are for negative tests, but mostly for
running cmake. IIUC you need tests that run cpack, right?
For that you can use run_cmake_command. See use in the
RunCMake.CTestMemcheck test to run ctest:
On 1/27/2015 10:52 AM, Deepak Garg wrote:
I want to build my cmake code with multiple cores (64). For this I am
trying to test the build on 4 cores by typing
make -j 4
But still build is done by a single core. The time taken for build by
make and make -j 4
is same. Can anyone guide me that
Hi all,
When generating VS solution targeting the Windows Store system, it turns out
that ALL projects gets to target Windows Store. In the event that the solution
also contains a project that is a simple Win32 console application that perform
some tasks on files needed by the final Windows
I want to build my cmake code with multiple cores (64). For this I am
trying to test the build on 4 cores by typing
make -j 4
But still build is done by a single core. The time taken for build by
make and make -j 4
is same. Can anyone guide me that what am I doing wrong?
thanks
Deepak
--
On 01/27/2015 04:52 PM, Deepak Garg wrote:
I want to build my cmake code with multiple cores (64). For this I am
trying to test the build on 4 cores by typing
make -j 4
But still build is done by a single core. The time taken for build by
make and make -j 4
is same. Can anyone guide me
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=15375
==
Reported By:raspy
Assigned To:
On 01/27/2015 12:03 PM, Robert Goulet wrote:
CMake uses a global variable that essentially means that the generator
targets a Windows Store app. This makes it difficult to hack it to
control this per project rather than globally.
This is a fundamental limitation of the design of CMake, not
There you go. Let me know if it's good now.
-Original Message-
From: Brad King [mailto:brad.k...@kitware.com]
Sent: Monday, January 26, 2015 3:09 PM
To: Robert Goulet
Cc: cmake-developers@cmake.org
Subject: Re: [cmake-developers] Setting additional compile flags to .hlsl files?
On
On 01/27/2015 12:47 PM, Robert Goulet wrote:
There you go. Let me know if it's good now.
Thanks. I've committed the patch and merged for testing:
VS: Add source file property to set extra hlsl shader flags
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=6b9bd827
In the test I see:
20 matches
Mail list logo
