Re: [cmake-developers] New no-soname-option topic for e.g. Android

2014-05-29 Thread Vadim Zhukov
28.05.2014 20:17 пользователь Nils Gladitz nilsglad...@gmail.com написал: On 28.05.2014 18:01, Vadim Zhukov wrote: I assumed that because people kept removing the soname options for their Android toolchains that SONAMEs aren't supported at all. It however looks like they just can't

Re: [cmake-developers] New no-soname-option topic for e.g. Android

2014-05-28 Thread Vadim Zhukov
28.05.2014 18:57 пользователь Nils Gladitz nilsglad...@gmail.com написал: On 28.05.2014 16:14, Ben Boeckel wrote: On Wed, May 28, 2014 at 10:39:22 +0200, Nils Gladitz wrote: As discussed here http://www.cmake.org/pipermail/cmake/2014-May/057657.html I proposed a minor modification in CMake

Re: [cmake-developers] FindBacktrace.cmake is slightly too chatty

2013-12-10 Thread Vadim Zhukov
thinking than I thought initially, sorrt. Anyway, see the last update to find_backtrace topic. Worked fine for me. -- WBR, Vadim Zhukov -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic

Re: [cmake-developers] FindBacktrace.cmake is slightly too chatty

2013-12-05 Thread Vadim Zhukov
06.12.2013 1:19 пользователь Rolf Eike Beer e...@sf-mail.de написал: Hi, I noticed that the message backtrace facility detected in default set of libraries appears every time CMake is run, and not just when the library is searched for, which is not what the modules usually do. Can this be

Re: [cmake-developers] FindBacktrace.cmake

2013-11-20 Thread Vadim Zhukov
2013/11/19 Vadim Zhukov persg...@gmail.com: 2013/11/19 Brad King brad.k...@kitware.com: On 07/31/2013 10:06 AM, Brad King wrote: The dependency is now in master so please rebase find_backtrace on that so you can use the reset feature. The find_backtrace topic has not yet been merged to 'next

[Cmake-commits] CMake branch, next, updated. v2.8.12.1-5518-gad057a1

2013-11-20 Thread Vadim Zhukov
- http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=ad057a104e2340e50cb08b95e8afbb92592bd112 commit ad057a104e2340e50cb08b95e8afbb92592bd112 Merge: 534ca7e c6f339c Author: Vadim Zhukov persg...@gmail.com AuthorDate: Wed Nov 20 16:01:27 2013 -0500 Commit: CMake Topic Stage kwro

Re: [cmake-developers] FindBacktrace.cmake

2013-11-19 Thread Vadim Zhukov
. -- WBR, Vadim Zhukov -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http

Re: [cmake-developers] FindBacktrace.cmake

2013-07-29 Thread Vadim Zhukov
2013/7/29 Alexander Neundorf neund...@kde.org: Hi Vadim, On Sunday 28 July 2013, you wrote: 2013/7/23 Alexander Neundorf neund...@kde.org: On Tuesday 09 July 2013, Brad King wrote: On 07/08/2013 05:51 PM, Vadim Zhukov wrote: I'm not sure whether resetting CMAKE_REQUIRED_* is the desired

Re: [cmake-developers] FindBacktrace.cmake

2013-07-29 Thread Vadim Zhukov
2013/7/28 Rolf Eike Beer e...@sf-mail.de: On Sun Jul 28 15:46:27 2013 Vadim Zhukov persg...@gmail.com wrote: With all input from you and after setting up local development repo, I created and pushed two branches to stage: If I understand correctly, there should be zero fallout in the night

Re: [cmake-developers] FindBacktrace.cmake

2013-07-29 Thread Vadim Zhukov
2013/7/29 Brad King brad.k...@kitware.com: On 07/29/2013 04:59 AM, Vadim Zhukov wrote: Thank you, Alexander. I've fixed both points you've mentioned and merged the add-cmake_reset_check_state branch into the next. Let's complete the add-cmake_reset_check_state topic first and then you can

[Cmake-commits] CMake branch, next, updated. v2.8.11.2-3456-g1222f93

2013-07-29 Thread Vadim Zhukov
, below. - Log - http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=1222f937e14b2a6087bf95e7a7b6e7c008ee7fdb commit 1222f937e14b2a6087bf95e7a7b6e7c008ee7fdb Merge: e56389d 3a1c57c Author: Vadim Zhukov persg...@gmail.com AuthorDate: Mon

Re: [cmake-developers] FindBacktrace.cmake

2013-07-28 Thread Vadim Zhukov
2013/7/23 Alexander Neundorf neund...@kde.org: On Tuesday 09 July 2013, Brad King wrote: On 07/08/2013 05:51 PM, Vadim Zhukov wrote: I'm not sure whether resetting CMAKE_REQUIRED_* is the desired behavior. The example in the CMakePushCheckState.cmake documentation tells the opposite, and I

Re: [cmake-developers] FindBacktrace.cmake

2013-07-08 Thread Vadim Zhukov
2013/7/8 Brad King brad.k...@kitware.com: On 7/3/2013 5:10 PM, Vadim Zhukov wrote: 2. Just make sure BACKTRACE_LIBRARIES is empty: if the developer wants to shoot himself in the foot with -nostdlib, then he's responsible Yes, I agree with this approach. However, cmake_push_check_state

[cmake-developers] FindBacktrace.cmake

2013-07-03 Thread Vadim Zhukov
! for CMake itself and attach the module itself. -- WBR, Vadim Zhukov FindBacktrace.cmake Description: Binary data -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ

Re: [cmake-developers] FindBacktrace.cmake

2013-07-03 Thread Vadim Zhukov
2013/7/3 Brad King brad.k...@kitware.com: On 7/3/2013 11:09 AM, Vadim Zhukov wrote: I'm an OpenBSD developer, working mostly on porting software. Most of my work is related to CMake-based land, including modern KDE and some other Qt4-based stuff. Great, thanks for coming to us. Here