Re: [CMake] linking boost to cmake under OSX 10.12.1 , boost 1.63 , cmake 2017.11

2017-05-03 Thread Michael Ellery

> On May 3, 2017, at 8:20 PM, Sean Wayland  wrote:
> 
> Hi all,
> 
> I am very new to cmake and boost. Sorry if my question is basic thanks for 
> your help in advance. 
> 
> I am having trouble linking a project to boost. I am using OSX 10.12.1 
> I am using clion 2017.1.1 
> 
> I installed boost on my machine using /bootstrap.sh --prefix=/usr/local/boost 
> --with-libraries=filesystem,system
> 
> I also tried a brew install boost also . 
> 
> Boost can indeed be found here usr/local/boost/ on my machine. 
> 
> I haven't had much luck getting boost to link properly. 
> 
> I believe the project uses the filesystem and tuple modules. 
> 
> I am getting this error 
> 
> CMake Error at CMakeLists.txt:557 (ADD_EXECUTABLE):
>   Cannot find source file:
> 
> anyExecutable.cpp
> 


This error means that it can’t find the named source file. The path is relative 
to the CMakeLists.txt file in which you define the target. Does that source 
file exist in that location? 


> From what I have read I think that if you are using OSX that you have to use 
> the FIND_PACKAGE command to link things properly. I suspect that the code 
> below doesn't work because I need to properly place the exact filesystem 
> location of the executable file created in the add_executable command. 
> On a positive note I did get this message 
> -- Boost version: 1.63.0
> -- Found the following Boost libraries:
> --   program_options
> -- Configuring done
> 

This indicates that it found some version of boost, but it seems only the 
program_options library. I would add message(“$Boost_LIBRARIES”) after your 
find_package() statement to print out the location of the found libraries to 
see if that matches your expectation. I generally prefer to do a full staged 
build of boost from source..that typically looks like “./bootstrap.sh && ./b2 
stage” — and I then I point to that staged build using a BOOST_ROOT environment 
variable (the CMake boost finder will honor BOOST_ROOT, I believe). You can 
also just do a ./b2 install to put everything in /usr/local/. 

> I have tried various versions of these 2 cmakelists scripts below (A) and (B) 
>  
> 
> Can anyone point me in the direction of a solution here? 
> 
> 
> A) 
> 
> FIND_PACKAGE( Boost 1.63.0 COMPONENTS program_options REQUIRED )
> INCLUDE_DIRECTORIES( ${Boost_INCLUDE_DIR} )
> 
> ADD_EXECUTABLE( anyExecutable anyExecutable.cpp )
> 
> TARGET_LINK_LIBRARIES( anyExecutable ${Boost_LIBRARIES} )
> B) 
> INCLUDE_DIRECTORIES(usr/local/boost/include/)
> 
> ADD_EXECUTABLE(  anyExecutable myMain.cpp )
> 
> TARGET_LINK_LIBRARIES( anyExecutable usr/local/boost/lib/ )
> 
> 

version (A) seems closer to what you want to me - but I suspect the error you 
posted was from option (B). Perhaps try running A again and share the error 
message(s) you get with that.

-Mike


-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake

[Cmake-commits] CMake branch, master, updated. v3.8.1-1036-gec52676

2017-05-03 Thread Kitware Robot
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  ec526768ac5f1e00a39075cd07fd93cffa1f1818 (commit)
  from  84d0841ed7d06779b68a3950054b636f6ef4af74 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=ec526768ac5f1e00a39075cd07fd93cffa1f1818
commit ec526768ac5f1e00a39075cd07fd93cffa1f1818
Author: Kitware Robot <kwro...@kitware.com>
AuthorDate: Thu May 4 00:01:04 2017 -0400
Commit: Kitware Robot <kwro...@kitware.com>
CommitDate: Thu May 4 00:01:04 2017 -0400

CMake Nightly Date Stamp

diff --git a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake
index b99ead6..ce87fe2 100644
--- a/Source/CMakeVersion.cmake
+++ b/Source/CMakeVersion.cmake
@@ -1,5 +1,5 @@
 # CMake version number components.
 set(CMake_VERSION_MAJOR 3)
 set(CMake_VERSION_MINOR 8)
-set(CMake_VERSION_PATCH 20170503)
+set(CMake_VERSION_PATCH 20170504)
 #set(CMake_VERSION_RC 1)

---

Summary of changes:
 Source/CMakeVersion.cmake |2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/mailman/listinfo/cmake-commits


[CMake] linking boost to cmake under OSX 10.12.1 , boost 1.63 , cmake 2017.11

2017-05-03 Thread Sean Wayland
Hi all,

I am very new to cmake and boost. Sorry if my question is basic thanks for
your help in advance.

I am having trouble linking a project to boost. I am using OSX 10.12.1
I am using clion 2017.1.1

I installed boost on my machine using /bootstrap.sh
--prefix=/usr/local/boost --with-libraries=filesystem,system

I also tried a brew install boost also .

Boost can indeed be found here *usr/local/boost/ *on my machine.

I haven't had much luck getting boost to link properly.

I believe the project uses the filesystem and tuple modules.

I am getting this error

CMake Error at CMakeLists.txt:557 (ADD_EXECUTABLE):
  Cannot find source file:

anyExecutable.cpp

>From what I have read I think that if you are using OSX that you have to
use the FIND_PACKAGE command to link things properly. I suspect that the
code below doesn't work because I need to properly place the exact
filesystem location of the executable file created in the add_executable
command.
On a positive note I did get this message
-- Boost version: 1.63.0
-- Found the following Boost libraries:
--   program_options
-- Configuring done

I have tried various versions of these 2 cmakelists scripts below (A) and
(B)

Can anyone point me in the direction of a solution here?


*A) *

FIND_PACKAGE( Boost 1.63.0 COMPONENTS program_options REQUIRED )
INCLUDE_DIRECTORIES( ${Boost_INCLUDE_DIR} )

ADD_EXECUTABLE( anyExecutable anyExecutable.cpp )

TARGET_LINK_LIBRARIES( anyExecutable ${Boost_LIBRARIES} )

B)

INCLUDE_DIRECTORIES(*usr/local/boost/include/*)

ADD_EXECUTABLE( * anyExecutable myMain.cpp *)

TARGET_LINK_LIBRARIES( *anyExecutable usr/local/boost/lib/ *)

Thanks very much for your help .

Yours Sincerely
Sean Wayland

www.seanwayland.com
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake

Re: [CMake] CPack not detecting pkgbuild or product build

2017-05-03 Thread Ayla Khan
That worked - thank you! Do I need to add NSIS manually for Windows installers 
as well? It looks like CMake finds NSIS without any difficulty but I’d rather 
be sure.

Thanks,

Ayla

> On May 3, 2017, at 2:56 PM, Robert Maynard  wrote:
> 
> You will need to append the productbuild type to you CPACK_GENERATOR so it 
> would look like SET(CPACK_GENERATOR "productbuild;STGZ;TGZ")
> 
> On Wed, May 3, 2017 at 4:14 PM, Ayla Khan  > wrote:
> Thank you Robert. The CPACK_GENERATOR variable is currently set to 
> “STGZ;TGZ”. When I installed Xcode, I made sure using xcode-select that the 
> usual command line tools were installed. I can find productbuild in my PATH, 
> but CPACK_BINARY_PRODUCTBUILD is off in CPackConfig.cmake. Do I need to 
> explicitly set CPACK_BINARY_PRODUCTBUILD in my CMakeLists.txt, or do I append 
> a type for packages to CPACK_GENERATOR? I assumed CPACK_GENERATOR was 
> generated automatically.
> 
> Also, I’ve been working with Xcode 8 on OS X 10.11.6, and CPack is ignoring 
> productbuild completely even if I set it using the generator flag. Command 
> line tools were also set up using xcode-select.
> 
> Thanks,
> 
> Ayla
> 
> > On May 3, 2017, at 1:12 PM, Robert Maynard  > > wrote:
> >
> > Hi Ayla,
> >
> > The packages that are built when executing "make package" is determined by 
> > the variable "CPACK_GENERATOR" inside your CPackConfig.cmake ( generally 
> > located in the root of your build directory as it is configured ).
> >
> >
> > On Fri, Apr 7, 2017 at 3:44 PM, Ayla Khan  > > wrote:
> > I’m trying to build a Mac OS X installer package on 10.10.5 using Xcode 7.2 
> > tools with the CPack that ships with CMake 3.7.2. I can generate a package 
> > from the CMake build directory if I call cpack directly on the command line 
> > with -G productbuild, but not through the CMake build using make package. 
> > Is there a CPack setting I need or some other build configuration 
> > information? Is the Xcode version too old?
> >
> > Thanks,
> >
> > Ayla
> > --
> >
> > Powered by www.kitware.com 
> >
> > Please keep messages on-topic and check the CMake FAQ at: 
> > http://www.cmake.org/Wiki/CMake_FAQ 
> >
> > Kitware offers various services to support the CMake community. For more 
> > information on each offering, please visit:
> >
> > CMake Support: http://cmake.org/cmake/help/support.html 
> > 
> > CMake Consulting: http://cmake.org/cmake/help/consulting.html 
> > 
> > CMake Training Courses: http://cmake.org/cmake/help/training.html 
> > 
> >
> > Visit other Kitware open-source projects at 
> > http://www.kitware.com/opensource/opensource.html 
> > 
> >
> > Follow this link to subscribe/unsubscribe:
> > http://public.kitware.com/mailman/listinfo/cmake 
> > 
> >
> 
> 

-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake

Re: [CMake] CPack not detecting pkgbuild or product build

2017-05-03 Thread Robert Maynard
You will need to append the productbuild type to you CPACK_GENERATOR so it
would look like SET(CPACK_GENERATOR "productbuild;STGZ;TGZ")

On Wed, May 3, 2017 at 4:14 PM, Ayla Khan  wrote:

> Thank you Robert. The CPACK_GENERATOR variable is currently set to
> “STGZ;TGZ”. When I installed Xcode, I made sure using xcode-select that the
> usual command line tools were installed. I can find productbuild in my
> PATH, but CPACK_BINARY_PRODUCTBUILD is off in CPackConfig.cmake. Do I need
> to explicitly set CPACK_BINARY_PRODUCTBUILD in my CMakeLists.txt, or do I
> append a type for packages to CPACK_GENERATOR? I assumed CPACK_GENERATOR
> was generated automatically.
>
> Also, I’ve been working with Xcode 8 on OS X 10.11.6, and CPack is
> ignoring productbuild completely even if I set it using the generator flag.
> Command line tools were also set up using xcode-select.
>
> Thanks,
>
> Ayla
>
> > On May 3, 2017, at 1:12 PM, Robert Maynard 
> wrote:
> >
> > Hi Ayla,
> >
> > The packages that are built when executing "make package" is determined
> by the variable "CPACK_GENERATOR" inside your CPackConfig.cmake ( generally
> located in the root of your build directory as it is configured ).
> >
> >
> > On Fri, Apr 7, 2017 at 3:44 PM, Ayla Khan  wrote:
> > I’m trying to build a Mac OS X installer package on 10.10.5 using Xcode
> 7.2 tools with the CPack that ships with CMake 3.7.2. I can generate a
> package from the CMake build directory if I call cpack directly on the
> command line with -G productbuild, but not through the CMake build using
> make package. Is there a CPack setting I need or some other build
> configuration information? Is the Xcode version too old?
> >
> > Thanks,
> >
> > Ayla
> > --
> >
> > Powered by www.kitware.com
> >
> > Please keep messages on-topic and check the CMake FAQ at:
> http://www.cmake.org/Wiki/CMake_FAQ
> >
> > Kitware offers various services to support the CMake community. For more
> information on each offering, please visit:
> >
> > CMake Support: http://cmake.org/cmake/help/support.html
> > CMake Consulting: http://cmake.org/cmake/help/consulting.html
> > CMake Training Courses: http://cmake.org/cmake/help/training.html
> >
> > Visit other Kitware open-source projects at http://www.kitware.com/
> opensource/opensource.html
> >
> > Follow this link to subscribe/unsubscribe:
> > http://public.kitware.com/mailman/listinfo/cmake
> >
>
>
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake

Re: [CMake] CPack not detecting pkgbuild or product build

2017-05-03 Thread Ayla Khan
Thank you Robert. The CPACK_GENERATOR variable is currently set to “STGZ;TGZ”. 
When I installed Xcode, I made sure using xcode-select that the usual command 
line tools were installed. I can find productbuild in my PATH, but 
CPACK_BINARY_PRODUCTBUILD is off in CPackConfig.cmake. Do I need to explicitly 
set CPACK_BINARY_PRODUCTBUILD in my CMakeLists.txt, or do I append a type for 
packages to CPACK_GENERATOR? I assumed CPACK_GENERATOR was generated 
automatically.

Also, I’ve been working with Xcode 8 on OS X 10.11.6, and CPack is ignoring 
productbuild completely even if I set it using the generator flag. Command line 
tools were also set up using xcode-select.

Thanks,

Ayla

> On May 3, 2017, at 1:12 PM, Robert Maynard  wrote:
> 
> Hi Ayla,
> 
> The packages that are built when executing "make package" is determined by 
> the variable "CPACK_GENERATOR" inside your CPackConfig.cmake ( generally 
> located in the root of your build directory as it is configured ).
> 
> 
> On Fri, Apr 7, 2017 at 3:44 PM, Ayla Khan  wrote:
> I’m trying to build a Mac OS X installer package on 10.10.5 using Xcode 7.2 
> tools with the CPack that ships with CMake 3.7.2. I can generate a package 
> from the CMake build directory if I call cpack directly on the command line 
> with -G productbuild, but not through the CMake build using make package. Is 
> there a CPack setting I need or some other build configuration information? 
> Is the Xcode version too old?
> 
> Thanks,
> 
> Ayla
> --
> 
> Powered by www.kitware.com
> 
> Please keep messages on-topic and check the CMake FAQ at: 
> http://www.cmake.org/Wiki/CMake_FAQ
> 
> Kitware offers various services to support the CMake community. For more 
> information on each offering, please visit:
> 
> CMake Support: http://cmake.org/cmake/help/support.html
> CMake Consulting: http://cmake.org/cmake/help/consulting.html
> CMake Training Courses: http://cmake.org/cmake/help/training.html
> 
> Visit other Kitware open-source projects at 
> http://www.kitware.com/opensource/opensource.html
> 
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/cmake
> 

-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake

Re: [CMake] CPack not detecting pkgbuild or product build

2017-05-03 Thread Robert Maynard
Hi Ayla,

The packages that are built when executing "make package" is determined by
the variable "CPACK_GENERATOR" inside your CPackConfig.cmake ( generally
located in the root of your build directory as it is configured ).


On Fri, Apr 7, 2017 at 3:44 PM, Ayla Khan  wrote:

> I’m trying to build a Mac OS X installer package on 10.10.5 using Xcode
> 7.2 tools with the CPack that ships with CMake 3.7.2. I can generate a
> package from the CMake build directory if I call cpack directly on the
> command line with -G productbuild, but not through the CMake build using
> make package. Is there a CPack setting I need or some other build
> configuration information? Is the Xcode version too old?
>
> Thanks,
>
> Ayla
> --
>
> Powered by www.kitware.com
>
> Please keep messages on-topic and check the CMake FAQ at:
> http://www.cmake.org/Wiki/CMake_FAQ
>
> Kitware offers various services to support the CMake community. For more
> information on each offering, please visit:
>
> CMake Support: http://cmake.org/cmake/help/support.html
> CMake Consulting: http://cmake.org/cmake/help/consulting.html
> CMake Training Courses: http://cmake.org/cmake/help/training.html
>
> Visit other Kitware open-source projects at http://www.kitware.com/
> opensource/opensource.html
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/cmake
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake

[cmake-developers] Proposed Feature: automatic search prefixes for find modules

2017-05-03 Thread Chuck Atkins
Brad and I discussed this a few years ago but nothing really came of it.
Working through several find modules today, I saw many common patterns for
this and realized it should be pretty easy to implement, so here it is:

Allow the variables ENV{PackageName_ROOT} and PackageName_ROOT to be used
as initial search prefixes for al find_{file,path,library,program} commands
executed from within a find module.

https://gitlab.kitware.com/cmake/cmake/merge_requests/796

Specifying the search prefix is a very common pattern, especially when the
utility is not setup in your path, and prevents the need to explicitly set
the location of all the various headers and libraries for a module when you
can just specify a prefix to use.

Thoughts? Good Idea?  Bad idea?  Good, but do it differently?  Undecided?

Thanks
- Chuck
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers

Re: [cmake-developers] Implicit library trouble with mixed languages

2017-05-03 Thread Brad King
On 05/02/2017 05:47 PM, Christian Pfeiffer wrote:
> Before filtering, gcc's output gives me the libgcc and libgcc_s twice. 

I think we already de-duplicate the results after extraction.

> However, I was mainly asking because the general matching logic there 
> can break down in other ways, too. For example, filtering libclang_rt.* 
> will cause Clang builds that pull in sanitizers, e.g. memory sanitizer 
> or UBsan, which both require libclang_rt.msan-... and 
> libclang_tr.ubsan_... to be linked to break on e.g. Linux.

That was added for this:

* https://gitlab.kitware.com/cmake/cmake/issues/16194
* https://gitlab.kitware.com/cmake/cmake/merge_requests/37

Thanks,
-Brad

-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers


[Cmake-commits] CMake branch, master, updated. v3.8.1-1035-g84d0841

2017-05-03 Thread Kitware Robot
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  84d0841ed7d06779b68a3950054b636f6ef4af74 (commit)
   via  0d8273fa32bdeb7f8bd939864ba6d6ea147e642d (commit)
   via  e335771157a1361e250989a5f2d7540144409e78 (commit)
  from  1fe2dc5ef2a1f262b125a2ba6a85f624ce150dd2 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=84d0841ed7d06779b68a3950054b636f6ef4af74
commit 84d0841ed7d06779b68a3950054b636f6ef4af74
Merge: 1fe2dc5 0d8273f
Author: Brad King 
AuthorDate: Wed May 3 15:10:15 2017 +
Commit: Kitware Robot 
CommitDate: Wed May 3 11:10:19 2017 -0400

Merge topic 'update-vim-syntax'

0d8273fa Merge branch 'upstream-vim-cmake-syntax'
e3357711 vim-cmake-syntax 2017-05-02 (15526199)

Acked-by: Kitware Robot 
Merge-request: !789


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=0d8273fa32bdeb7f8bd939864ba6d6ea147e642d
commit 0d8273fa32bdeb7f8bd939864ba6d6ea147e642d
Merge: 3960038 e335771
Author: Patrick Boettcher 
AuthorDate: Tue May 2 17:34:53 2017 +0200
Commit: Patrick Boettcher 
CommitDate: Tue May 2 17:34:53 2017 +0200

Merge branch 'upstream-vim-cmake-syntax'

* upstream-vim-cmake-syntax:
  vim-cmake-syntax 2017-05-02 (15526199)


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=e335771157a1361e250989a5f2d7540144409e78
commit e335771157a1361e250989a5f2d7540144409e78
Author: vim-cmake-syntax upstream 
AuthorDate: Tue May 2 13:49:23 2017 +0200
Commit: Patrick Boettcher 
CommitDate: Tue May 2 17:34:33 2017 +0200

vim-cmake-syntax 2017-05-02 (15526199)

Code extracted from:

https://github.com/pboettch/vim-cmake-syntax.git

at commit 155261999e9affb087e9034ed6009396de6b8f28 (master).

Upstream Shortlog
-

Patrick Boettcher (7):
  eb4537d6 no tab in CMake-files
  933b6aea update syntax to cmake-version 3.7.1
  545bddcd fix highlighting of keyword variables in ${}-regions and 
cleanups
  9c06c8fb README updated
  2ca39d28 make keywords contained, to inhibit highlighting when 
outside highlighting
  6cb8352f do not highlight strings outside regions
  15526199 update to 3.8.20170502-g7a806

diff --git a/cmake.vim.in b/cmake.vim.in
index 89ece66..389d9e4 100644
--- a/cmake.vim.in
+++ b/cmake.vim.in
@@ -14,54 +14,56 @@ if exists("b:current_syntax")
   finish
 endif
 
-syn match cmakeEscaped /\(\|\\"\|\\n\|\\t\)/ contained
 syn region cmakeComment start="#" end="$" contains=cmakeTodo,@Spell
 syn region cmakeLuaComment start="\[\z(=*\)\[" end="\]\z1\]" 
contains=cmakeTodo,@Spell
-syn region cmakeGeneratorExpression start=/$/
-\ contained oneline 
contains=CONTAINED,cmakeTodo,cmakeVariable,cmakeProperty,cmakeGeneratorExpressions
-syn region cmakeRegistry start=/\[/ end=/]/
-\ contained oneline contains=CONTAINED,cmakeTodo,cmakeEscaped
-syn region cmakeVariableValue start=/\${/ end=/}/
-\ contained oneline contains=CONTAINED,cmakeTodo,cmakeVariable
-syn region cmakeEnvironment start=/\$ENV{/ end=/}/
-\ contained oneline contains=CONTAINED,cmakeTodo
-syn region cmakeString start=/"/ end=/"/
-\ contains=CONTAINED,cmakeTodo
-syn region cmakeArguments start=/(/ end=/)/
-\ contains=ALLBUT,cmakeArguments,cmakeTodo
+
+syn match cmakeEscaped /\(\|\\"\|\\n\|\\t\)/ contained
+syn region cmakeRegistry start="\[" end="]" contained oneline 
contains=cmakeTodo,cmakeEscaped
+
+syn region cmakeGeneratorExpression start="$<" end=">" contained oneline 
contains=cmakeVariableValue,cmakeProperty,cmakeGeneratorExpressions,cmakeTodo
+
+syn region cmakeString start='"' end='"' contained 
contains=cmakeTodo,cmakeVariableValue
+
+syn region cmakeVariableValue start="${" end="}" contained oneline 
contains=cmakeVariable,cmakeTodo
+
+syn region cmakeEnvironment start="$ENV{" end="}" contained oneline 
contains=cmakeTodo
+
+syn region cmakeArguments start="(" end=")" 
contains=ALLBUT,cmakeArguments,cmakeTodo
 
 syn case match
-syn keyword cmakeProperty
+
+syn keyword cmakeProperty contained
 \ ABSTRACT ADDITIONAL_MAKE_CLEAN_FILES ADVANCED ALIASED_TARGET 
ALLOW_DUPLICATE_CUSTOM_TARGETS ANDROID_ANT_ADDITIONAL_OPTIONS ANDROID_API 
ANDROID_API_MIN ANDROID_ARCH ANDROID_ASSETS_DIRECTORIES ANDROID_GUI 
ANDROID_JAR_DEPENDENCIES ANDROID_JAR_DIRECTORIES ANDROID_JAVA_SOURCE_DIR 

[Cmake-commits] CMake branch, master, updated. v3.8.1-1032-g1fe2dc5

2017-05-03 Thread Kitware Robot
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  1fe2dc5ef2a1f262b125a2ba6a85f624ce150dd2 (commit)
   via  bf3c08d648c398026eef363bb43d3f8bfaf2a286 (commit)
   via  f1e91c694b1581b4ae923b3bd4a243372cb29023 (commit)
   via  7e75568b001e29a7428d7489c57cebd909359571 (commit)
   via  0225417f60ebaa9de96dd9a9846c2ef7105a39f1 (commit)
   via  d908987634ad1dd1295ac585ffe7c810bda69415 (commit)
   via  174c02e149ab4bcc9bc98d4e4042eb0b24e2f2ee (commit)
   via  08fa2ba8d0682e0c9c307b572afbcee05cc93477 (commit)
   via  0198502ff4fa3dec9cbd3249f6f458f53a8087f3 (commit)
   via  d1aa2b3f607b35dc5dbf613b2334b6d243ec2bda (commit)
   via  87b9d6d93f2e5e6076992cae7395647359de306d (commit)
  from  96820279541017402c1fe0852444aac68179ddb7 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=1fe2dc5ef2a1f262b125a2ba6a85f624ce150dd2
commit 1fe2dc5ef2a1f262b125a2ba6a85f624ce150dd2
Merge: bf3c08d 7e75568
Author: Brad King 
AuthorDate: Wed May 3 15:04:08 2017 +
Commit: Kitware Robot 
CommitDate: Wed May 3 11:04:17 2017 -0400

Merge topic 'ipo-xcode'

7e75568b Xcode: Support IPO (LTO)

Acked-by: Kitware Robot 
Merge-request: !785


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=bf3c08d648c398026eef363bb43d3f8bfaf2a286
commit bf3c08d648c398026eef363bb43d3f8bfaf2a286
Merge: f1e91c6 d908987
Author: Brad King 
AuthorDate: Wed May 3 15:00:59 2017 +
Commit: Kitware Robot 
CommitDate: Wed May 3 11:01:12 2017 -0400

Merge topic 'port-language-default-to-common-macro'

d9089876 AppleClang: Use common compiler macros for language standard 
default
174c02e1 SunPro: Use common compiler macros for language standard default
08fa2ba8 Clang: Use common compiler macros for language standard default
0198502f Intel: Use common compiler macros for language standard default
d1aa2b3f GNU: Use common compiler macros for language standard default
87b9d6d9 XL: Use common compiler macros for language standard default

Acked-by: Kitware Robot 
Merge-request: !787


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=f1e91c694b1581b4ae923b3bd4a243372cb29023
commit f1e91c694b1581b4ae923b3bd4a243372cb29023
Merge: 9682027 0225417
Author: Brad King 
AuthorDate: Wed May 3 15:00:43 2017 +
Commit: Kitware Robot 
CommitDate: Wed May 3 11:00:51 2017 -0400

Merge topic 'fix-typo-in-pgi-files'

0225417f PGI: Fix typo in logic for C standard flags

Acked-by: Kitware Robot 
Merge-request: !788


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=7e75568b001e29a7428d7489c57cebd909359571
commit 7e75568b001e29a7428d7489c57cebd909359571
Author: Ruslan Baratov 
AuthorDate: Thu Apr 27 21:18:26 2017 +0800
Commit: Ruslan Baratov 
CommitDate: Tue May 2 18:33:25 2017 +0300

Xcode: Support IPO (LTO)

diff --git a/Modules/CheckIPOSupported.cmake b/Modules/CheckIPOSupported.cmake
index 712a95e..6bbde13 100644
--- a/Modules/CheckIPOSupported.cmake
+++ b/Modules/CheckIPOSupported.cmake
@@ -217,7 +217,7 @@ function(check_ipo_supported)
 return()
   endif()
 
-  if(CMAKE_GENERATOR MATCHES "^(Visual Studio |Xcode$)")
+  if(CMAKE_GENERATOR MATCHES "^Visual Studio ")
 _ipo_not_supported("CMake doesn't support IPO for current generator")
 return()
   endif()
diff --git a/Source/cmGlobalXCodeGenerator.cxx 
b/Source/cmGlobalXCodeGenerator.cxx
index d99e3bb..95c1236 100644
--- a/Source/cmGlobalXCodeGenerator.cxx
+++ b/Source/cmGlobalXCodeGenerator.cxx
@@ -1683,8 +1683,11 @@ void 
cmGlobalXCodeGenerator::CreateBuildSettings(cmGeneratorTarget* gtgt,
 return;
   }
 
-  // Check IPO related warning/error.
-  gtgt->IsIPOEnabled(configName);
+  if (gtgt->IsIPOEnabled(configName)) {
+const char* ltoValue =
+  this->CurrentMakefile->IsOn("_CMAKE_LTO_THIN") ? "YES_THIN" : "YES";
+buildSettings->AddAttribute("LLVM_LTO", this->CreateString(ltoValue));
+  }
 
   // Add define flags
   this->CurrentLocalGenerator->AppendFlags(
diff --git a/Source/cmGlobalXCodeGenerator.h b/Source/cmGlobalXCodeGenerator.h
index ee06074..a5d169f 100644
--- a/Source/cmGlobalXCodeGenerator.h
+++ b/Source/cmGlobalXCodeGenerator.h
@@ -90,6 +90,8 @@ public:
 
   bool HasKnownObjectFileLocation(std::string* reason) const CM_OVERRIDE;
 
+  bool IsIPOSupported() const CM_OVERRIDE { 

Re: [CMake] Qt Project Generator for Cmake

2017-05-03 Thread Konstantin Tokarev
  03.05.2017, 11:06, "K O ranjith" :I'm using CMake for Qt creator project(in Non-Qt c++ project).In Qt kit->CMake generator I couldn't find a way to generate a Qt project (o CMakeLists.txt which can open as non-Qt project in Qt creator)(But have generator option to other IDE types like to Generate Visual studio  project)Have any CMake Generator which create Qt project file(or CMakeLists.txt file)'? If you are using cmake already, it makes no sense to generate CMakeLists.txt file, since you already have one.Just build your project as usual, open CMakeLists.txt in Qt Creator, and point build directory in project settings to your build directory path. ,-- Powered by www.kitware.comPlease keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQKitware offers various services to support the CMake community. For more information on each offering, please visit:CMake Support: http://cmake.org/cmake/help/support.htmlCMake Consulting: http://cmake.org/cmake/help/consulting.htmlCMake Training Courses: http://cmake.org/cmake/help/training.htmlVisit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.htmlFollow this link to subscribe/unsubscribe:http://public.kitware.com/mailman/listinfo/cmake  -- Regards,Konstantin -- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake

[CMake] Qt Project Generator for Cmake

2017-05-03 Thread K O ranjith
I'm using CMake for Qt creator project(in Non-Qt c++ project).
In Qt kit->CMake generator I couldn't find a way to generate a Qt project
(o CMakeLists.txt which can open as non-Qt project in Qt creator)
(But have generator option to other IDE types like to Generate Visual
studio  project)
Have any CMake Generator which create Qt project file(or CMakeLists.txt
file)'?
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake