Hello,
On 01/02/16 04:52, Craig Scott wrote:
> After a bit of experimenting, it seems that getting ccache working with the
> Xcode generator isn't so straightforward. For Ninja and Unix Makefiles, the
> RULE_LAUNCH_COMPILE global property nicely gives us the behaviour we want,
> but this doesn't
On 01.02.2016 00:09, Eric Wing wrote:
This has been an ongoing nuisance for me, so I thought I would finally
ask. Is there a way I can force soname versioning without modifying
everybody's CMake build scripts?
The main problem is Android. Using soname versioning on Android will
basically cause
There is currently no way to exclude a component install() from a full
installation. Current workarounds using OPTIONAL do not work reliably
because they depend on previous builds and on the order of the execution of
the
build and install commands for the components and the default target
Let us
_VERSION_MINOR 4)
-set(CMake_VERSION_PATCH 20160201)
+set(CMake_VERSION_PATCH 20160202)
#set(CMake_VERSION_RC 1)
---
Summary of changes:
Source/CMakeVersion.cmake |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/
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 812d9a224af1be364d763b4d907a222f1d44dec0 (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 4ca6b8b949f0fc01122407f5dfc1ab080f7d06a3 (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 a753016ca89b2ff5841cc90850c4a74f193d6977 (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 c022b6f6862c67885401d24c438acac457c64f31 (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 adc3d1244bf373fca10cc15a45e34ac7aac34961 (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 ec2d350795a55ffb5ab1d3b048f62f5db19cd0f4 (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 5ee96fc2724e2264d7ba804586da2f0bc759929d (commit)
via
Hi Yi-Long
Clang-Cl requires a few changes in order to work properly,
I've prototyped the support for Clang-Cl on our CMake fork with the plan to
integrate the support once we've got good confirmation and work through some of
the design issues.
You can find the code on
On 01/29/2016 05:43 PM, Christoph GrĂ¼ninger wrote:
> please find attached a minimal patch to fix a GCC 6 pedantic warning
> concerning a superfluous semicolon after a method.
Applied, thanks:
cmAlgorithms.h: remove superfluous semicolon after method
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 3ca37701c2e37fb18268e4def57c3ca91862f892 (commit)
via
14 matches
Mail list logo