[Cmake-commits] CMake branch, master, updated. v3.9.2-751-ge18ab9c

[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  e18ab9c4b2fc3b11a1e246b1418d25382a853bfb (commit)
  from  d4f58a9cd8e3709a0cb176814226da324b17e0fe (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=e18ab9c4b2fc3b11a1e246b1418d25382a853bfb
commit e18ab9c4b2fc3b11a1e246b1418d25382a853bfb
Author: Kitware Robot <kwro...@kitware.com>
AuthorDate: Sat Sep 9 00:01:09 2017 -0400
Commit: Kitware Robot <kwro...@kitware.com>
CommitDate: Sat Sep 9 00:01:09 2017 -0400

CMake Nightly Date Stamp

diff --git a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake
index c0be9c5..04380a0 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 9)
-set(CMake_VERSION_PATCH 20170908)
+set(CMake_VERSION_PATCH 20170909)
 #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

Re: [CMake] cmake install

[Craig Scott]

On Sat, Sep 9, 2017 at 11:25 AM, Craig Scott 
wrote:

>
>
> On Sat, Sep 9, 2017 at 11:19 AM, Adam Getchell 
> wrote:
>
>>
>> On Sep 8, 2017, at 6:11 PM, Craig Scott  wrote:
>>
>>>
>>> I tried:
>>>
>>> # cmake -G Ninja .
>>> # cmake --build .
>>> # cmake --build . --target install
>>>
>>
>> This should be correct. Did this not work for you?
>>
>>
>> No.
>>
>> https://travis-ci.org/acgetchell/CDT-plusplus/jobs/273498700
>>
>> Thanks for your help.
>>
>
> That job uses sudo to do the install step and pipes the output to a file
> install.log. You will probably find the reason for the failure in that
> install.log file. It would also be unusual to do such an install step to a
> system-wide location as part of a CI job. Perhaps you might want to
> consider creating a package using CPack instead of doing a system-wide
> install.
>

And I just noticed that you did "target" rather than "--target"


-- 
Craig Scott
Melbourne, Australia
https://crascit.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] cmake install

[Craig Scott]

On Sat, Sep 9, 2017 at 11:19 AM, Adam Getchell 
wrote:

>
> On Sep 8, 2017, at 6:11 PM, Craig Scott  wrote:
>
>>
>> I tried:
>>
>> # cmake -G Ninja .
>> # cmake --build .
>> # cmake --build . --target install
>>
>
> This should be correct. Did this not work for you?
>
>
> No.
>
> https://travis-ci.org/acgetchell/CDT-plusplus/jobs/273498700
>
> Thanks for your help.
>

That job uses sudo to do the install step and pipes the output to a file
install.log. You will probably find the reason for the failure in that
install.log file. It would also be unusual to do such an install step to a
system-wide location as part of a CI job. Perhaps you might want to
consider creating a package using CPack instead of doing a system-wide
install.

-- 
Craig Scott
Melbourne, Australia
https://crascit.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] cmake install

[Adam Getchell]

> On Sep 8, 2017, at 6:11 PM, Craig Scott  wrote:
> 
> I tried:
> 
> # cmake -G Ninja .
> # cmake --build .
> # cmake --build . --target install
> 
> This should be correct. Did this not work for you?

No.

https://travis-ci.org/acgetchell/CDT-plusplus/jobs/273498700

Thanks for your help.

>  
> 
> If its somewhere in the manual, I’d appreciate pointers.
> 
> Which part were you looking for? The use of --target is documented as part of 
> the Build Tool Mode 
>  
> section, but it seems you've already figured out that part. There's nothing 
> technically special about the install target as far as I'm aware, you should 
> be able to refer to it as a build target like you've done above.
>  
> 
> Craig Scott
> Melbourne, Australia
> https://crascit.com 
-- 
Adam Getchell
https://keybase.io/adamgetchell

-- 

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] cmake install

[Craig Scott]

On Sat, Sep 9, 2017 at 9:56 AM, Adam Getchell 
wrote:

> Hello all,
>
> If I want to use CMake to invoke my build system, I can use:
>
> # cmake -- build .
>
> What’s the syntax for invoking the build system installer from cmake, i.e.
> the equivalent of:
>
> # cmake -G Ninja .
> # ninja
> # ninja install
>
> I tried:
>
> # cmake -G Ninja .
> # cmake --build .
> # cmake --build . --target install
>

This should be correct. Did this not work for you?


If its somewhere in the manual, I’d appreciate pointers.
>

Which part were you looking for? The use of --target is documented as part
of the Build Tool Mode

section, but it seems you've already figured out that part. There's nothing
technically special about the install target as far as I'm aware, you
should be able to refer to it as a build target like you've done above.


Craig Scott
Melbourne, Australia
https://crascit.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

[CMake] cmake install

[Adam Getchell]

Hello all,

If I want to use CMake to invoke my build system, I can use:

# cmake -- build .

What’s the syntax for invoking the build system installer from cmake, i.e. the 
equivalent of:

# cmake -G Ninja .
# ninja
# ninja install

I tried:

# cmake -G Ninja .
# cmake --build .
# cmake --build . --target install

If its somewhere in the manual, I’d appreciate pointers.

Thanks,
Adam
-- 
Adam Getchell
https://keybase.io/adamgetchell

-- 

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] Merge multiple static libraries into single static library

[Rich Evans via cmake-developers]

Hi all,

I have a CMake library project which contains multiple child CMake projects, 
each of which produces a single static library.

I want the output of the parent project to be a single static library, 
containing all of the child libraries.  I have spent a while researching, and 
found a number of suggestions and implementations of cmake functions/macros to 
do the merging online such as the ones from 
https://www.mail-archive.com/cmake@cmake.org/msg28670/libutils.cmake, 
https://github.com/EddieRingle/erbium/blob/master/scripts/cmake/modules/MergeStaticLibs.cmake,
 https://github.com/FreeRDP/FreeRDP/blob/master/cmake/MergeStaticLibs.cmake.

After setting CMP0026 to OLD, I was able to successfully generate a Visual 
Studio Project using CMake and the last Modelon implementation.  This project 
however, does not contain the references to the other projects in the solution 
to maintain the build order.  If I try and build the project for the main 
combined library, it immediately complains that the libraries it's trying to 
combine don't exist.  If I manually modify the project to add the reference to 
the others and then build, Visual Studio correctly builds the dependencies and 
then combines them.

I tried a number of approaches in the CMake files to try and force a dependency 
for the combined library on the others, but I don't seem to be able to get the 
dependency correctly carrying through to visual studio.  I tried 
add_dependencies(${combined} ${libs}), I tried add_custom_command(${combined} 
DEPENDS ${libs}), I tried changing the declaration of the library from 
add_library(${combined} STATIC ${dummy_file}) to be add_custom_target() instead 
but no joy.

I see a lot of mentions online of Object Libraries, but the child CMake 
projects are also used in other projects so I can't easily go in and modify 
them without also impacting others.

I understand that, normally, linking static libraries is an unusual thing to do 
and so that's likely why CMake is ignoring my attempts, but can anyone suggest 
a way to achieve what it is I'm attempting?

Thanks,
Rich
-- 

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] Create Mac OS Bundle with VTK and Qt

[Oleksii Vilchanskyi via CMake]

Hello,

> 1) I try to add an icon without success
> When I launch my app, the default icon is used and not my icon.

Can you elaborate on this? You say that the .icns file is under
Resources and the final Info.plist contains the proper key with the
proper value and that a non-default icon is used when the application is
launched. If you do actually see the icon on the application [for
example] in Launchpad, then the bundle is correctly built and macOS can
recognize the icon. If instead you see something like this[0], then the
bundle is built incorrectly.

However, you also say "when I launch my app", which, if you mean
application's runtime in particular, is unrelated to CMake or bundling.
If the tray icon is broken etc. it's something your application is not
doing (for example, we use RCC and /image for the icon).

So, if this is the former, then the bundling part is incorrect, if it's
the latter, the program's behaviour is incorrect.

As a side note, I don't rely on MACOSX_PACKAGE_LOCATION property and
install() the icon where it belongs.

> 2) For the libraries of VTK I tried to use macdeployqt (found using
find_program) but it doesn’t found the libraries (installed in a custom
directories)
> Is there a simple way to copy all found libraries/framework?

I would recommend using DeployQt5.cmake module[1] instead of
macdeployqt. Initially found on this list and later edited by Marcus D.
Hanwell, the module (I believe) is distributed under BSD 3-clause.

Usage example[2], also under BSD 3-clause (I believe).

[0]: 
[1]:

[2]:


Regards,
Oleksii Vilchanskyi

On 8.9.2017 18:11, Romain LEGUAY wrote:
> Hello everyone,
> 
> Since this morning, I try to create a Bundle Application using CMake (3.9.1).
> 
> My application use VTK (8.x) and Qt (5.x). The find_package of those two 
> libraries works greats (no problem to build and run the application).
> 
> I have many problems:
> 
> 1) I try to add an icon without success.
> 2) I don’t know how (and where) to copy VTK dynamic libraries.
> ( Optional / not really related ) 3) When I try to use only some components 
> of VTK, my application is linking to all VTK modules
> 
> I’m going to details each points:
> 
> 1) For the icon issue, I proceed this way:
> 
>  
> set(ICON_NAME "appIcon.icns") # I try without the icns extension without 
> success.
> set(ICON_PATH "${CMAKE_CURRENT_SOURCE_DIR}/resources/icons/${ICON_NAME}")
> set_source_files_properties("${ICON_PATH}" PROPERTIES MACOSX_PACKAGE_LOCATION 
> Resources)
> 
> add_executable(MYAPP MACOSX_BUNDLE ${ICON_PATH} ${other_sources})
> 
> set_target_properties(CRAFPACK_GUI PROPERTIES
>   MACOSX_BUNDLE_ICON_FILE ${ICON_NAME})
> 
> 
> The icon is copied inside the Resources folder of my bundle and the 
> Info.plist is well updated (the CFBundleIconFile key is set to 
> "appIcon.icns").
> 
> When I launch my app, the default icon is used and not my icon.
> 
> 
> 2) For the libraries of VTK I tried to use macdeployqt (found using 
> find_program) but it doesn’t found the libraries (installed in a custom 
> directories)
> 
> I tried to use BundleUtilities without any success (except to tell me that 
> cmake doesn’t found the libraries).
> 
> I attach you my CMakeLists.
> 
> Is there a simple way to copy all found libraries/framework?
> 
> Thank you!
> 
> 
> 
-- 

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] Extending XCode scheme generation support

[Steven Velez]

Hello All,

I recently noticed that 3.9.1 added the ability for the XCode generator to
also generate scheme files.  This is great as we have been post processing
generator output to add schemes according to our standards, but are
discovering various issues with this approach.

However, the current scheme generation appears to lack a couple of
abilities we would require to replace our custom scripts.  Primarily, we
need more flexibility over what goes in a particular scheme's launch
configuration.

I have searched the lists and google to try to find discussions on the
intended direction of this feature, but could not find any.

If I were to be able to contribute to this, would there be some sort of
guidance available around how best to expose additional configurability to
a user?  My immediate thoughts are just that we would need to define/use
additional target properties, but is there any sort of recommended naming
convention/scheme or structure that is already existing for mapping sets of
properties in to the more structured format of scheme xml files.

Thanks,
Steven
-- 

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] Create Mac OS Bundle with VTK and Qt

[Romain LEGUAY]

Hello everyone,

Since this morning, I try to create a Bundle Application using CMake (3.9.1).

My application use VTK (8.x) and Qt (5.x). The find_package of those two 
libraries works greats (no problem to build and run the application).

I have many problems:

1) I try to add an icon without success.
2) I don’t know how (and where) to copy VTK dynamic libraries.
( Optional / not really related ) 3) When I try to use only some components of 
VTK, my application is linking to all VTK modules

I’m going to details each points:

1) For the icon issue, I proceed this way:

 
set(ICON_NAME "appIcon.icns") # I try without the icns extension without 
success.
set(ICON_PATH "${CMAKE_CURRENT_SOURCE_DIR}/resources/icons/${ICON_NAME}")
set_source_files_properties("${ICON_PATH}" PROPERTIES MACOSX_PACKAGE_LOCATION 
Resources)

add_executable(MYAPP MACOSX_BUNDLE ${ICON_PATH} ${other_sources})

set_target_properties(CRAFPACK_GUI PROPERTIES
MACOSX_BUNDLE_ICON_FILE ${ICON_NAME})


The icon is copied inside the Resources folder of my bundle and the Info.plist 
is well updated (the CFBundleIconFile key is set to "appIcon.icns").

When I launch my app, the default icon is used and not my icon.


2) For the libraries of VTK I tried to use macdeployqt (found using 
find_program) but it doesn’t found the libraries (installed in a custom 
directories)

I tried to use BundleUtilities without any success (except to tell me that 
cmake doesn’t found the libraries).

I attach you my CMakeLists.

Is there a simple way to copy all found libraries/framework?

Thank you!

cmake_minimum_required(VERSION 3.1)

project (GUI CXX)

set(CMAKE_INCLUDE_CURRENT_DIR ON)
set(CMAKE_AUTOMOC ON)

find_package(VTK COMPONENTS vtkGUISupportQt NO_MODULE)

find_package(Qt5 COMPONENTS Core Widgets Network WebSockets REQUIRED)

if(${ENABLE_MPI})
find_package(MPI REQUIRED)
endif(${ENABLE_MPI})

include(${VTK_USE_FILE})

get_target_property(QtCore_location Qt5::Core LOCATION)
get_target_property(QtWidgets_location Qt5::Widgets LOCATION)
get_target_property(QtNetwork_location Qt5::Network LOCATION)
get_target_property(QtWebSockets_location Qt5::WebSockets LOCATION)
get_target_property(QT5_QMAKE_EXECUTABLE Qt5::qmake IMPORTED_LOCATION)
get_filename_component(QT5_WINDEPLOYQT_PATH ${QT5_QMAKE_EXECUTABLE} PATH)
set(QT5_WINDEPLOYQT_EXECUTABLE "${QT5_WINDEPLOYQT_PATH}/windeployqt.exe")
set(QT5_MACDEPLOYQT_EXECUTABLE "${QT5_WINDEPLOYQT_PATH}/macdeployqt")

include_directories("${COMMON_INCLUDE_DIR}"
services/include
include
resources
${QtCore_location}
${QtWidgets_location}
${QtNetwork_location}
${QtWebSockets_location})

include_directories(${VKT_INCLUDE_DIR} ${MPI_INCLUDE_PATH})

file(GLOB_RECURSE headers
include/*.hpp
include/*.tpp)

file(GLOB_RECURSE sources
src/*.cpp)

file(GLOB_RECURSE services_headers
services/include/*.h*
services/include/*.tpp)

file(GLOB_RECURSE services_sources
services/src/*.c*)


file(GLOB_RECURSE ui_files
resources/ui/*.ui)

file(GLOB_RECURSE qrc_files
resources/*.qrc)

if (APPLE)
set(ICON_NAME "appIcon")
set(ICON_PATH 
"${CMAKE_CURRENT_SOURCE_DIR}/resources/icons/${ICON_NAME}.icns")
endif()

qt5_wrap_ui(ui_sources "${ui_files}")
qt5_add_resources(qrc_resources "${qrc_files}")

if (APPLE)
set_source_files_properties("${ICON_PATH}" PROPERTIES 
MACOSX_PACKAGE_LOCATION Resources)
set_source_files_properties("${VTK_LIBRARIES}" PROPERTIES 
MACOSX_PACKAGE_LOCATION Resources/vtk)
endif()

add_executable(GUI MACOSX_BUNDLE ${headers} ${sources} ${services_headers}
${services_sources} 
${ui_sources} ${qrc_resources} ${ICON_PATH})

set_target_properties(GUI PROPERTIES
CXX_STANDARD 14
CXX_STANDARD_REQUIRED YES
CXX_EXTENSIONS NO
MACOSX_BUNDLE_ICON_FILE ${ICON_NAME}
MACOSX_BUNDLE_GUI_IDENTIFIER "crafpack.TISSU"
MACOSX_BUNDLE_BUNDLE_NAME "TISSU"
BUILD_WITH_INSTALL_RPATH 1)

target_link_libraries(GUI
Qt5::Widgets Qt5::Network Qt5::WebSockets
${VTK_LIBRARIES} ${MPI_LIBRARIES})

if(${ENABLE_MPI})
target_compile_definitions(GUI PRIVATE "-DENABLE_MPI")
endif()

add_custom_command(TARGET GUI
POST_BUILD
COMMAND ${QT5_MACDEPLOYQT_EXECUTABLE} ARGS ${CMAKE_CURRENT_BINARY_DIR}/GUI.app
)-- 

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