_VERSION_MINOR 7)
-set(CMake_VERSION_PATCH 20161121)
+set(CMake_VERSION_PATCH 20161122)
#set(CMake_VERSION_RC 1)
---
Summary of changes:
Source/CMakeVersion.cmake |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/
on Mon Nov 21 2016, Brad King wrote:
> On 11/21/2016 11:06 AM, Dave Abrahams wrote:
>> the documentation for JOB_POOLS is sparse
>
> Yes, it is bare-bones reference documentation for someone that already
> knows how Ninja job pools work.
I know perfectly well how Ninja job pools work. The
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 5b04ef2a793c50b18e258c2236778fd0ae9f1d2c (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 a90b109787bd7e62dd478149992fea0a3bb00b5c (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 2a46ccf4a510d719956769de05e6df2f160005b5 (commit)
via
Hi Peter,
Seems like CMake is continuing to pass cmd line args that are only suitable for
the default msvc compiler, which clang is treating as invalid paths. You need
to override more than just the C_COMPILER. Try the instructions here:
I am trying to use cmake to generate a "Nmake Makefiles" project in a Windows
10 VS2015 (update 3) environment using the VS2015 clang compiler (which is
the MS Clang/C2 compiler, version 3.8.0), but in doing so receive these
errors :
C:\Qsync\Source\Hello_World_C\build\clang_x64_nmake>cmake -G
On 11/19/2016 06:06 AM, Craig Scott wrote:
> can documentation be added for it
Yes, it was simply missing the docs:
https://gitlab.kitware.com/cmake/cmake/merge_requests/271
Thanks,
-Brad
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
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 17a67400ee5eee12577e446a029adb65bd16c394 (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 acde2c4a5389bfe5b1af697a02c160060db7d6e8 (commit)
via
On 11/21/2016 11:06 AM, Dave Abrahams wrote:
> the documentation for JOB_POOLS is sparse
Yes, it is bare-bones reference documentation for someone that already
knows how Ninja job pools work. A sufficiently motivated contributor
could add more to the `Help/generator/Ninja.rst` document in a new
Hi Frank,
I got curious about this myself, and it looks like the checkbox alters the
following in the .pbxproj:
TargetAttributes = {
2BA1B86D1DE33AA300073B96 = {
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 08a3cf513b5807195c8382540fd820dd35a59d8c (commit)
via
Hi all,
I'm finding that the documentation for JOB_POOLS is... sparse, to say
the least. I understand the principle at work, but it's really unclear
how JOB_POOL_LINK and JOB_POOL_COMPILE are supposed to work when set
per-target. When set globally, it's clear that JOB_POOL_COMPILE is
supposed
> On Nov 21, 2016, at 5:04 AM, Michael Jackson
> wrote:
>
> Is there a command or variable or a code snippet from someone that
> essentially has a list of all the "include_directories" that have been
> used/created in a given project? Or can I get a list of all
On Mon, Nov 21, 2016 at 4:21 PM, Tobias Hunger
wrote:
> Hi Tim,
>
> Am 21.11.2016 01:19 schrieb "tim cotter" :
> >
> > i've patched my local cmake to automatically add a virtual folder group
> option for every file in a code blocks project.
> >
Hi Tim,
Am 21.11.2016 01:19 schrieb "tim cotter" :
>
> i've patched my local cmake to automatically add a virtual folder group
option for every file in a code blocks project.
>
> it's not proper support for cmake source groups.
> but it does what i want it to do.
>
> the
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 45d74e9ad32592856852f92471c658256b619e6a (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 2f1cb23aa2499bcdac6d7c5fd3c5666d21e0aa4c (commit)
via
Is there a command or variable or a code snippet from someone that
essentially has a list of all the "include_directories" that have been
used/created in a given project? Or can I get a list of all the
targets(created and imported) and then get the list of
"include_directories" from those
20 matches
Mail list logo