_VERSION_MINOR 5)
-set(CMake_VERSION_PATCH 20160509)
+set(CMake_VERSION_PATCH 20160510)
#set(CMake_VERSION_RC 1)
---
Summary of changes:
Source/CMakeVersion.cmake |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/
Version 7.3.1 (7D1014)
On Mon, May 9, 2016 at 10:03 PM, Gregor Jasny wrote:
> On 02/05/16 11:16, Siyuan Ren wrote:
>> I have CMake 3.5.2.
>>
>> I write a simple CMakeLists.txt like the below
>>
>> ```
>> project(mytest)
>> add_executable(mytest test.cpp)
>> ```
>>
>> Then
CMake version 3.5.0
When exporting from a project, the PROJECTTargets.cmake file contains logic
for computing the _IMPORT_PREFIX. This _IMPORT_PREFIX is then used in the
PROJECTTargets-.cmake to generate
the IMPORTED_LOCATION_. If _IMPORT_PREFIX is "/",
then the IMPORTED_LOCATION_ properties all
On Mon, 2016-05-09 at 14:17 -0400, Brad King wrote:
> > What is the rationale for "ColumnLimit: 79"? To make a line fit on old
> > school terminals, 80 should be OK. To make a diff or an email response
> > fit on old school terminals, two extra spaces are reserved. That leads
> > to a column limit
On Thu, Apr 28, 2016 at 2:21 PM, Burlen Loring wrote:
> Hi Guys,
>
> I'd like to discuss changing the defaults of CMAKE_C/CXX_FLAGS_RELEASE on
> gcc, and potentially gcc like compilers such as clang and intel.
>
> Currently the default is "-O3 -DNDEBUG". I would like to
On 2016-05-09 17:11+0200 Konrad Kleine wrote:
Hi,
I'm trying to verify the integrity of a CMake release using GPG. I'm
getting the error, that there's a BAD signature from "Brad King". Now I
wonder what could be the reason for this issue.
[...]
# Verify the integrity of the downloaded cmake
On 05/09/2016 01:48 PM, Daniel Pfeifer wrote:
> "AllowShortFunctionsOnASingleLine: Inline" is default in the Mozilla
> preset. This line can be removed.
Yes, thanks.
> What is your rationale for "IndentCaseLabels: false"? I find that
> indenting them increases readability when switch statements
On Mon, May 9, 2016 at 11:14 AM, Brad King wrote:
> On 05/02/2016 10:08 AM, Brad King wrote:
>> Next I'll look at the style updates themselves.
>
> I've made some more preparatory commits:
>
> Isolate formatted streaming blocks with clang-format off/on
>
On Mon, May 9, 2016 at 11:31 AM, Rolf Eike Beer wrote:
> Am Montag, 9. Mai 2016, 13:14:17 schrieb Brad King:
>> On 05/02/2016 10:08 AM, Brad King wrote:
>> > Next I'll look at the style updates themselves.
>>
>> I've made some more preparatory commits:
>
> […]
>> Remove
Am Montag, 9. Mai 2016, 13:14:17 schrieb Brad King:
> On 05/02/2016 10:08 AM, Brad King wrote:
> > Next I'll look at the style updates themselves.
>
> I've made some more preparatory commits:
[…]
> Remove `//--...` horizontal separator comments
>
On 05/02/2016 10:08 AM, Brad King wrote:
> Next I'll look at the style updates themselves.
I've made some more preparatory commits:
Isolate formatted streaming blocks with clang-format off/on
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=64b55203
Move comments off of class access
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 3880c440e0a73b5b9898343bf17886ddfc50bd26 (commit)
via
On 05/09/2016 11:11 AM, Konrad Kleine wrote:
> ADD https://cmake.org/files/v3.5/cmake-3.5.2-Linux-x86_64.tar.gz /tmp
> ADD https://cmake.org/files/v3.5/cmake-3.5.2-SHA-256.txt /tmp
> ADD https://cmake.org/files/v3.5/cmake-3.5.2-SHA-256.txt.asc /tmp
[snip]
> # Verify the integrity
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, master has been updated
via 3ecdddfc35a0f0ecc1495d902f34d9cee2d59459 (commit)
via
Hi,
I'm trying to verify the integrity of a CMake release using GPG. I'm
getting the error, that there's a BAD signature from "Brad King". Now I
wonder what could be the reason for this issue.
To make it easily reproducible, here's my Dockerfile, describing the
process for you to test it
I think that changing the Release mode to generate non portable code
is very nasty side-effect that would bite numerous projects down the
road. I think a better avenue would be to think about adding another
build configuration called ReleaseNative which would produce highly
optimized non portable
Hi list,
In my project I have to build things in two stages (different compilers
and different flags between the two stages). Both are built with CMake.
I'm looking for a way of how to correctly include the generated
products from one project (libraries in my case) in the other
project's build.
The following issue has been SUBMITTED.
==
https://cmake.org/Bug/view.php?id=16097
==
Reported By:Nils Gladitz
Assigned To:
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 d1ea20a5782ac72f5d4616360d73e51cf3958dd2 (commit)
via
On 02/05/16 11:16, Siyuan Ren wrote:
> I have CMake 3.5.2.
>
> I write a simple CMakeLists.txt like the below
>
> ```
> project(mytest)
> add_executable(mytest test.cpp)
> ```
>
> Then generate the Xcode project file with `cmake -G Xcode .`. Open the
> project file in Xcode, and I found the
On 05/06/2016 09:02 AM, ivan Ivanov wrote:
> Fix for https://cmake.org/Bug/view.php?id=15756
Thanks for working on this.
Please split the patch to first perform refactoring like moving
the version extraction into a helper function. Then the actual
logic change will be easier to see in the
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 20913edb0538920f0bc0c5f48d0f034564ab7fb8 (commit)
via
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 0972a1d937fa89ab3ae7a7ef93165ccf66feef5a (commit)
via
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, master has been updated
via d95fbdb70944a8f9a7e6ac11bc51f410a99aafcd (commit)
via
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, master has been updated
via 7ecd9648a166ecf500badfd0c4eab77a15101c35 (commit)
via
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, master has been updated
via 138ddfae509d55ee260c57caee7684e08678d20f (commit)
via
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 0e106879e83239d7eaa997d2bc85d31851a94e6c (commit)
via
On Sun, May 8, 2016 at 11:20 PM, Craig Scott wrote:
> Add the MACOSX_BUNDLE keyword to your add_executable() command. See the
> CMake docs for details.
Thanks, it works.
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
28 matches
Mail list logo