_VERSION_MINOR 6)
-set(CMake_VERSION_PATCH 20160727)
+set(CMake_VERSION_PATCH 20160728)
#set(CMake_VERSION_RC 1)
---
Summary of changes:
Source/CMakeVersion.cmake |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/
I have 2 projects (one built with cmake, one in the process of being
converted to using it)
Project A (built with cmake) builds lib_a that Project B requires.
I'm thinking I'm doing something wrong around here:
project(lib_a)
...
add_library(lib_a STATIC ${SRC})
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 10aeccbfbd4d34050a470f59757a81cd553f0eb2 (commit)
via
There may be a way to tell, but nothing is coming to mind at the moment.
Maybe someone else on the list can chime in?
On Thu, Jul 28, 2016 at 5:36 AM, Azharuddin Mohammed <
azhar...@codeaurora.org> wrote:
> Thanks for the explanation, Craig. Is there a way to detect if the target
> was a
Thanks for the explanation, Craig. Is there a way to detect if the target was a
physical file created using add_library/add_executable, or a utility target
created using add_custom_target in order to conditionally call the
target_link_libraries command ? There is the condition if(TARGET
Am 27.07.2016 um 19:31 schrieb Ben Boeckel:
On Wed, Jul 27, 2016 at 17:49:40 +0200, Sebastian Holtermann wrote:
Is there an error exit function in CMake?
Or just exit(-1);
Here's an example I found:
this->Makefile->IssueMessage(
cmake::INTERNAL_ERROR, "fileFound is true but
Currently Microsoft's C++ libraries implementation of std::cout/cerr
can't output Unicode characters but only ASCII or ANSI if locale is set
so we implement and use our own ConsoleBuf which can output Unicode
characters to console and it doesn't matter what locale or console's
codepage is set.
---
Am 27.07.2016 um 17:49 schrieb Sebastian Holtermann:
Doing so I found that Base64 allows '+' and '/' as characters which is
bad for directory names obviously.
For now these characters get replaced with 'A' and 'B'.
'_' and '@' would be better replacements (with comments why they are
used)
Doing so I found that Base64 allows '+' and '/' as characters which is
bad for directory names obviously.
For now these characters get replaced with 'A' and 'B'.
'_' and '@' would be better replacements (with comments why they are
used) since 'A' and 'B' are already characters in Base64.
On Tue, Jul 26, 2016 at 23:38:34 +0200, Sebastian Holtermann wrote:
> Doing so I found that Base64 allows '+' and '/' as characters which is
> bad for directory names obviously.
> For now these characters get replaced with 'A' and 'B'.
'_' and '@' would be better replacements (with comments why
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 e752540b9f56d82cc5527c681c3883df66730c48 (commit)
via
11 matches
Mail list logo
