- Forwarded message from Ben Cooksley bcooks...@kde.org -
Date: Sun, 26 Oct 2014 11:50:45 +1300
From: Ben Cooksley bcooks...@kde.org
To: Ben Boeckel ben.boec...@kitware.com
Subject: Re: [bcooks...@kde.org: Re: [cmake-developers] Fwd: Re: Severe
behavioural change regressions in
On 10/24/2014 09:21 AM, Pascal Bach wrote:
---
Tests/CMakeLists.txt | 46 +-
1 file changed, 45 insertions(+), 1 deletion(-)
Thanks, applied:
Tests: Run Tutorial steps 1-4 as tests for Windows CE
On 10/24/2014 05:46 PM, Evgeny Kalishenko wrote:
Documentation added, authorship fixed, a couple of commits squashed.
Great. Applied and merged for testing:
CPackRPM: Support pre(post) install scripts
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=7d049e7c
CPackRPM: Support PREUN and
On 10/14/2014 12:48 PM, Geoffrey Viola wrote:
Green Hills MULTI is an IDE for embedded real-time systems.
http://www.ghs.com/products/MULTI_IDE.html.
http://www.ghs.com/products/rtos/integrity.html.
Thanks for the explanation.
I took a look at CMAKE_OSX_SYSROOT. It is similar to GHS_OS_DIR.
Am 27.10.2014 14:27, schrieb Brad King:
On 10/24/2014 05:46 PM, Evgeny Kalishenko wrote:
Documentation added, authorship fixed, a couple of commits squashed.
Great. Applied and merged for testing:
CPackRPM: Support pre(post) install scripts
On 10/27/2014 10:41 AM, Rolf Eike Beer wrote:
if(${_RPM_SPEC_HEADER} MATCHES REQUIRES_PRE OR
${_RPM_SPEC_HEADER} MATCHES REQUIRES_POST)
This should really be using STREQUAL and not using dereferences on the
left hand side.
Thanks. Actually I mentioned that in my first review in this
The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=15220
==
Reported By:Anton Indrawan
Assigned To:
Little correction: the first comment CPackRPM: Support pre(post) install
scripts differs from mine Requires for pre(post) install scripts are
implemented and can cause misunderstanding. Because pre(post) install
scripts are already implemented.
2014-10-27 17:55 GMT+03:00 Brad King
On 10/27/2014 12:22 PM, Evgeny Kalishenko wrote:
Little correction:
Revised:
CPackRPM: Support pre(post) install script requirements
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=add4e50d
CPackRPM: Support PREUN and POSTUN requirements
Am Montag, 27. Oktober 2014, 10:55:50 schrieb Brad King:
On 10/27/2014 10:41 AM, Rolf Eike Beer wrote:
if(${_RPM_SPEC_HEADER} MATCHES REQUIRES_PRE OR
${_RPM_SPEC_HEADER} MATCHES REQUIRES_POST)
This should really be using STREQUAL and not using dereferences on the
left hand side.
Trying to bring a bit more attention to this:
Fedora is pushing to have higher resolution icons for the applications. There
already is CMakeSetup128.png, but these would need to get installed into the
proper /usr/share/icons/ hierarchy and named appropriately for the correct
size to be
On Mon, Oct 27, 2014 at 11:59:09 -0600, Orion Poplawski wrote:
Trying to bring a bit more attention to this:
Fedora is pushing to have higher resolution icons for the applications. There
already is CMakeSetup128.png, but these would need to get installed into the
proper /usr/share/icons/
On Sat, Oct 25, 2014 at 7:14 PM, Stephen Kelly steve...@gmail.com wrote:
Ben Cooksley wrote:
On Sat, Oct 25, 2014 at 5:44 AM, Stephen Kelly steve...@gmail.com wrote:
Is build.kde.org now using the release branch of cmake.git instead of the
next branch? When/why did that change?
This was
On Tue, Oct 28, 2014 at 09:58:58 +1300, Ben Cooksley wrote:
If anyone is interested, help would be appreciated to get a Contracts
style build up and running.
In particular, pointers to documentation on how to perform such builds
would be appreciated - we'll need to run make install for parts
The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=15221
==
Reported By:Ilya
Assigned To:
On 10/24/2014 04:29 PM, Bill Somerville wrote:
Sorry, I am struggling with this. I have copied the
Darwin-GNU-Fortran.cmake file into my project modules directory and
patched it as you suggested.
Sorry, I meant the Modules directory of your CMake installation.
The good news is that it
On 27/10/2014 13:17, Brad King wrote:
Hi Brad,
On 10/24/2014 04:29 PM, Bill Somerville wrote:
Sorry, I am struggling with this. I have copied the
Darwin-GNU-Fortran.cmake file into my project modules directory and
patched it as you suggested.
Sorry, I meant the Modules directory of your CMake
A summary of limitations with (mostly) armcc and Cmake, primarly using Ninja
generator.
(Note that this is referring to two emails and add a new problem.)
The workarounds where applicable are listed, as well as possible
corrections/enhancements in CMake. I will probably open issues later, maybe
The warning message for CMP0020 seems to be completely random as to where you
actually have to set the policy.
Im not getting the warning on my main executables, but cant seem to get rid of
it on any of my Qt based unittests (using gmock/gtest )
I have the following line, in various places in
Hello,
--8---
FOSDEM http://www.fosdem.org is one of the largest gatherings of Free
Software contributors in the world and happens each February in Brussels
(Belgium). One of the tracks will be the Desktops DevRoom (formerly known
as “CrossDesktop DevRoom”), which will host Desktop-related
I know that when defining link libraries, I can do this:
$$CONFIG:Debug:${my_debug_libs}
The debug libraries will be the same for all debug targets. Likewise
with Release targets. Is there a way to refer to *all* release targets
using generator expressions? There are 3 release configurations
I forgot to give a more concrete example. Consider this:
add_library( Foo INTERFACE )
target_link_libraries( Foo INTERFACE
$$CONFIG:Debug:${lib_debug}
$$CONFIG:Release:${lib_release}
$$CONFIG:RelWithDebInfo:${lib_release}
$$CONFIG:MinSizeRel:${lib_release}
I think this should work:
$$NOT:$CONFIG:Debug:${my_release_libs}
--
Daniel
-Original Message-
From: CMake [mailto:cmake-boun...@cmake.org] On Behalf Of Robert Dailey
Sent: Monday, October 27, 2014 5:12 PM
To: CMake
Subject: Re: [CMake] Refer to all debug or release targets with
Hello,
I'm trying to create a simple exercise, a definition for a virtual language
X that will be used side-by-side with C and C++.
There are some restrictions on the level of compatibility with C/C++. For
instance, the objects of this language aren't directly compatible with C
and C++ but then
This actually used to be a very difficult problem to solve. However,
to debug in visual studio it's essential.
If I have DLLs located in third party directories OR from targets that
I depend on, those must all be copied to the directory of the
executable I'm debugging in order for those DLLs to
That's a cute solution. Never thought of it. Generator expressions are
really advanced handy now. I like it.
On Mon, Oct 27, 2014 at 7:14 PM, Daniel Schepler
dschep...@scalable-networks.com wrote:
I think this should work:
$$NOT:$CONFIG:Debug:${my_release_libs}
--
Daniel
-Original
If you add install rules, you can get a runnable package... and kill having
to configure things to package in one step.
Install can just target 'output' or some relative directory to the build
directory, it doesn't have to be the final install target.
On Mon, Oct 27, 2014 at 6:55 PM, Robert
I use a copy rule for the DLLs during the build which finds the DLL and then
copies it to the Debug or Release directory. You are welcome to the macro that
we use for our project. If there is an easier way with Cmake 3.0.x I would love
to hear about it.
Thanks
Mike Jackson
On Oct 27, 2014,
how does that work with say openwatcom?
On Mon, Oct 27, 2014 at 7:51 PM, Michael Jackson
mike.jack...@bluequartz.net wrote:
I use a copy rule for the DLLs during the build which finds the DLL and
then copies it to the Debug or Release directory. You are welcome to the
macro that we use for
Well basically, if you are on windows cmake can find the .lib file but then I
wrote some code for each 3rd party library that attempts to find the .dll
files. Once those files are found I create the copy files targets for each DLL.
Mike Jackson
On Oct 27, 2014, at 11:17 PM, J Decker
And if not, is there any information on how an outside developer might
begin work on a custom generator? I'm just a student, so I'm not sure how
much time I have to dedicate to something like this, but I am interested in
seeing what's involved.
Link to FASTBuild:
Hi,
you can use generator expression in a post build rule to copy the dll file to
the same target dir as the target you link it with. The easiest way to do this
is to properly define all 3rd party libraries as imported targets that contains
both, the lib and the dll file.
Sadly, the FindQt4 on
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 8eb64831bec333914aab3af54e2d1deded02eb90 (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 badb5d34778e640d6f7996b19e1c47c9e6055108 (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 c5e72de1949ded9954b456f1e3cf12f95c289b9b (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 407bc1c646eba9dc40c9d0d95b38602593f210d2 (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 0c3ddf8b652311ec2a9447a9e6303691841628b4 (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 0f068c177c3834aacc1b27e32c318b53adad06f9 (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 a1273a981c8b1e32a0c7180ca3c23e47f615ad91 (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 a02f7296791f3f46a096c8409201c0b6c82461f2 (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 a7caa9c513fdbdbd4e81be70fce765bd2a6e64a5 (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 90f5ad573761bd65962d71d34d31a1beb754b7af (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 3ecf8efd0fde7480d0eaba58feab133478574371 (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 4a8b6430d970256653729a695b74f73cc2434fde (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 70f065d1cbaff76b4e55b4fc6f778cc7d0b37775 (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 e562910dcba4de9de3fe5138d19609092917c881 (commit)
via
20141027)
+set(CMake_VERSION_PATCH 20141028)
#set(CMake_VERSION_RC 1)
---
Summary of changes:
Source/CMakeVersion.cmake |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/post-receive
--
CMake
47 matches
Mail list logo
