_VERSION_MINOR 8)
-set(CMake_VERSION_PATCH 20170228)
+set(CMake_VERSION_PATCH 20170301)
#set(CMake_VERSION_RC 1)
---
Summary of changes:
Source/CMakeVersion.cmake |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/
On 02/28/2017 03:38 PM, Rolf Eike Beer wrote:
>> +/usr/local/libx32
>> /usr/local/lib64
>> /usr/local/lib
>> +/usr/libx32
>> /usr/lib64
>> /usr/lib
>> /usr/X11R6/include
> And so on…
>
> Shouldn't we think of
> + PATH_SUFFIXES libx32 lib64 lib lib32
> + PATH_SUFFIXES lib64 libx32)
> +/usr/local/libx32
> /usr/local/lib64
> /usr/local/lib
> +/usr/libx32
> /usr/lib64
> /usr/lib
> /usr/X11R6/include
> +
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 0412b809f4d426ad1826c10e7f4b2d172906b0ee (commit)
via
On 02/28/2017 08:22 AM, Brad King wrote:
>> 2) Make sure, in case lib32 is a symlink, to follow the symlink.
>
> I was thinking the same thing. The lib => lib32 search path conversion
> should just be skipped if lib32 is a symlink back to lib.
For reference, I opened an issue for this part of
On 02/27/2017 08:50 AM, Steven Newbury wrote:
>> we now use gitlab.kitware.com merge requests.
>
> Right, I'll do that.
For reference, the MR is [1].
Thanks,
-Brad
[1] https://gitlab.kitware.com/cmake/cmake/merge_requests/532
--
Powered by www.kitware.com
Please keep messages on-topic and
On 02/27/2017 08:36 AM, Brad King wrote:
> we now use gitlab.kitware.com merge requests.
For reference, the MR is [1].
Thanks,
-Brad
[1] https://gitlab.kitware.com/cmake/cmake/merge_requests/533
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
On Tue, 2017-02-28 at 08:22 -0500, Brad King wrote:
> On 02/28/2017 05:25 AM, Jörg Krause wrote:
> > Buildroot does not have any problems with searching for libraries
> > in
> > lib32. It does have a problem with having a host rpath used for
> > linking
> > with libraries.
>
> From your
Dear cmakers,
I just found a rather disturbing fact on my Mac which leads to entire Xcode
projects and everything stored next to them to be excluded from the Time
Machine backup:
➜ ~ cmake --version
cmake version 3.7.2
CMake suite maintained and supported by Kitware (kitware.com/cmake).
➜ ~
Hi,
Is there a way to declare a target property to be transitive and accumulate
into a list? Similar to how COMPILE_DEFINITIONS works, but for custom
properties? I know about COMPATIBLE_INTERFACE_STRING etc, which create a
transitive property, but the values don't accumulate into a list.
As a
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 29c967ef21bf0248e965cac171cfa2fb51fbaf1c (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 f9ea9e5b5716a3b37799af673375bb41d5cb5816 (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, release has been updated
via 220b799c8a7ff6039254c90bbeba1890d816b523 (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 63f5ddc0f7c158543113352593ba6999c675814c (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 78104bd7bca4bd9b4b7a5c17622838a33843138e (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 13e34019b22fb5930919401599c4623d2c65508c (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 2ca029d9a896433c6b8681930ee0bd8d87a21122 (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 2a8c67ccc306ab592098adb218610d2b39062633 (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 30243e7fafee60a8ef6ffc6fb8eed09548a86aa9 (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 0aec4d38642570cc38440b5368fec4de02e09a6a (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 183836811c2ae8bce19dab4f77f1afecf84fbef0 (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 9780a18290b8763870a57a315cdaad1a8b5a02a6 (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 6a8da1d7773ac3d50a450b1043f453406528ae29 (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 6403cda149e5213608b8f4889676c1e69aaf498a (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 09a81e29fee15bb6781d66769497fa320765fed9 (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 fd6b260c40509e1ab8a6b548e47634388b84d56b (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 c3c0a0a531937b5b897e8ebaf7c296038304 (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 7d1a84228d336288da78fc0efac3a94e651fbdd0 (commit)
via
On 02/27/2017 08:11 PM, Ray Donnelly wrote:
>> CMake passes the host rpath to the linker
>
> CMake does this because it isn't *asking* the linker, it's making
> assumptions instead (and adding some predefined values like
> `/usr/lib32`). If we just ask the linker instead then everything
> should
On 02/28/2017 05:25 AM, Jörg Krause wrote:
> Buildroot does not have any problems with searching for libraries in
> lib32. It does have a problem with having a host rpath used for linking
> with libraries.
From your description we are not adding a host rpath. It's coming from
/sysroot/usr/lib32
On Mon, 2017-02-27 at 16:33 -0500, Brad King wrote:
> On 02/27/2017 03:50 PM, Jörg Krause wrote:
> > The problem is...
>
> Thanks. I've opened an issue for this here:
>
> https://gitlab.kitware.com/cmake/cmake/issues/16682
Great!
> > > These are set on by default in
31 matches
Mail list logo
