Well, after installing the Update 4 to VS 2013 yesterday, and letting
the dashboards run their usual course overnight ... the WinStorePhone
tests seem to work just fine now.
So: must be some difference in VS 2013 out of the box and Update 4
that was to blame. I'm perfectly ok with saying you
Hello.
Trying to build kde frameworks and got weird problem, when building kauth
which uses kcoreaddons :
CMake Error in src/CMakeLists.txt:
Imported target KF5::CoreAddons includes non-existent path
/include/KF5/KCoreAddons
in its INTERFACE_INCLUDE_DIRECTORIES. Possible reasons
On 11/18/2014 04:10 PM, Alin Marin Elena wrote:
the original bug/feature was introduced by this
https://www.cmake.org/Bug/view.php?id=14656history=1
@Brad: Could this be fixed in time for 3.1?
Nils
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
On 11/20/2014 8:28 AM, Nils Gladitz wrote:
On 11/18/2014 04:10 PM, Alin Marin Elena wrote:
the original bug/feature was introduced by this
https://www.cmake.org/Bug/view.php?id=14656history=1
@Brad: Could this be fixed in time for 3.1?
Yes, since it is a regression.
On 11/18/2014 10:10 AM,
On 11/20/2014 02:32 PM, Brad King wrote:
On 11/18/2014 10:10 AM, Alin Marin Elena wrote:
2. the fortran test in FindOpenMP.cmake shall be provided in fixed
form (add 6 empty spaces in front of the character of each line)
Please use this approach in a topic based of origin/release.
Thanks,
On 11/19/2014 4:26 AM, Fraser Hutchison wrote:
I've attached an updated patch
Thanks. Applied here:
Avoid if() quoted auto-dereference when checking for MSVC
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=4d52cd36
and backported for the 'release' branch here:
Avoid if() quoted
On 11/20/2014 8:57 AM, Nils Gladitz wrote:
Thanks, done.
@Alin I hope you don't mind that I took the liberty :)
Alin, the commit is here:
FindOpenMP: Use fixed form Fortran test program
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=7d633ebf
Please try it out so we know it fixes your
On 20/11/2014 13:59, Brad King wrote:
The latter will be merged to 'release' for 3.1.0-rc3.
Thanks very much.
Fraser.
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the
Arkadiusz Miśkiewicz wrote:
Hello.
Trying to build kde frameworks and got weird problem, when building kauth
which uses kcoreaddons :
Can you put all of this into a bug report please?
http://public.kitware.com/Bug/bug_report_page.php
Remember: paste the important info, not pastebin
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=15258
==
Reported By:Arkadiusz Miskiewicz
Assigned To:
Hello,
I would like to add support for INtime (v6) platform (RTOS for Windows).
I add these variables to my CMakeLists.txt project:
SET(CMAKE_SYSTEM_NAME INtime)
SET(CMAKE_GENERATOR_PLATFORM INtime)
I generated a platform/INtime.cmake file (attach to this email).
When trying to
On Wed, 2014-11-19 at 22:55 +, Braden McDaniel wrote:
The documentation for the source property COMPILE_FLAGS describes it
as, Additional flags to be added when compiling this source file.
However, when using the Visual Studio 2013 generator (at least), it appears
to replace (rather
CMAKE_CXX_KNOWN_FEATURES seems to be empty in
cmake 3.1.0-rc2
Should it be?
cheers,
Erik Sjölund
erik@ubuntu:~/tmp$ cat CMakeLists.txt
cmake_minimum_required(VERSION 3.1.0 FATAL_ERROR)
project(foobar CXX)
list(LENGTH CMAKE_CXX_KNOWN_FEATURES length1)
message(length of
On 11/20/2014 12:32 AM, Andrew Maclean wrote:
I only picked this up because I use the Microsoft Visual Studio Version
Selector to open the *.sln file by default.
Tested on CMake 3.0.2 and the pre-release version CMake 3.1.20141119
VS 2013 Community Edition will happily use the VS Express 2013
Mark,
I also have had a lot of difficulty using cmake in the Cray computing
environment (Cray XE6). My team has given up on autodetection of the build
environment. Instead we use cmake in a cross compiling environment
(http://www.cmake.org/Wiki/CMake_Cross_Compiling), where we manually
Erik Sjölund wrote:
CMAKE_CXX_KNOWN_FEATURES seems to be empty in
cmake 3.1.0-rc2
Should it be?
Yes, it's not a variable, but a global property:
get_property(cxx_features GLOBAL PROPERTY CMAKE_CXX_KNOWN_FEATURES)
message(known: ${cxx_features})
Thanks,
Steve.
--
Powered by
I have a shared library. To build it as framework i write:
set_target_properties(lib_name FRAMEWORK TRUE)
How I build it as bundle? Please dont confuse library bundle with
application bundle.
Regards, Alexey
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ
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 e4db3f81ebd5cb54241849b602395106f674864b (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 7e2bff62b95c28721f8d5a558a16f91bfac86ab1 (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 3749ad49e3251dad7b392317a50ef3b1194ee63b (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 3a20cef3d71ab55c77aa85b05217e13afabb35b4 (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 56993e7ab8fd7739bb4d5a57d5118f586a280f46 (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 3a78c6d134e1abd1f456dd8802f6d9de3cf72199 (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 6b8513cc23433ca3037560b525206aa719aa8ce0 (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 eeb0de0af58f287c5c03a2a2655bdc2af404feb5 (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 d8e425c37bb9c0a3b3bba8651eedc3646c421067 (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 7ca9ac40d619d48792f5c2cc35c4c2ca6dd5fef4 (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 5c5d83c996d5cbbee6d57b1b09f41a24f7e809b8 (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 dbf41e4b9e41704ea0c0b40bd61e21c8647f1b28 (commit)
via
20141120)
+set(CMake_VERSION_PATCH 20141121)
#set(CMake_VERSION_RC 1)
---
Summary of changes:
Source/CMakeVersion.cmake |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/post-receive
--
CMake
30 matches
Mail list logo
