Hi,
Part of the work on the SOURCES genex feature is that I want to have uniform
handling of it.
So
add_library(ObjLib OBJECT a.cpp b.cpp)
add_executable(exec c.cpp d.o e.cpp $TARGET_OBJECTS:ObjLib f.cpp)
file(GENERATE OUTPUT exec_files CONTENT $TARGET_PROPERTY:exec,SOURCES)
will result
The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=14776
==
Reported By:Dmitri
Assigned To:
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=14777
==
Reported By:Petr Kmoch
Assigned To:
On 02/26/2014 05:21 PM, Vince Harron wrote:
The question is, how does the cmake project decide on new features?
There is no formal process.
It is just discussion here of the feasibility, design, merits, etc.
Also for non-trivial changes we'd like to feel confident that the
contributor will
On 02/26/2014 04:09 PM, Christoph Grüninger wrote:
hopefully my last try:
https://github.com/gruenich/CMake/commit/60de7f7fd5362580ada234a0513284d08a47519e
Thanks. I've merged a slightly tweaked version to 'next':
FindPkgConfig: Prefer PKG_CONFIG to find pkg-config (#13175)
Brad King wrote:
On 02/27/2014 03:32 AM, Stephen Kelly wrote:
IDE generators are problematic though.
'git grep GetExternalObjects' shows that the IDEs mostly don't call
GetExternalObjects at all.
In this discussion we must distinguish external objects that are
explicit .o files
On 02/27/2014 11:20 AM, Stephen Kelly wrote:
Why do we have to distinguish them? I'm trying to not distinguish them.
I meant to distinguish the existing concepts in this discussion.
Hmm, that is true for VS 10 also. All those generators still
have their own loops to classify sources. They
I was recently communicating with openwatcom matinainers; which just
released a version 2.0 fork on sourceforge... but the issue was
basically... if I have a shared library with no exports, it fails to build.
I used to use a method...(and this is how cmake does it)
wlink (...) # build library
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=14778
==
Reported By:A. Klitzing
Assigned To:
Hi
I am using cmake 2.8.12.2 on MacOSX 10.9 for managing C/C++ code. Targets are 2
shared libraries and a command line binary, while external libraries are boost
and fuse. However, when using Xcode generator I am unable to open the generated
project. Using Makefile generator works fine, but I
You can search the bug tracker http://public.kitware.com/Bug for known
CMake bugs related to Xcode... I don't recall anything like this being
reported recently.
What version of Xcode?
What error message do you get when trying to open the project with
Xcode?
D
--
Powered by
On 27 Feb 2014, at 12:15, David Cole dlrd...@aol.com wrote:
What version of Xcode?
xcode 5.0.2
What error message do you get when trying to open the project with Xcode?
The error says that ’the project file cannot be parsed'--
Powered by www.kitware.com
Please keep messages on-topic
Anybody else out there using Xcode 5.0.2 with CMake yet?
Perhaps open a bug report, and attach the generated Xcode project
files. Or send a minimal CMakeLists.txt file that reproduces the
problem. Does it happen with the very simplest CMakeLists file? (For
example, the one from the tutorial
On Thu, 27 Feb 2014 09:35:09 -0500, David Cole said:
Anybody else out there using Xcode 5.0.2 with CMake yet?
This dashboard of mine is using Xcode 5.0.2 under OS X 10.9:
http://open.cdash.org/buildSummary.php?buildid=3234853
It's basically green.
Cheers,
--
On Thu, Feb 27, 2014, at 06:35 AM, David Cole wrote:
Anybody else out there using Xcode 5.0.2 with CMake yet?
Yes, I'm using LLVM's CMake-generated xcodeproj with Xcode 5.0.2. But I
haven't tried regenerating the xcodeproj since upgrading.
--Kyle Sluder
--
Powered by www.kitware.com
Please
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 b8ebeeaa7d8adeaaf7e207595fc882b207545966 (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 d430024891b6a83af7b71cc2a32e028b02f15079 (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 646c444359faccd06b897b5745b79f8e64e20666 (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 37c294a775cd2a7dc3a34553b271b1dc7738dd2d (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 853a0e370cde10035906d6f68aacf1e13fdd2bb1 (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 1c8323b3d143650ee9d0077e1ed2831db1e95d3b (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 8f1c50feffe3061e14bc4ee8af5e4b24f58de0d2 (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 8c2a1f91d3625a3afdf667a9d7507c357059a0e1 (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 b18cb5acb5b1a094e46457514f7bf02cb3b9b735 (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 d2042f77d15d238d3a27d466a97b58fb76869b3f (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 ffa09c3fc70a23dcde02dafbca1ceb44b691a60a (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 a3ff0e7b0cc739a5308f7a0e4ebeea78e9e4fc6b (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 a5c312be24e966f5b14367065a2e7b6109405f3a (commit)
via
20140227)
+set(CMake_VERSION_PATCH 20140228)
#set(CMake_VERSION_RC 1)
---
Summary of changes:
Source/CMakeVersion.cmake |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/post-receive
--
CMake
29 matches
Mail list logo
