The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=15277
==
Reported By:Georg Altmann
Assigned To:
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=15278
==
Reported By:bogdanm
Assigned To:
On 12/01/2014 10:52 AM, Brad King wrote:
cmSystemTools: Add StringToInt helper
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=5121f118
file: Add LOCK subcommand to do file and directory locking
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=fca624ca
Help: Add notes for topic
On 12/02/2014 09:34 AM, Brad King wrote:
VS, WINCE: Fix entry point for Unicode builds
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=a4962595
Fixed typo in commit message:
VS, WINCE: Fix entry point for Unicode builds
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=681cda02
-Brad
On 12/02/2014 10:27 AM, Brad King wrote:
VS: Add source file properties to set the hlsl shader entry point and model
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=5ab06dcd
I updated the patch to sort the cmake-properties manual list in order:
VS: Add source file properties to set the
On 12/02/2014 04:41 PM, Gilles Khouzam wrote:
I'd like a patch to allow the location of content files to be specified.
Applied and merged for testing, thanks:
VS: Add source file property to specify Windows App deployment location
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=352f246f
On 12/02/2014 04:50 PM, Konstantin Podsvirov wrote:
The command install(...) allows you to specify the COMPONENT.
Why this feature is not used by CMake?
It simply never came up before. There is no reason not to
define components for CMake's installation. What set of
components do you propose?
On 12/02/2014 07:52 PM, Thompson, KT wrote:
1. The command add_library(GSL::gsl UNKOWN IMPORTED) generates
warnings on platforms that do not support shared libraries.
That is a bug in the warning. Fixed:
add_library: Fix target type check for non-shared-lib platforms
On 02.12.2014 12:28, Georg Altmann wrote:
Hi,
I am using CMake for generating a project file for nvidia nsight to edit
CUDA sources.
$ mkdir myproj-build cd myproj-build
$ cmake -GEclipse CDT4 - Unix Makefiles ../myproj
The problem is, eclipse won't recognize the compiler errors
I have a something.cmake file that works when included directly, but
does not work when it is included from inside a function.
can someone explain if there is an intentional difference, and what it
is, between
include(something)
and
function(use_something)
Hi.
The difference is that if there are any variables defined in something,
they will be defined in the scope of the function in the second case,
making them invisible outside of the function.
If that is your problem, you could help this by turning the function into a
macro (which has its own
On 12/2/2014 5:19 PM, Chris Johnson wrote:
The target_link_libraries() directive is adequate for this job when the
header files for the library are simply referred to with no directory
prefix, i.e. #include some file.h instead of #include my
lib/somefile.h. Referencing the library with
I think I've made it work by adding 1 ugly hack and 1 reasonable directive
to each library's CMakeLists.txt, which is at least far preferable to
adding several new include paths to potentially hundreds of programs which
refer to those libraries.
The hack is a function which is defined in my
2014-12-03 21:22 GMT+01:00 Chris Johnson cxjohn...@gmail.com:
I think I've made it work by adding 1 ugly hack and 1 reasonable directive
to each library's CMakeLists.txt, which is at least far preferable to adding
several new include paths to potentially hundreds of programs which refer to
Chris Johnson wrote:
That
seems to imply the top-level source is not part of the default include
path, correct?
Correct. CMake doesn't add anything by default. The only defaults are those
provided by the compiler.
--
Powered by www.kitware.com
Please keep messages on-topic and check the
Chris Johnson wrote:
Yes, by adding another directory between my top-level ./src/ directory and
./mylib, I can cause the example to fail. I understand now that the
include_directory() directive really has no hidden intelligence to it at
all, as I had mistakenly believed. It's just a path.
Angeliki Chrysochou wrote:
Hi Bill,
He wrote
Note also that prog.cpp includes this header via #include myfunc.h.
in his first email, so I thought he wants to include it directly.
See his second email.
Thanks,
Steve.
--
Powered by www.kitware.com
Please keep messages on-topic
Domen Vrankar wrote:
I've started solving this a while ago with treating every library as
an external dependency even if it is part of the same repository as
the code for the executable.
For every new library that I write I also write a FindSomeLib.cmake
Much of what you describe should 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 90db0ab1f178901caab463d797b262f015407cca (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 890288592800ea037c0e176329a02492db4df226 (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 34a3df2f3d59f62be871db543f975c3a44b1cf30 (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 719298b41f47721d3efe2a0bc33709db82118ee5 (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 3fd185d4c3115ccd87d9117bc89a187a08859c36 (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 9843dfab4486f76cab567862e504a71d1ecc58a5 (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 f773e28a8e6033ca128e1dd223fc2345a97efba5 (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 beb75b378f156eed1caa882245278c4aadea6f63 (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 03b3ee7de25acac71fa37c2add32f6d431e82a41 (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 eccc5e34cda8f4c784cffe4a255db82f5b20f832 (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 d91feda4136b8fb9bc3002b38ba8c08fca9cd62c (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 2ddda7bae332030814b8f17cef9f4ff41209c8e6 (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 7c28e7c17205983ef16d72d4ad6f65649355e805 (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 a9d6a0926705062ac183f8fab1cfa14b900a70b4 (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 acbb29284941bd549fa9fd713dac9e50ceb6e58c (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 d6a34e781a210d3c9794d62ed53bbd99d3559357 (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 b7f1ba1691b6b49947eaba55bf506ffc63eafa70 (commit)
via
20141203)
+set(CMake_VERSION_PATCH 20141204)
#set(CMake_VERSION_RC 1)
---
Summary of changes:
Source/CMakeVersion.cmake |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/post-receive
--
CMake
36 matches
Mail list logo
