Am 19.12.2013 16:28, schrieb Brad King:
On 12/11/2013 02:17 AM, Vadim Zhukov wrote:
It took a bit more thinking than I thought initially, sorrt. Anyway,
see the last update to find_backtrace topic. Worked fine for me.
I've rebased the new commit and merged the topic to 'next' for testing:
2013/12/6 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 changed?
It took a bit more
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
On 11/20/2013 04:07 PM, Vadim Zhukov wrote:
I've pushed the version which uses cmake_push_check_state(RESET).
Great, thanks. It is now in master!
-Brad
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep
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
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' for
testing. After the documentation transition I rebased and revised
the topic once to
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' for
testing. After the documentation
On 07/29/2013 12:38 PM, Vadim Zhukov wrote:
2013/7/29 Brad King brad.k...@kitware.com:
Let's complete the add-cmake_reset_check_state topic first and
then you can rebase the find_backtrace topic on it to use the
feature. The former looks good but we'll let it run through the
dashboards
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
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
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 rebase the find_backtrace topic on it to use the
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
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
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
build, and after that, given there will be
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
behavior. The example in the
On Wednesday 03 July 2013, Vadim Zhukov wrote:
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
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 think that appending values have a point by
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 think that appending values have a point by
adding some sort of a flexibility for writers of
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()
will not erase any existing CMAKE_REQUIRED_*
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()
Hello all.
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.
Here is a module I constructed a few months ago. It's helpful for
programs that want to use GNU-style backtrace(3)
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 is a module I constructed a few months ago. It's
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 is a
23 matches
Mail list logo
