Hi Brad,
Am 07.06.2016 19:23 schrieb "Brad King" :
> If it doesn't conflict with 'master' too much I can take it directly.
It should not. I regularly rebase my branch on top of master.
> I've cherry-picked 124f8295bee0c228b79a5cf38f0b2581be308118 and merged
> to 'next'
Hello,
Here is a little patch that lets FindFreetype find the debug library on
Windows, where it is named with a d suffix.
Much thanks to Rolf Eike Beer for help on this.
Cheers,
Stuart
From 93576b26f52017eb9b60705c123be1956a512a77 Mon Sep 17 00:00:00 2001
From: Stuart Mentzer
_VERSION_MINOR 6)
-set(CMake_VERSION_PATCH 20160607)
+set(CMake_VERSION_PATCH 20160608)
#set(CMake_VERSION_RC 1)
---
Summary of changes:
Source/CMakeVersion.cmake |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/
I noticed that FindBZip2.cmake was searching for the bzip2d debug
library but not bz2d (it uses bz2 and bzip2 for the release library
names). While bzip2[d] is the common form on Windows, which is what the
upstream nmake build creates, there are at least two CMake builds for
bzip2 which use
On 07/06/2016 12:10, B00083603 Michael O Brien wrote:
Hi all,
I have to build OpenCV on multiple machines and I was wondering if the
following was possible and advisable or should I use a different method?
I'm still learning about the cmake,make, make install way of software
installation
Hey Andreas,
thanks for your answer. Yes, that also works :)
2016-06-07 16:58 GMT-04:00 Andreas Naumann :
> Hey Kristian,
>
> as the documentation
> https://github.com/Kitware/CMake/blob/master/Modules/FindFreetype.cmake
> at line 21 states, FREETYPE_DIR is an
Hello,
Is there a built-in way to get a ctest -S script to checkout and pull from a
git branch other than 'master'? I can't seem to find a way to so this and
there is no mention of branches at all in the official documentation:
Hey Kristian,
as the documentation
https://github.com/Kitware/CMake/blob/master/Modules/FindFreetype.cmake
at line 21 states, FREETYPE_DIR is an environment variable.
So, if you change your line
set(FREETYPE_DIR "/home/kristian/Documents/freetype/freetype")
to
set(ENV{FREETYPE_DIR}
Am Dienstag, 7. Juni 2016, 16:47:42 schrieb Kristian:
> Hey guys,
>
> I wanted to try something out with CMake and latest version of freetype
> (2.6.3). So I downloaded freetype, compiled it with the commands
>
> > ./configure --prefix=/home/kristian/Documents/freetype/freetype
> > make
> > make
Hey guys,
I wanted to try something out with CMake and latest version of freetype
(2.6.3). So I downloaded freetype, compiled it with the commands
> ./configure --prefix=/home/kristian/Documents/freetype/freetype
> make
> make install
After that, I created a small C++-file and a CMakeLists.txt.
Hey everyone,
I posted a question on StackOverflow a while ago, but got no real answer
to my question there. I posted an answer there by myself, but this
solution does not work on every system. Since it also involves some
possible inconsistencies in the CMake documentation, I decided to ask
the
On 06/07/2016 04:00 PM, Kristian wrote:
> What's the meaning of the bootstrap executable? I thought, when
> compiling CMake, it is sufficient to call ./configure and then make...
The bootstrap script is the way to bootstrap CMake. The `configure`
script is just a thin wrapper around `bootstrap`
What's the meaning of the bootstrap executable? I thought, when compiling
CMake, it is sufficient to call ./configure and then make...
2016-06-07 15:13 GMT-04:00 Brad King :
> On 06/07/2016 10:58 AM, Lowekamp, Bradley (NIH/NLM/LHC) [C] wrote:
> > I tried out 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, master has been updated
via b86585d89a84fb1bdee1e751d0247f30d2315ed0 (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 cd1f0a824e84f4d7f37fb526528e1cfb04d5c250 (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 be12b9ab1246bd1d7a31dc90515f33d8fff455f1 (commit)
via
On 06/07/2016 10:58 AM, Lowekamp, Bradley (NIH/NLM/LHC) [C] wrote:
> I tried out the 3.6.0-rc1 and my problem building CMake still exists.
Thanks for testing it.
> (cd /tmp/cmake-build && \
> ../cmake-3.6.0-rc1/bootstrap && \
> make -j 10 && \
> ./bin/cmake
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 627ad82ba68588053570af6d5926e85a7ae00337 (commit)
via
Hi,
I am working on an IBM Power8 RHEL7.2 system and we installed cmake 3.6
(default cmake from repo was 2.8.12?) but it seems when making a package
the arch is set incorrectly to x86_64 instead of ppc64le.
Anyone have a clue if this cpack on this dist could get its arch wrong ?
cmake 3.5.1 on
On 06/07/2016 12:18 PM, Tobias Hunger wrote:
>> When you have a few such independent refactoring changes done
>> we can look at integrating them immediately to avoid holding
>> them externally in your daemon topic for too long.
>
> Can you take that patch from github or do you want them sent
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 1cc2c0d0f7d9670de22a72d146aba68fadd4fea4 (commit)
via
Hi Brad,
sorry for the empty mail, my phone acted up:-)
Am 07.06.2016 16:48 schrieb "Brad King" :
>
> On 06/07/2016 10:42 AM, Tobias Hunger wrote:
> > On Mo, 2016-06-06 at 13:24 -0400, Brad King wrote:
> >> We should be able to refactor things to share the flags
Hi
Am 07.06.2016 16:48 schrieb "Brad King" :
> On 06/07/2016 10:42 AM, Tobias Hunger wrote:
> > On Mo, 2016-06-06 at 13:24 -0400, Brad King wrote:
> >> We should be able to refactor things to share the flags computation.
> >> Methods like
> >>
> >>
Hello,
I tried out the 3.6.0-rc1 and my problem building CMake still exists.
I created a Dockerfile to reproduce my problem:
===Dockerfile===
ROM debian:8
MAINTAINER Bradley Lowekamp
RUN apt-get update && apt-get install -y \
build-essential \
curl \
On 06/07/2016 10:42 AM, Tobias Hunger wrote:
> On Mo, 2016-06-06 at 13:24 -0400, Brad King wrote:
>> We should be able to refactor things to share the flags computation.
>> Methods like
>>
>> cmLocalGenerator::GetTargetFlags
>
> Does this patch here make sense:
>
>
On Mo, 2016-06-06 at 13:24 -0400, Brad King wrote:
> We should be able to refactor things to share the flags computation.
> Methods like
>
> cmLocalGenerator::GetTargetFlags
Does this patch here make sense:
https://github.com/hunger/CMake/commit/124f8295bee0c228b79a5cf38f0b2581be308118
It
Thanks Brad. I haven't run into a mac without
/System/Library/Frameworks/Kernel.framework before but maybe it comes from
XCode or something. Thanks for merging.
Harry.
Harry Mallon
CODEX | Software Engineer
60 Poland Street | London | England | W1F 7NT
E ha...@codexdigital.com | T +44 203 7000
The following issue has been SUBMITTED.
==
https://public.kitware.com/Bug/view.php?id=16137
==
Reported By:Andry81
Assigned To:
On 06/07/2016 02:07 AM, michael.jaent...@gmx.de wrote:
> problem is not the POST_BUILD which is set to "cd ." as you said but the
> CMAKE_CXX_ARCHIVE_FINISH which is before the POST_BUILD
[snip]
> command = ... D:\gcc\win32\mips-sde-elf\bin\mips-sde-elf-ar.exe qc
> $TARGET_FILE $LINK_FLAGS $in
On 06/07/2016 09:07 AM, Tobias Hunger wrote:
>> We should be able to refactor things to share the flags computation.
>> Methods like
>>
>> cmLocalGenerator::GetTargetFlags
>> cmLocalGenerator::GetIncludeDirectories
>>
>> are meant to be used across multiple generators.
>
> So is that the
On 06/07/2016 07:29 AM, Harry Mallon wrote:
> I have updated my patch with new simplified logic and a test.
Thanks. I revised the test to not depend on a specific framework
path to exist on the system (it didn't on mine). Merged to 'next'
for testing:
find_path: Fix location of in a
On 06/07/2016 05:27 AM, Daniel Pfeifer wrote:
> If we have a daemon mode that provides this information (as your
> implementation already does), we could let ccmake and cmake-gui use
> the daemon instead of linking against CMakeLib.
That would be really nice. A lot of the state space in CMake's
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 ec9b42e9e29c11f41f13f70ded93debc61eafcb0 (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 15ecac966da9656101847cf8cc213e0ff2fa3691 (commit)
via
Hi Brad!
On Mon, Jun 6, 2016 at 7:24 PM, Brad King wrote:
>> A big chunk of Stephen's work has not even landed in my branch yet. Since
>> cmake
>> reformated all the source in the meantime it is a bit tedious to apply
>> patches
>> from his tree and I have simply not
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 f6ae3ecd3763d255c91f3831ecaabd9f8d86eef9 (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 9095b13b1caa941bf0109f62ceab07495aff37cd (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 7f2a735a10a3180a6614ce10d3705e521421bb22 (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 9b15a15fe96f099ac9a277c9d3722b9c1e4b6ff5 (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 633d99dc6255901c2fbc9f7c80a1d24f357a4024 (commit)
via
Hi all,
I have to build OpenCV on multiple machines and I was wondering if the
following was possible and advisable or should I use a different method? I'm
still learning about the cmake,make, make install way of software installation
Environment
All the machines (vms) have access to the
I have updated my patch with new simplified logic and a test.
Harry Mallon
CODEX | Software Engineer
60 Poland Street | London | England | W1F 7NT
E ha...@codexdigital.com | T +44 203 7000 989
0001-Fix-a-problem-where-using-find_path-to-find-a-header.patch
Description:
For some reason I was looking for it in the cmake modules, where
"CHECK_CXX_SOURCE_RUNS" was..
Thanx!
On Tue, Jun 7, 2016 at 10:23 AM, Petr Kmoch wrote:
> Hi Yaron,
>
> I believe you're looking for CMake's try_run() command:
>
Hi Daniel,
On Tue, Jun 7, 2016 at 11:27 AM, Daniel Pfeifer wrote:
> On Mon, Jun 6, 2016 at 5:39 PM, Tobias Hunger wrote:
>> Please help to support your use-cases.
>
> A while ago I wrote a graphical cache editor in GTK:
>
On Mon, Jun 6, 2016 at 7:24 PM, Brad King wrote:
> On 06/06/2016 11:39 AM, Tobias Hunger wrote:
>
>> A big chunk of Stephen's work has not even landed in my branch yet. Since
>> cmake
>> reformated all the source in the meantime it is a bit tedious to apply
>> patches
>>
On Mon, Jun 6, 2016 at 5:39 PM, Tobias Hunger wrote:
> Please help to support your use-cases.
A while ago I wrote a graphical cache editor in GTK:
https://github.com/purpleKarrot/cmake-gtk
The tool reads the cache and provides a graphical view to modify it.
It can then write
Hi Yaron,
I believe you're looking for CMake's try_run() command:
https://cmake.org/cmake/help/latest/command/try_run.html
Petr
On 7 June 2016 at 09:15, Yaron Cohen-Tal wrote:
> Hi,
>
> I'd like to build a C++ program and get its output during "cmake" run, not
> during the
Hi,
I'd like to build a C++ program and get its output during "cmake" run, not
during the project build. "CHECK_CXX_SOURCE_RUNS" only gives me the exit
code, but I need the output from the program. Anyway to do it?
Thanx,
Yaron
--
Powered by www.kitware.com
Please keep messages on-topic and
48 matches
Mail list logo