Am Montag, 22. Dezember 2014, 22:16:50 schrieb Rolf Eike Beer:
Am Montag, 22. Dezember 2014, 10:50:28 schrieb Brad King:
On 12/20/2014 08:44 AM, Rolf Eike Beer wrote:
This is basically the same, but it avoids the needless floating point
arithmetic. Does it work for you?
Thanks, Eike.
Am Dienstag, 23. Dezember 2014, 10:27:47 schrieb Rolf Eike Beer:
Am Montag, 22. Dezember 2014, 22:16:50 schrieb Rolf Eike Beer:
Am Montag, 22. Dezember 2014, 10:50:28 schrieb Brad King:
On 12/20/2014 08:44 AM, Rolf Eike Beer wrote:
This is basically the same, but it avoids the needless
On 12/23/2014 4:27 AM, Rolf Eike Beer wrote:
cmCTest.cxx
C:\Dashboards\My Tests\CMakeNext-vs12-64-ninja-src\Source\cmCTest.cxx(1705) :
warning C4267: 'argument' : conversion from 'size_t' to 'unsigned long',
possible loss of data
The problem is: this is absolutely right. On Windows64 this
On 12/22/2014 6:29 PM, Christoph Grüninger wrote:
please find attached a new patch following your latest suggestions.
Thanks.
I'd like to have lower case components but I dislike mixed-cased
variable names. The latter feeling is stronger.
Mixed-case variable names are quite common in CMake
On 22/12/14 19:38, Rolf Eike Beer wrote:
About the FindPkgConfig macros documentation, what is that is not clear?
It's not about the documentation of that module, but where I need to hack it
into the module. The code is quite a bit of indirections, I guess I would
need
to do this
Hi Brad,
next try and as always better than the last attempt.
Bye
Christoph
From ba775bd58b70ad2581fc05f30d8c5e42e1c94096 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Christoph=20Gr=C3=BCninger?= gruen...@dune-project.org
Date: Tue, 23 Dec 2014 11:33:32 +0100
Subject: [PATCH] FindLATEX: Add
Is there a way to separate components for a library with a SONAME and
the link?
For example if I do something like this:
add_library(foo ${foo_SRCS})
set_target_properties(foo PROPERTIES SOVERSION 1)
install(TARGETS foo
LIBRARY DESTINATION lib)
This will install
Dear CMake developers,
find attached two small patches that get rid of C++ warnings I get from
the current GCC 5 development build.
One patch removes semicolons after methods, the other uses unsigned ints
for version numbers to match the type of the sscanf string %u.
Bye
Christoph
From
On 12/22/2014 02:15 PM, Robert Maynard wrote:
If anyone has any questions or issues with this branch please tell me.
I'd appreciate feedback on this from others with experience in
OS X packaging. For reference, the commit drafts are:
DragNDropGenerator background image now uses source file
On 12/23/2014 06:24 AM, Daniele E. Domenichelli wrote:
I think it would be nice to be able to do something like
install(TARGETS foo
LIBRARY DESTINATION lib COMPONENT library
NAMELINK_COMPONENT devel)
Yes, I think that would make sense.
Thanks,
On 12/23/2014 07:36 AM, Christoph Grüninger wrote:
find attached two small patches that get rid of C++ warnings I get from
the current GCC 5 development build.
One patch removes semicolons after methods, the other uses unsigned ints
for version numbers to match the type of the sscanf string
On 12/23/2014 05:35 AM, Christoph Grüninger wrote:
next try and as always better than the last attempt.
Applied:
FindLATEX: Add components handling
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=07a3f9ad
with minor documentation tweaks and one logic fix:
-# set(LATEX_MAKEINDEX_FOUND
This looks pretty reasonable to me. From Rob's initial email, I
thought it sounded like there was some sort of backward compatibility
problem, but looking through the code, it seems like everything should
all work the same for projects that aren't changing. Was I
misunderstanding about
Hi all. I need a pointer or two.
In my environment I need to have my executables and binaries copied to
another location; this has to happen as part of the default all
target: it can't be required to run install for example (we use the
install rule for a real install step, for one thing).
What
Have you tried the CMake variables LIBRARY_OUTPUT_PATH and
EXECUTABLE_OUTPUT_PATH? I¹ve been using them to accomplish much the same
thing.
Parag Chandra
Software Engineer, Mobile Team
Mobile: +1.919.824.1410
https://ionic.com
Ionic Security Inc.
1170 Peachtree St. NE STE 2285, Atlanta, GA
Paul,
Are you sure there's a problem using TARGET_FILE in your original context?
It seems to me it should work...
From
http://www.cmake.org/cmake/help/v3.1/manual/cmake-generator-expressions.7.html
:
$TARGET_FILE:tgt
Full path to main file (.exe, .so.1.2, .a) where tgt is the name of a
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 ed359fefbc80b68c3cdf91daa082cd74997f20e6 (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 eb2ec05131f8e2a241c02c5fb3e7f03d1d6b54de (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 86e11c7ecd365d5c1019980ece4056b6d8e4b138 (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 2a8f8d925fb30143c1a1f7ca22e125515e8c9c74 (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 a19a43a930a577edb7f2aa2fc11e28faf7134d9c (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 400af305efb009e5274f1122dc0d596fb6781f69 (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 656af73bca01e4d0834b398685513be2a30c2c7d (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 396a008ff0ffed5d4f07f0cb66de5d2523772184 (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 90b015a0bacdbc066670becf0e16843c104cce8c (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 3b3da0d39e36b88db521c8f7eec31ede82596ba1 (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 23e9bc55f38665adab6406980edfaa26f5b14d88 (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 cca8c3bb60ae156e3b14ca3d158a83b819b30d37 (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 f8d5ed133d146f00474fe68e73048c31e8359a83 (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 62b19984039235d5325ee1ad6a7643a4ccd696a8 (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 99f682b0fd2d01c57a365442b472ed628bdb7a9b (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 c49d23f531be40047bd28d0cc248aa6ac47ef41c (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 0ea1a975a8c4873be4529c03a6967b9c3e008c9b (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 e0a5d8f871bccbc5bcf4460778fd5bdfbf1957e3 (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 659c3ac9500c56c2f66302775f2d6a71ba87e943 (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 6a680df6aad7710c9aca4b01a16567dd3ca9771e (commit)
via
20141223)
+set(CMake_VERSION_PATCH 20141224)
#set(CMake_VERSION_RC 1)
---
Summary of changes:
Source/CMakeVersion.cmake |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/post-receive
--
CMake
37 matches
Mail list logo
