[CMake] Unable to debug Qt app in Xcode

[Roman Wüger]

Hello,

with a simple GUI Qt application I’m unable to stop at a given breakpoint.

Could it be that the xcodeproj is not generated correctly?

I’m using cmake 3.16, Qt 5.14.1 and Xcode 11.3.1 on Catalina 10.15.3

Thanks in advance 

Best Regards
Roman
-- 

Powered by kitware.com/cmake

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

Visit other Kitware open-source projects at https://www.kitware.com/platforms

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake

This mailing list is deprecated in favor of https://discourse.cmake.org

[CMake] Preferred way to deploy Qt app to Mac App Store

[Roman Wüger]

Hello,

What is at the moment the preferred way to deploy a Qt app to the Mac App Store 
and to the iOS App Store ?

Thanks in advance 

Best Regards
Roman
-- 

Powered by kitware.com/cmake

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

Visit other Kitware open-source projects at https://www.kitware.com/platforms

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake

This mailing list is deprecated in favor of https://discourse.cmake.org

Re: [CMake] Problems with installer on macOS

[Roman Wüger]

Setting BundleIsRelocatable to false was the solution

Best regards 
Roman

> Am 08.01.2020 um 21:07 schrieb Roman Wüger :
> 
> Hello,
> 
> I generate a productbuild installer with CPack.
> 
> When I start the installer and view the files then everthing is packaged as 
> it should. But when I install them, then not all files are installed.
> 
> The install protocol from the installer succeeds with no errors.
> 
> Any hints?
> 
> Best Regards
> Roman
> -- 
> 
> Powered by kitware.com/cmake
> 
> Kitware offers various services to support the CMake community. For more 
> information on each offering, please visit https://cmake.org/services
> 
> Visit other Kitware open-source projects at https://www.kitware.com/platforms
> 
> Follow this link to subscribe/unsubscribe:
> https://cmake.org/mailman/listinfo/cmake
> 
> This mailing list is deprecated in favor of https://discourse.cmake.org
-- 

Powered by kitware.com/cmake

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

Visit other Kitware open-source projects at https://www.kitware.com/platforms

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake

This mailing list is deprecated in favor of https://discourse.cmake.org

[CMake] Problems with installer on macOS

[Roman Wüger]

Hello,

I generate a productbuild installer with CPack.

When I start the installer and view the files then everthing is packaged as it 
should. But when I install them, then not all files are installed.

The install protocol from the installer succeeds with no errors.

Any hints?

Best Regards
Roman
-- 

Powered by kitware.com/cmake

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

Visit other Kitware open-source projects at https://www.kitware.com/platforms

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake

This mailing list is deprecated in favor of https://discourse.cmake.org

Re: [CMake] [cmake-developers] productbuild: Installing to absolute system path or to user home path

[Roman Wüger]

Ok if someone is interested I solved it with a post-install script at the 
moment. I installed it in the default location and moved it afterwards with the 
post-install script to the ~/Library...

Regards
Roman

> Am 05.11.2019 um 15:02 schrieb Roman Wüger :
> 
> 
> Hello,
> 
> The main wish is to install to the user directory as described in the 
> documentation, the absolute path to the „all users“ works already:
> 
> Here is the description from the manual, also attached as an image
> 
> Automatic plug-in loading
> Lightroom automatically checks for plug-ins in the standard Modules folder 
> where other Lightroom settings are stored:
>In Mac OS (current user) In Mac OS (all users)
> In Windows XP
> plug-in and also installs a helper application.
> Plug-ins that are installed in this location are automatically listed in the 
> Plug-in Manager dialog. You can use the dialog to enable or disable such a 
> plug-in, but not to remove it. The Remove button is dimmed when such a 
> plug-in is selected.
> ~/Library/Application Support/Adobe/Lightroom/Modules /Library/Application 
> Support/Adobe/Lightroom/Modules
> C:\Documents and Users\username\Application Data\Adobe\Lightroom\Modules
> C:\Users\username\AppData\Roaming\Adobe\Lightroom\Modules You may want to use 
> this location if, for example, you are writing an installer that installs a 
> Lightroom
>In Windows 7/Vista
> 
> 
> 
> 
> Regards
> Roman
> 
>>> Am 01.11.2019 um 05:10 schrieb David Aguilar :
>>> 
>> 
>> I would also suggest avoiding absolute paths so that the user can tell you 
>> where to root the installation.
>> 
>> One way to do that is to use GNUInstallDirs so that the user can specify the 
>> install prefix.  And maybe you want to let them user their home directory be 
>> default if they've not specified it:
>> 
>> 
>> include(GNUInstallDirs)
>> 
>> if (CMAKE_INSTALL_PREFIX_INITIALIZED_TO_DEFAULT)
>> # NOTE: default to the home directory, assumes $HOME is defined in the 
>> environment
>> set(CMAKE_INSTALL_PREFIX $ENV{HOME} CACHE PATH "Installation prefix" 
>> FORCE) 
>> endif ()
>> 
>> [... usual stuff here ...]
>> 
>> # NOTE: relative path
>> install(TARGETS target_name DESTINATION "Library/Application 
>> Support/Adobe/Lightroom/Modules")
>> 
>> 
>> Then the user would just "make && make install" and it'll install to their 
>> ~/Library directory by default.
>> 
>> Then, if they have the permissions to do so, they can install to the global 
>> system location using:
>> 
>> cmake -D CMAKE_INSTALL_PREFIX=/ . &&
>> make &&
>> sudo make install
>> 
>> Mixing both in the same cmake invocation can be done, but now you've made it 
>> impossible to install into other locations (for testing, packaging, etc).
>> 
>> For example, someone might want to package it without sudo, so they might 
>> want to do this instead of "sudo make install":
>> 
>> make DESTDIR=$PWD/tmp install
>> 
>> and then you have a tmp/Library/ directory structure that can be made into a 
>> macOS .pkg installer:
>> 
>> pkgbuild --install-location / --identifier org.domain.pkgs.example 
>> --version 1.0.0 --root tmp example-1.0.0.pkg
>> 
>> And now you have a .pkg installer that updates the global /Library directory 
>> without needing to be root to build it.
>> 
>> 
>> Question -- is this a situation where you want a single build to install 
>> into both locations, or is the literally the same plugin and it only needs 
>> to be in one of the two locations (global vs. user)?  I interpreted your 
>> question to be about the latter, where the user really only needs one or the 
>> other, and it's the same plugin in both cases.
>> 
>> I don't know if cpack handles this for you, but hopefully this is helpful 
>> advice.
>> 
>> 
>>> On Thu, Oct 31, 2019 at 10:19 AM David Cole via cmake-developers 
>>>  wrote:
>>> According to the docs, the INSTALL command uses the absolute path if
>>> it is given as the DESTINATION, so  it should work.
>>> https://cmake.org/cmake/help/latest/command/install.html
>>> 
>>> Did you try using a double quoted string, instead of escaping the
>>> space with a backslash?
>>> 
>>> I think this should work for the absolute one:
>>> INSTALL( ... DESTINATION "/abs/path/to/some folder")
>>> 
>>> For the one in the home directory, I'm not sure if

[cmake-developers] productbuild: Installing to absolute system path or to user home path

[Roman Wüger]


Hello,
 
I tried to install a file/directory with productbuild on macOS which is 
generated with CPack.
The most of the files are installed correctly, but I have two problems:
 
If I want to install to “/Library/Application\ Support/Adobe/Lightroom/Modules”
If I want to install to the users modules folder “~/Library/Application\ 
Support/Adobe/Lightroom/Modules”
 
How can I archive these two?
 
I already tried the following with no luck:

install(DIRECTORY 
$/${CMAKE_PROJECT_NAME}.lrplugin
DESTINATION /Library/Application\ 
Support/Adobe/Lightroom/Modules)
 
install(DIRECTORY 
$/${CMAKE_PROJECT_NAME}.lrplugin
DESTINATION ~/Library/Application\ 
Support/Adobe/Lightroom/Modules)
 
Best Regards
Roman-- 

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:
https://cmake.org/mailman/listinfo/cmake-developers

[CMake] productbuild: Installing to absolute system path or to user home path

[Roman Wüger]


Hello,
 
I tried to install a file/directory with productbuild on macOS which is 
generated with CPack.
The most of the files are installed correctly, but I have two problems:
 
If I want to install to “/Library/Application\ Support/Adobe/Lightroom/Modules”
If I want to install to the users modules folder “~/Library/Application\ 
Support/Adobe/Lightroom/Modules”
 
How can I archive these two?
 
I already tried the following with no luck:

install(DIRECTORY 
$/${CMAKE_PROJECT_NAME}.lrplugin
DESTINATION /Library/Application\ 
Support/Adobe/Lightroom/Modules)
 
install(DIRECTORY 
$/${CMAKE_PROJECT_NAME}.lrplugin
DESTINATION ~/Library/Application\ 
Support/Adobe/Lightroom/Modules)
 
Best Regards
Roman-- 

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:
https://cmake.org/mailman/listinfo/cmake

[CMake] XCode target membership

[Roman Wüger]

Hello,

since Xcode 10 I noticed that I must check the Checkbox (Target membership on 
the right pane) for my target when I want that the assets are recognized for 
the specified target.

Is there a way to automatically set this option via CMake? The problem is that 
when I forget to set this check mark (or it is an automated build), then no app 
icon will be set.

Thanks in advance

Regards
Roman
-- 

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:
https://cmake.org/mailman/listinfo/cmake

Re: [CMake] Android project with CMake and Visual Studio and without Nsight Tegra

[Roman Wüger]

No one?

> Am 15.08.2018 um 17:01 schrieb Roman Wüger :
> 
> Why isn‘t it enough to install the SDK and NDK?
> 
> Regards
> Roman
> 
>> Am 09.08.2018 um 09:02 schrieb Roman Wüger :
>> 
>> Hello,
>> 
>> is it somehow possible to build an Android project with CMake and Visual 
>> Studio without the Nsight Tegra Visual Studio Edition? Because the 
>> installation of NVIDIA Nsight Tegra hangs during configuring the Visual 
>> Studio 2017 in a Virtual Machine.
>> 
>> Thanks in advance
>> 
>> Best Regards
>> -- 
>> 
>> 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:
>> https://cmake.org/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:
> https://cmake.org/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:
https://cmake.org/mailman/listinfo/cmake

[CMake] Translation for CPack.GenericWelcome.txt

[Roman Wüger]

Hello,

I use CPack and productbuild on Mac OS. When I run the Installer after 
creation, then the welcome message in the Installer is German, but I do not 
find a translation for the original english document. Where do the translation 
come from?

Thanks in advance

Regards
Roman
-- 

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:
https://cmake.org/mailman/listinfo/cmake

Re: [CMake] Android project with CMake and Visual Studio and without Nsight Tegra

[Roman Wüger]

Why isn‘t it enough to install the SDK and NDK?

Regards
Roman

> Am 09.08.2018 um 09:02 schrieb Roman Wüger :
> 
> Hello,
> 
> is it somehow possible to build an Android project with CMake and Visual 
> Studio without the Nsight Tegra Visual Studio Edition? Because the 
> installation of NVIDIA Nsight Tegra hangs during configuring the Visual 
> Studio 2017 in a Virtual Machine.
> 
> Thanks in advance
> 
> Best Regards
> -- 
> 
> 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:
> https://cmake.org/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:
https://cmake.org/mailman/listinfo/cmake

Re: [CMake] CMake and Visual Studio Code under linux

[Roman Wüger]

Thank you, I will give it a try.

Regards
Roman

> Am 09.08.2018 um 09:45 schrieb Eric Noulard :
> 
> 
>> Le jeu. 9 août 2018 à 09:09, Roman Wüger  a écrit :
>> Hello,
>> 
>> how can I configure my Project to run it with the Visual Studio Code under 
>> Linux? I did not find a useful generator.
> 
> AFAIK there is no VSCode generator, however you can install VSCode CMake 
> Tools extension which begins to interesting to use (my opinion).
> See:  https://vector-of-bool.github.io/2018/07/20/cmt-1.1.0.html
> 
> interesting meaning I think the project has matured to a point it gives you 
> many valuable features:
> - CMake project view
> - Intellisense
> ...
> have a look at the doc as well: 
> https://vector-of-bool.github.io/docs/vscode-cmake-tools/index.html
> 
> -- 
> Eric
-- 

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:
https://cmake.org/mailman/listinfo/cmake

[CMake] CMake and Visual Studio Code under linux

[Roman Wüger]

Hello,

how can I configure my Project to run it with the Visual Studio Code under 
Linux? I did not find a useful generator.

Thanks in advance

Best Regards
-- 

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:
https://cmake.org/mailman/listinfo/cmake

[CMake] Android project with CMake and Visual Studio and without Nsight Tegra

[Roman Wüger]

Hello,

is it somehow possible to build an Android project with CMake and Visual Studio 
without the Nsight Tegra Visual Studio Edition? Because the installation of 
NVIDIA Nsight Tegra hangs during configuring the Visual Studio 2017 in a 
Virtual Machine.

Thanks in advance

Best Regards
-- 

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:
https://cmake.org/mailman/listinfo/cmake

Re: [CMake] Path to vc_redist

[Roman Wüger]

Thank you Robert,

I came up with the following, maybe someone has a better idea:

if (WIN32)
if(CMAKE_SIZEOF_VOID_P EQUAL 8) # 64-bit
set(REDIST_ARCH x64)
else()
set(REDIST_ARCH x86)
endif()
 
set(REDIST_FILE vcredist_${REDIST_ARCH}.exe)
 
set(CMAKE_INSTALL_SYSTEM_RUNTIME_LIBS_SKIP TRUE)
include(InstallRequiredSystemLibraries)
 
# Check if the list contains minimum one element, to get the path from
list(LENGTHCMAKE_INSTALL_SYSTEM_RUNTIME_LIBS libsCount)
if (libsCount GREATER 0)
list(GET CMAKE_INSTALL_SYSTEM_RUNTIME_LIBS 0 _path)
 
get_filename_component(_path ${_path} DIRECTORY)
get_filename_component(_path ${_path}/../../ ABSOLUTE)
 
if (EXISTS "${_path}/${REDIST_FILE}") # VS 2017
set(REDIST_FILE ${_path}/${REDIST_FILE})
else()
get_filename_component(_path ${_path}/1033ABSOLUTE)
set(REDIST_FILE ${_path}/${REDIST_FILE})
endif()
 
install(PROGRAMS ${_path}/${REDIST_FILE})
endif()
endif()
 
Regards
Roman

> Am 04.09.2017 um 15:20 schrieb Robert Maynard <robert.mayn...@kitware.com>:
> 
> You can use the InstallRequiredSystemLibraries to do this. Since it sounds 
> like you don't want all the libraries installed, use 
> CMAKE_INSTALL_SYSTEM_RUNTIME_LIBS_SKIP and than deduce the path of 
> vc_redist.exe from the value(s) in CMAKE_INSTALL_SYSTEM_RUNTIME_LIBS.
> 
>> On Mon, Sep 4, 2017 at 3:01 AM, Roman Wüger <roman.wue...@gmx.at> wrote:
>> Hello,
>> 
>> is there already an existing function to get the vc_redist.exe for the 
>> current generator?
>> 
>> Regards
>> Roman
>> --
>> 
>> 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-developers] [CMake] Path to vc_redist

[Roman Wüger]

Thank you Robert,

I came up with the following, maybe someone has a better idea:

if (WIN32)
if(CMAKE_SIZEOF_VOID_P EQUAL 8) # 64-bit
set(REDIST_ARCH x64)
else()
set(REDIST_ARCH x86)
endif()
 
set(REDIST_FILE vcredist_${REDIST_ARCH}.exe)
 
set(CMAKE_INSTALL_SYSTEM_RUNTIME_LIBS_SKIP TRUE)
include(InstallRequiredSystemLibraries)
 
# Check if the list contains minimum one element, to get the path from
list(LENGTHCMAKE_INSTALL_SYSTEM_RUNTIME_LIBS libsCount)
if (libsCount GREATER 0)
list(GET CMAKE_INSTALL_SYSTEM_RUNTIME_LIBS 0 _path)
 
get_filename_component(_path ${_path} DIRECTORY)
get_filename_component(_path ${_path}/../../ ABSOLUTE)
 
if (EXISTS "${_path}/${REDIST_FILE}") # VS 2017
set(REDIST_FILE ${_path}/${REDIST_FILE})
else()
get_filename_component(_path ${_path}/1033ABSOLUTE)
set(REDIST_FILE ${_path}/${REDIST_FILE})
endif()
 
install(PROGRAMS ${_path}/${REDIST_FILE})
endif()
endif()
 
Regards
Roman

> Am 04.09.2017 um 15:20 schrieb Robert Maynard <robert.mayn...@kitware.com>:
> 
> You can use the InstallRequiredSystemLibraries to do this. Since it sounds 
> like you don't want all the libraries installed, use 
> CMAKE_INSTALL_SYSTEM_RUNTIME_LIBS_SKIP and than deduce the path of 
> vc_redist.exe from the value(s) in CMAKE_INSTALL_SYSTEM_RUNTIME_LIBS.
> 
>> On Mon, Sep 4, 2017 at 3:01 AM, Roman Wüger <roman.wue...@gmx.at> wrote:
>> Hello,
>> 
>> is there already an existing function to get the vc_redist.exe for the 
>> current generator?
>> 
>> Regards
>> Roman
>> --
>> 
>> 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-developers

[CMake] Path to vc_redist

[Roman Wüger]

Hello,

is there already an existing function to get the vc_redist.exe for the current 
generator?

Regards
Roman
-- 

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] Path to vc_redist

[Roman Wüger]

Hello,

is there already an existing function to get the vc_redist.exe for the current 
generator?

Regards
Roman
-- 

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-developers] Signing of DEB and RPM packages

[Roman Wüger]

Hello,

is the signing of DEB packages (debsigs) and RPM packages (rpmsign or rpm 
--addsign) supported at the moment?

Best Regards
Roman
-- 

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] Signing of DEB and RPM packages

[Roman Wüger]

Hello,

is the signing of DEB packages (debsigs) and RPM packages (rpmsign or rpm 
--addsign) supported at the moment?

Best Regards
Roman
-- 

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 install 3rd party shared libraries

[Roman Wüger]

Sorry for the MailingList thing, it was a reply mistake.

 

So, here is the complete output:

 

CPack: Enable Verbose

CPack Verbose: Read CPack config file: 

CPack Verbose: Read CPack configuration file: 
/home/rowu/MyPackage/CPackConfig.cmake

CPack Verbose: Specified generator: DEB

CPack Verbose: Use generator: cmCPackDebGenerator

CPack Verbose: For project: MyPackage

CPack: Create package using DEB

CPack Verbose: Read description file: 
/opt/cmake-3.8.2-Linux-x86_64/share/cmake-3.8/Templates/CPack.GenericDescription.txt

CPack Verbose: [DEB] requested component grouping = ONE_PER_GROUP

CPack Verbose: Remove toplevel directory: 
/home/rowu/MyPackage/_CPack_Packages/Linux/DEB

CPack: Install projects

CPack: - Run preinstall target for: MyPackage

CPack: - Install project: MyPackage

CPack Verbose: Install configuration: "Release"

CPack Verbose: Installing: 
/home/rowu/MyPackage/_CPack_Packages/Linux/DEB/MyPackage-0.0.0.1499458629/opt/MyPackage-0.0.0.1499458629/./testprog

CPack Verbose: Set runtime path of 
"/home/rowu/MyPackage/_CPack_Packages/Linux/DEB/MyPackage-0.0.0.1499458629/opt/MyPackage-0.0.0.1499458629/bin/testprog"
 to ""

CPack Verbose: Installing: 
/home/rowu/MyPackage/_CPack_Packages/Linux/DEB/MyPackage-0.0.0.1499458629/opt/MyPackage-0.0.0.1499458629/./file1.dat

CPack Verbose: Installing: 
/home/rowu/MyPackage/_CPack_Packages/Linux/DEB/MyPackage-0.0.0.1499458629/opt/MyPackage-0.0.0.1499458629/./file2.dat

CPack Verbose: fixup_bundle

CPack Verbose:   app='/opt/MyPackage-0.0.0.1499458629/bin/testprog'

CPack Verbose:   libs=''

CPack Verbose:   dirs='/usr/local/lib'

CPack Verbose:   ignoreItems=''

CPack Verbose: warning: *NOT* handled - directory/file does not exist...

CMake Error at 
/opt/cmake-3.8.2-Linux-x86_64/share/cmake-3.8/Modules/BundleUtilities.cmake:956 
(message):

  error: fixup_bundle: not a valid bundle

Call Stack (most recent call first):

  /home/rowu/MyPackage/app/testprog/cmake_install.cmake:68 (fixup_bundle)

  /home/rowu/MyPackage/app/cmake_install.cmake:37 (include)

  /home/rowu/MyPackage/cmake_install.cmake:37 (include)

 

CPack Verbose: fixup_bundle: done

CPack Error: Error when generating package: MyPackage

 

 

Regards

Roman

 

-Ursprüngliche Nachricht-
Von: Elvis Stansvik [mailto:elvis.stans...@orexplore.com] 
Gesendet: Mittwoch, 19. Juli 2017 20:07
An: Roman Wüger <roman.wue...@gmx.at>; CMake MailingList <cmake@cmake.org>
Betreff: Re: [CMake] CPack install 3rd party shared libraries

 

(Adding the mailing list back to the list of recepients - It's always good to 
keep the discussion on the list)

 

2017-07-19 19:30 GMT+02:00 Roman Wüger < <mailto:roman.wue...@gmx.at> 
roman.wue...@gmx.at>:

> Hello Elvis,

> 

> I tried you solution, but I get always the message:

> 

> CMake Error at 
> /opt/cmake-3.8.2-Linux-x86_64/share/cmake-3.8/Modules/BundleUtilities.cmake:956
>  (message):

>   error: fixup_bundle: not a valid bundle

 

It would help to see your full CMake code.

 

Was there no warning printed before this error? Something like

"warning: *NOT* handled - " followed by an explanation?

 

Elvis

 

> 

> Regards

> Roman

> 

> -Ursprüngliche Nachricht-----

> Von: CMake [ <mailto:cmake-boun...@cmake.org> mailto:cmake-boun...@cmake.org] 
> Im Auftrag von Roman Wüger

> Gesendet: Mittwoch, 19. Juli 2017 19:14

> An: 'Elvis Stansvik' < <mailto:elvis.stans...@orexplore.com> 
> elvis.stans...@orexplore.com>

> Cc: 'CMake MailingList' < <mailto:cmake@cmake.org> cmake@cmake.org>

> Betreff: Re: [CMake] CPack install 3rd party shared libraries

> 

> Thank you Elvis for the awesome example.

> 

> Best Regards

> Roman

> 

> -Ursprüngliche Nachricht-

> Von: Elvis Stansvik [ <mailto:elvis.stans...@orexplore.com> 
> mailto:elvis.stans...@orexplore.com]

> Gesendet: Mittwoch, 19. Juli 2017 16:51

> An: David Cole < <mailto:dlrd...@aol.com> dlrd...@aol.com>

> Cc: Roman Wüger < <mailto:roman.wue...@gmx.at> roman.wue...@gmx.at>; CMake 
> MailingList 

> < <mailto:cmake@cmake.org> cmake@cmake.org>

> Betreff: Re: [CMake] CPack install 3rd party shared libraries

> 

> 2017-07-19 16:42 GMT+02:00 David Cole < <mailto:dlrd...@aol.com> 
> dlrd...@aol.com>:

>> Very nice example. Does CMake have a place to put examples like VTK 

>> does...? If so, where is it? And if not, it would be super useful to 

>> start one somewhere "official."

> 

> I guess the wiki is for that? Though I think my example should be cleaned up 
> before being put up anywhere.

> 

>> 

>> However, one word of caution on the example. I know it was targeted 

>> at Linux, and perhaps for a very simple case it's proper, but using 

>> 

Re: [CMake] CPack install 3rd party shared libraries

[Roman Wüger]

Thank you Elvis for the awesome example.

Best Regards
Roman

-Ursprüngliche Nachricht-
Von: Elvis Stansvik [mailto:elvis.stans...@orexplore.com] 
Gesendet: Mittwoch, 19. Juli 2017 16:51
An: David Cole <dlrd...@aol.com>
Cc: Roman Wüger <roman.wue...@gmx.at>; CMake MailingList <cmake@cmake.org>
Betreff: Re: [CMake] CPack install 3rd party shared libraries

2017-07-19 16:42 GMT+02:00 David Cole <dlrd...@aol.com>:
> Very nice example. Does CMake have a place to put examples like VTK 
> does...? If so, where is it? And if not, it would be super useful to 
> start one somewhere "official."

I guess the wiki is for that? Though I think my example should be cleaned up 
before being put up anywhere.

>
> However, one word of caution on the example. I know it was targeted at 
> Linux, and perhaps for a very simple case it's proper, but using an 
> unconditional "local" for everything in a 
> gp_resolved_file_type_override would not be something you'd want to do 
> in general, especially on Windows. You would end up with probably on 
> the order of a hundred (or maybe nowadays even a few hundred) DLLs 
> from the Windows system directories inside your bundle. Almost 
> certainly not what you intended.

Yes, good point and I should have said something about that. My example was 
quick and dirty.

In my real projects, I've so far always ended up with separate calls to 
fixup_bundle for the different platforms anyway (though never used fixup_bundle 
on Linux before), so I guess my mind was thinking "oh well, this is just for 
Linux" when I wrote it.

Elvis

>
>
> Cheers,
> David C.
>
>
>
> On Wed, Jul 19, 2017 at 9:57 AM, Elvis Stansvik 
> <elvis.stans...@orexplore.com> wrote:
>> 2017-07-19 13:42 GMT+02:00 Roman Wüger <roman.wue...@gmx.at>:
>>> The problem with BundleUtilities which Inder is that it doesn't support 
>>> generator expressions.
>>>
>>> Maybe I do something wrong?
>>> But I need to specify the path to the executable (generator expression) and 
>>> the paths where to look for dependencies. Right?
>>
>> You don't need to use a generator to fetch the executable path. You 
>> will know the path, since you installed the executable with
>> install(..) :) I think most people essentially hardcode the 
>> executable path in their call to fixup_bundle(..).
>>
>> If you really want to, I think there is a way to use generator 
>> expressions, and that is to put the fixup_bundle(..) call in a 
>> separate file (say InstallStuff.cmake.in), and then process that file 
>> with file(GENERATE OUTPUT ...) [1] to produce InstallStuff.cmake with 
>> generator expressions evaluated and then use install(SCRIPT 
>> InstallStuff.cmake). But that's much too complicated IMHO, and I 
>> would avoid it.
>>
>> I made a minimal example that links against zlib and also the Boost 
>> library you mentioned:
>>
>> cmake_minimum_required(VERSION 2.8)
>>
>> project(bundletest)
>>
>> find_package(ZLIB REQUIRED)
>> find_package(Boost REQUIRED COMPONENTS filesystem)
>>
>> add_executable(bundletest main.cpp)
>>
>> target_include_directories(bundletest PRIVATE ${ZLIB_INCLUDE_DIRS}
>> ${Boost_INCLUDE_DIRS})
>>
>> target_link_libraries(bundletest ${ZLIB_LIBRARIES} 
>> ${Boost_LIBRARIES})
>>
>> install(TARGETS bundletest
>> RUNTIME DESTINATION "bin"
>> )
>>
>> install(CODE "
>> function(gp_resolved_file_type_override resolved_file type_var)
>>set(\${type_var} local PARENT_SCOPE)
>> endfunction()
>> include(BundleUtilities)
>> fixup_bundle(\"\${CMAKE_INSTALL_PREFIX}/bin/bundletest\" \"\" 
>> \"\") " COMPONENT Runtime)
>>
>> main.cpp:
>>
>> #include 
>> #include 
>> #include 
>>
>> using namespace boost::filesystem;
>>
>> int main (int argc, char *argv[]) {
>> // Pretend we're using zlib and Boost
>> deflateInit(0, 0);
>> std::cout << file_size(argv[1]) << std::endl;
>> return 0;
>> }
>>
>> The overriding of the gp_resolved_file_type_override was necessary, 
>> to make it treat all libraries as local (otherwise it skips "system"
>> libraries). See the docs for GetPrerequisites.
>>
>> Building/installing this with
>>
>> mkdir build
>> cd build
>> cmake -DCMAKE_INSTALL_PREFIX=~/bundletest_install ..
>> make install
>>
>> produces:
>>
>> /home/estan/bundletest_install
>> /home/estan/bundletest_install/bin
>

Re: [cmake-developers] [CMake] CPack install 3rd party shared libraries

[Roman Wüger]

The problem with BundleUtilities which Inder is that it doesn't support 
generator expressions.

Maybe I do something wrong?
But I need to specify the path to the executable (generator expression) and the 
paths where to look for dependencies. Right?

Please, could you give me a hint?

Regards
Roman

> Am 19.07.2017 um 12:40 schrieb Elvis Stansvik <elvis.stans...@orexplore.com>:
> 
> 2017-07-19 10:24 GMT+02:00 Roman Wüger <roman.wue...@gmx.at>:
>> Hello,
>> 
>> I have a project which depends on a self compiled 3rd party project (boost)
>> Boost is here only an example, there are other 3rd party libraries too.
>> 
>> If I call the "install" command on the target, then it would be packaged.
>> But how could I add the shared libraries and especially the links for the 
>> shared libraries?
>> 
>> E.g.:
>> libboost_filesystem.so -> libboost_filesystem.so.1.48.0
>> libboost_filesystem.so.1.48.0
>> 
>> Thanks in advance
> 
> I think fixup_bundle() from BundleUtilities is what you want [1].
> 
> We're using it to make our Windows and macOS installs standalone, but
> (I think) it should work on Linux as well.
> 
> [1] https://cmake.org/cmake/help/v3.8/module/BundleUtilities.html
> 
>> 
>> Best Regards
>> Roman
>> --
>> 
>> 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-developers

Re: [CMake] CPack install 3rd party shared libraries

[Roman Wüger]

The problem with BundleUtilities which Inder is that it doesn't support 
generator expressions.

Maybe I do something wrong?
But I need to specify the path to the executable (generator expression) and the 
paths where to look for dependencies. Right?

Please, could you give me a hint?

Regards
Roman

> Am 19.07.2017 um 12:40 schrieb Elvis Stansvik <elvis.stans...@orexplore.com>:
> 
> 2017-07-19 10:24 GMT+02:00 Roman Wüger <roman.wue...@gmx.at>:
>> Hello,
>> 
>> I have a project which depends on a self compiled 3rd party project (boost)
>> Boost is here only an example, there are other 3rd party libraries too.
>> 
>> If I call the "install" command on the target, then it would be packaged.
>> But how could I add the shared libraries and especially the links for the 
>> shared libraries?
>> 
>> E.g.:
>> libboost_filesystem.so -> libboost_filesystem.so.1.48.0
>> libboost_filesystem.so.1.48.0
>> 
>> Thanks in advance
> 
> I think fixup_bundle() from BundleUtilities is what you want [1].
> 
> We're using it to make our Windows and macOS installs standalone, but
> (I think) it should work on Linux as well.
> 
> [1] https://cmake.org/cmake/help/v3.8/module/BundleUtilities.html
> 
>> 
>> Best Regards
>> Roman
>> --
>> 
>> 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] CPack install 3rd party shared libraries

[Roman Wüger]

Hello,

I have a project which depends on a self compiled 3rd party project (boost)
Boost is here only an example, there are other 3rd party libraries too.

If I call the "install" command on the target, then it would be packaged.
But how could I add the shared libraries and especially the links for the 
shared libraries?

E.g.:
libboost_filesystem.so -> libboost_filesystem.so.1.48.0
libboost_filesystem.so.1.48.0

Thanks in advance

Best Regards
Roman
-- 

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] CPack install 3rd party shared libraries

[Roman Wüger]

Hello,

I have a project which depends on a self compiled 3rd party project (boost)
Boost is here only an example, there are other 3rd party libraries too.

If I call the "install" command on the target, then it would be packaged.
But how could I add the shared libraries and especially the links for the 
shared libraries?

E.g.:
libboost_filesystem.so -> libboost_filesystem.so.1.48.0
libboost_filesystem.so.1.48.0

Thanks in advance

Best Regards
Roman
-- 

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] [cmake-developers] C# Support and Embedded Resources

[Roman Wüger]

Thank you,

The following seems to work:

set_property(SOURCE TextFile1.txt PROPERTY VS_TOOL_OVERRIDE "EmbeddedResource")

Regards
Roman 

> Am 09.05.2017 um 12:34 schrieb Stuermer, Michael SP/HZA-ZSEP 
> <michael.stuer...@schaeffler.com>:
> 
> Set the appropriate tool for the resource files using the source file 
> property VS_TOOL_OVERRIDE.
> 
> This should work.
> 
> Best regards,
> Michael
> 
> -Ursprüngliche Nachricht-
> Von: cmake-developers [mailto:cmake-developers-boun...@cmake.org] Im Auftrag 
> von Roman Wüger
> Gesendet: Montag, 8. Mai 2017 23:05
> An: CMake Developer MailingList; CMake MailingList
> Betreff: [cmake-developers] C# Support and Embedded Resources
> 
> Hello,
> 
> I played around with the C# support in CMake 3.8.0/3.8.1.
> In a project I need embedded resources, how can I add those?
> 
> Regards
> Roman
> -- 
> 
> 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

-- 

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 regexes: Case insensitive and whitespace matching

[Roman Wüger]

Hello Daniel,

I tried it also in various ways, but I think the Regex in Cmake is very 
limited. What has worked for me was to use try_run and implement a simple c++ 
application which uses C++11's  and accept one or two command line 
arguments (~ 15 lines of code).

Hope it helps

Regards Roman

> Am 08.05.2017 um 15:19 schrieb Daniel Lueken :
> 
> Hi!
>  
> Is there any way to do case insensitive matching in string(REGEX … ?
> Also, is there a way to match whitespaces?
>  
> What I would like to do, speaking in Perl-like syntax, is something like
>  
> string(REGEX REPLACE “/something\s+/stuff/i” …
>  
> Not knowing how to do this, I am currently doing something along the lines of
>  
> string(REGEX REPLACE “[Ss][Oo][Mm][Ee][Tt][Hh][Ii][Nn][Gg][\\r\\n\\t ]+” …
>  
> which looks pretty wrong to me. Converting everything to upper or lower case 
> is also not an option since parts of the input string in which I need to 
> replace something are case sensitive.
>  
> Best regards
> Daniel Lueken
>  
> --
> BMW Car IT GmbH
> Daniel Lüken
> Spezialist Entwicklung
> Moosacher Straße 86
> 80809 München
> 
> Tel.: ­+49-89-189311-35
> Fax: +49-89-189311-20
> Mail: daniel.lue...@bmw-carit.de
> Web: http://www.bmw-carit.de
> -
> BMW Car IT GmbH
> Geschäftsführer: Kai-Uwe Balszuweit und Alexis Trolin
> Sitz und Registergericht: München HRB 134810
> -
>  
> -- 
> 
> 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] C# Support and Embedded Resources

[Roman Wüger]

Hello,

I played around with the C# support in CMake 3.8.0/3.8.1.
In a project I need embedded resources, how can I add those?

Regards
Roman
-- 

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] C# Support and Embedded Resources

[Roman Wüger]

Hello,

I played around with the C# support in CMake 3.8.0/3.8.1.
In a project I need embedded resources, how can I add those?

Regards
Roman
-- 

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-developers] C++11/C++14 doesn't work in check_cxx_source_compiles

[Roman Wüger]

but it does not set/add the required library

> Am 24.11.2016 um 22:01 schrieb Craig Scott <craig.sc...@crascit.com>:
> 
> You might also need to set CMAKE_CXX_EXTENSIONS to OFF (it's ON by default). 
> This controls which c++ library is linked for some compilers, with clang and 
> gcc being two cases where it does this. You may also find this article about 
> the related CMake variables and commands to be of interest.
> 
>> On Fri, Nov 25, 2016 at 5:43 AM, Roman Wüger <roman.wue...@gmx.at> wrote:
>> It is working now, after I added -lc++ to CMAKE_REQUIRED_LIBRARIES before 
>> the check_cxx_source_compiles() call.
>> 
>> Shouldn't this be done by CMAKE_CXX_STANDARD?
>> 
>> Best Regards
>> Roman
>> 
>>> Am 24.11.2016 um 19:08 schrieb Roman Wüger <roman.wue...@gmx.at>:
>>> 
>>> Hello,
>>> 
>>>  
>>> 
>>> If I use a small piece of code which uses , then it fails with 
>>> check_cxx_source_compiles. If I copy the piece of code into a file and run 
>>> the following on the command line, then it works:
>>> 
>>>  
>>> 
>>> clang++ main.cpp -std=c++14 -stdlib=libc++
>>> 
>>>  
>>> 
>>> Here is the piece of code:
>>> 
>>>  
>>> 
>>> #include 
>>> 
>>> #include 
>>> 
>>>  
>>> 
>>> int main() {
>>> 
>>> const std::string text = "Roses are #ff, other flowers have other 
>>> colors.";
>>> 
>>> const std::regex pattern("#([a-f0-9]{2})");
>>> 
>>>  
>>> 
>>> std::smatch match;
>>> 
>>> std::regex_search(text, match, pattern);
>>> 
>>>  
>>> 
>>> return 0;
>>> 
>>> }
>>> 
>>>  
>>> 
>>> I use this code in CMake as a platform check as followed:
>>> 
>>>  
>>> 
>>> # C++11 Regular Expression
>>> 
>>> set(CMAKE_REQUIRED_FLAGS "${CMAKE_CXX_FLAGS}")
>>> 
>>> check_cxx_source_compiles(
>>> 
>>>   "#include 
>>> 
>>>#include 
>>> 
>>>  
>>> 
>>>int main() {
>>> 
>>>const std::string text = \"Roses are #ff, other flowers have 
>>> other colors.\";
>>> 
>>>const std::regex pattern(\"#([a-f0-9]{2})\");
>>> 
>>>  
>>> 
>>>std::smatch match;
>>> 
>>>std::regex_search(text, match, pattern);
>>> 
>>>  
>>> 
>>>return 0;
>>> 
>>>}"
>>> 
>>>   HAVE_CXX11_REGULAR_EXPRESSIONS
>>> 
>>> )
>>> 
>>> set(CMAKE_REQUIRED_FLAGS "")
>>> 
>>>  
>>> 
>>> CMakeFiles/CMakeError.log shows:
>>> 
>>>  
>>> 
>>> Undefined symbols for architecture x86_64:
>>> 
>>>   "std::__1::basic_string<char, std::__1::char_traits, 
>>> std::__1::allocator >::compare(char const*) const", referenced from:
>>> 
>>>   std::__1::basic_regex<char, std::__1::regex_traits 
>>> >::__start_matching_list(bool) in src.o
>>> 
>>>   "std::__1::__vector_base_common::__throw_length_error() const", 
>>> referenced from:
>>> 
>>>   std::__1::vector<std::__1::sub_match, 
>>> std::__1::allocator<std::__1::sub_match > >::assign(unsigned 
>>> long, std::__1::sub_match const&) in src.o
>>> 
>>>   std::__1::vector<std::__1::sub_match, 
>>> std::__1::allocator<std::__1::sub_match > >::allocate(unsigned 
>>> long) in src.o
>>> 
>>>   void std::__1::vector<std::__1::__state, 
>>> std::__1::allocator<std::__1::__state > 
>>> >::__push_back_slow_path<std::__1::__state 
>>> >(std::__1::__state&&) in src.o
>>> 
>>>   std::__1::vector<std::__1::sub_match, 
>>> std::__1::allocator<std::__1::sub_match > >::__append(unsigned 
>>> long, std::__1::sub_match const&) in src.o
>>> 
>>>   std::__1::vector<std::__1::pair, 
>>> std::__1::allocator<std::__1::pair > 
>>> >::__append(unsigned long) in src.o
>>> 
>>>   std::__1::vector<std::__1::pair, 
>>> std::__1::allocator<std::__1::pair > 
&

Re: [CMake] [cmake-developers] C++11/C++14 doesn't work in check_cxx_source_compiles

[Roman Wüger]

It is working now, after I added -lc++ to CMAKE_REQUIRED_LIBRARIES before the 
check_cxx_source_compiles() call.

Shouldn't this be done by CMAKE_CXX_STANDARD?

Best Regards
Roman

> Am 24.11.2016 um 19:08 schrieb Roman Wüger <roman.wue...@gmx.at>:
> 
> Hello,
>  
> If I use a small piece of code which uses , then it fails with 
> check_cxx_source_compiles. If I copy the piece of code into a file and run 
> the following on the command line, then it works:
>  
> clang++ main.cpp -std=c++14 -stdlib=libc++
>  
> Here is the piece of code:
>  
> #include 
> #include 
>  
> int main() {
> const std::string text = "Roses are #ff, other flowers have other 
> colors.";
> const std::regex pattern("#([a-f0-9]{2})");
>  
> std::smatch match;
> std::regex_search(text, match, pattern);
>  
> return 0;
> }
>  
> I use this code in CMake as a platform check as followed:
>  
> # C++11 Regular Expression
> set(CMAKE_REQUIRED_FLAGS "${CMAKE_CXX_FLAGS}")
> check_cxx_source_compiles(
>   "#include 
>#include 
>  
>int main() {
>const std::string text = \"Roses are #ff, other flowers have other 
> colors.\";
>const std::regex pattern(\"#([a-f0-9]{2})\");
>  
>std::smatch match;
>std::regex_search(text, match, pattern);
>  
>return 0;
>}"
>   HAVE_CXX11_REGULAR_EXPRESSIONS
> )
> set(CMAKE_REQUIRED_FLAGS "")
>  
> CMakeFiles/CMakeError.log shows:
>  
> Undefined symbols for architecture x86_64:
>   "std::__1::basic_string<char, std::__1::char_traits, 
> std::__1::allocator >::compare(char const*) const", referenced from:
>   std::__1::basic_regex<char, std::__1::regex_traits 
> >::__start_matching_list(bool) in src.o
>   "std::__1::__vector_base_common::__throw_length_error() const", 
> referenced from:
>   std::__1::vector<std::__1::sub_match, 
> std::__1::allocator<std::__1::sub_match > >::assign(unsigned 
> long, std::__1::sub_match const&) in src.o
>   std::__1::vector<std::__1::sub_match, 
> std::__1::allocator<std::__1::sub_match > >::allocate(unsigned 
> long) in src.o
>   void std::__1::vector<std::__1::__state, 
> std::__1::allocator<std::__1::__state > 
> >::__push_back_slow_path<std::__1::__state >(std::__1::__state&&) 
> in src.o
>   std::__1::vector<std::__1::sub_match, 
> std::__1::allocator<std::__1::sub_match > >::__append(unsigned 
> long, std::__1::sub_match const&) in src.o
>   std::__1::vector<std::__1::pair, 
> std::__1::allocator<std::__1::pair > 
> >::__append(unsigned long) in src.o
>   std::__1::vector<std::__1::pair, 
> std::__1::allocator<std::__1::pair > 
> >::allocate(unsigned long) in src.o
>   void std::__1::vector<char, std::__1::allocator 
> >::__push_back_slow_path(char&&) in src.o
>   ...
>   "std::__1::__basic_string_common::__throw_length_error() const", 
> referenced from:
>   std::__1::enable_if<__is_forward_iterator<char*>::value, void>::type 
> std::__1::basic_string<char, std::__1::char_traits, 
> std::__1::allocator >::__init<char*>(char*, char*) in src.o
>   std::__1::enable_if<__is_forward_iterator::value, 
> void>::type std::__1::basic_string<char, std::__1::char_traits, 
> std::__1::allocator >::__init(char const*, char const*) in 
> src.o
>   std::__1::enable_if<__is_forward_iterator<std::__1::__wrap_iter<char*> 
> >::value, void>::type std::__1::basic_string<char, 
> std::__1::char_traits, std::__1::allocator 
> >::__init<std::__1::__wrap_iter<char*> >(std::__1::__wrap_iter<char*>, 
> std::__1::__wrap_iter<char*>) in src.o
>   "std::__1::__match_any_but_newline::__exec(std::__1::__state&) 
> const", referenced from:
>   vtable for std::__1::__match_any_but_newline in src.o
>   "std::__1::locale::name() const", referenced from:
>   std::__1::basic_regex<char, std::__1::regex_traits 
> >::__start_matching_list(bool) in src.o
>   "std::__1::locale::use_facet(std::__1::locale::id&) const", referenced from:
>   std::__1::regex_traits::__init() in src.o
>   
> "std::__1::regex_error::regex_error(std::__1::regex_constants::error_type)", 
> referenced from:
>   char const* std::__1::basic_regex<char, std::__1::regex_traits 
> >::__parse(char const*, char const*) in src.o
>   char const* std::__1::basic_regex<char, std::__1::regex_traits 
> >::__parse_

Re: [cmake-developers] C++11/C++14 doesn't work in check_cxx_source_compiles

[Roman Wüger]

It is working now, after I added -lc++ to CMAKE_REQUIRED_LIBRARIES before the 
check_cxx_source_compiles() call.

Shouldn't this be done by CMAKE_CXX_STANDARD?

Best Regards
Roman

> Am 24.11.2016 um 19:08 schrieb Roman Wüger <roman.wue...@gmx.at>:
> 
> Hello,
>  
> If I use a small piece of code which uses , then it fails with 
> check_cxx_source_compiles. If I copy the piece of code into a file and run 
> the following on the command line, then it works:
>  
> clang++ main.cpp -std=c++14 -stdlib=libc++
>  
> Here is the piece of code:
>  
> #include 
> #include 
>  
> int main() {
> const std::string text = "Roses are #ff, other flowers have other 
> colors.";
> const std::regex pattern("#([a-f0-9]{2})");
>  
> std::smatch match;
> std::regex_search(text, match, pattern);
>  
> return 0;
> }
>  
> I use this code in CMake as a platform check as followed:
>  
> # C++11 Regular Expression
> set(CMAKE_REQUIRED_FLAGS "${CMAKE_CXX_FLAGS}")
> check_cxx_source_compiles(
>   "#include 
>#include 
>  
>int main() {
>const std::string text = \"Roses are #ff, other flowers have other 
> colors.\";
>const std::regex pattern(\"#([a-f0-9]{2})\");
>  
>std::smatch match;
>std::regex_search(text, match, pattern);
>  
>return 0;
>}"
>   HAVE_CXX11_REGULAR_EXPRESSIONS
> )
> set(CMAKE_REQUIRED_FLAGS "")
>  
> CMakeFiles/CMakeError.log shows:
>  
> Undefined symbols for architecture x86_64:
>   "std::__1::basic_string<char, std::__1::char_traits, 
> std::__1::allocator >::compare(char const*) const", referenced from:
>   std::__1::basic_regex<char, std::__1::regex_traits 
> >::__start_matching_list(bool) in src.o
>   "std::__1::__vector_base_common::__throw_length_error() const", 
> referenced from:
>   std::__1::vector<std::__1::sub_match, 
> std::__1::allocator<std::__1::sub_match > >::assign(unsigned 
> long, std::__1::sub_match const&) in src.o
>   std::__1::vector<std::__1::sub_match, 
> std::__1::allocator<std::__1::sub_match > >::allocate(unsigned 
> long) in src.o
>   void std::__1::vector<std::__1::__state, 
> std::__1::allocator<std::__1::__state > 
> >::__push_back_slow_path<std::__1::__state >(std::__1::__state&&) 
> in src.o
>   std::__1::vector<std::__1::sub_match, 
> std::__1::allocator<std::__1::sub_match > >::__append(unsigned 
> long, std::__1::sub_match const&) in src.o
>   std::__1::vector<std::__1::pair, 
> std::__1::allocator<std::__1::pair > 
> >::__append(unsigned long) in src.o
>   std::__1::vector<std::__1::pair, 
> std::__1::allocator<std::__1::pair > 
> >::allocate(unsigned long) in src.o
>   void std::__1::vector<char, std::__1::allocator 
> >::__push_back_slow_path(char&&) in src.o
>   ...
>   "std::__1::__basic_string_common::__throw_length_error() const", 
> referenced from:
>   std::__1::enable_if<__is_forward_iterator<char*>::value, void>::type 
> std::__1::basic_string<char, std::__1::char_traits, 
> std::__1::allocator >::__init<char*>(char*, char*) in src.o
>   std::__1::enable_if<__is_forward_iterator::value, 
> void>::type std::__1::basic_string<char, std::__1::char_traits, 
> std::__1::allocator >::__init(char const*, char const*) in 
> src.o
>   std::__1::enable_if<__is_forward_iterator<std::__1::__wrap_iter<char*> 
> >::value, void>::type std::__1::basic_string<char, 
> std::__1::char_traits, std::__1::allocator 
> >::__init<std::__1::__wrap_iter<char*> >(std::__1::__wrap_iter<char*>, 
> std::__1::__wrap_iter<char*>) in src.o
>   "std::__1::__match_any_but_newline::__exec(std::__1::__state&) 
> const", referenced from:
>   vtable for std::__1::__match_any_but_newline in src.o
>   "std::__1::locale::name() const", referenced from:
>   std::__1::basic_regex<char, std::__1::regex_traits 
> >::__start_matching_list(bool) in src.o
>   "std::__1::locale::use_facet(std::__1::locale::id&) const", referenced from:
>   std::__1::regex_traits::__init() in src.o
>   
> "std::__1::regex_error::regex_error(std::__1::regex_constants::error_type)", 
> referenced from:
>   char const* std::__1::basic_regex<char, std::__1::regex_traits 
> >::__parse(char const*, char const*) in src.o
>   char const* std::__1::basic_regex<char, std::__1::regex_traits 
> >::__parse_

[cmake-developers] C++11/C++14 doesn't work in check_cxx_source_compiles

[Roman Wüger]

Hello,

 

If I use a small piece of code which uses , then it fails with
check_cxx_source_compiles. If I copy the piece of code into a file and run
the following on the command line, then it works:

 

clang++ main.cpp -std=c++14 -stdlib=libc++

 

Here is the piece of code:

 

#include 

#include 

 

int main() {

const std::string text = "Roses are #ff, other flowers have other
colors.";

const std::regex pattern("#([a-f0-9]{2})");

 

std::smatch match;

std::regex_search(text, match, pattern);

 

return 0;

}

 

I use this code in CMake as a platform check as followed:

 

# C++11 Regular Expression

set(CMAKE_REQUIRED_FLAGS "${CMAKE_CXX_FLAGS}")

check_cxx_source_compiles(

  "#include 

   #include 

 

   int main() {

   const std::string text = \"Roses are #ff, other flowers have
other colors.\";

   const std::regex pattern(\"#([a-f0-9]{2})\");

 

   std::smatch match;

   std::regex_search(text, match, pattern);

 

   return 0;

   }"

  HAVE_CXX11_REGULAR_EXPRESSIONS

)

set(CMAKE_REQUIRED_FLAGS "")

 

CMakeFiles/CMakeError.log shows:

 

Undefined symbols for architecture x86_64:

  "std::__1::basic_string::compare(char const*) const", referenced from:

  std::__1::basic_regex::__start_matching_list(bool) in src.o

  "std::__1::__vector_base_common::__throw_length_error() const",
referenced from:

  std::__1::vector >::assign(unsigned
long, std::__1::sub_match const&) in src.o

  std::__1::vector >::allocate(unsigned
long) in src.o

  void std::__1::vector
>::__push_back_slow_path(std::__1::__state&&) in src.o

  std::__1::vector >::__append(unsigned
long, std::__1::sub_match const&) in src.o

  std::__1::vector
>::__append(unsigned long) in src.o

  std::__1::vector
>::allocate(unsigned long) in src.o

  void std::__1::vector::__push_back_slow_path(char&&) in src.o

  ...

  "std::__1::__basic_string_common::__throw_length_error() const",
referenced from:

  std::__1::enable_if<__is_forward_iterator::value, void>::type
std::__1::basic_string::__init(char*, char*) in src.o

  std::__1::enable_if<__is_forward_iterator::value,
void>::type std::__1::basic_string::__init(char const*, char const*)
in src.o

  std::__1::enable_if<__is_forward_iterator
>::value, void>::type std::__1::basic_string::__init >(std::__1::__wrap_iter,
std::__1::__wrap_iter) in src.o

  "std::__1::__match_any_but_newline::__exec(std::__1::__state&)
const", referenced from:

  vtable for std::__1::__match_any_but_newline in src.o

  "std::__1::locale::name() const", referenced from:

  std::__1::basic_regex::__start_matching_list(bool) in src.o

  "std::__1::locale::use_facet(std::__1::locale::id&) const", referenced
from:

  std::__1::regex_traits::__init() in src.o

 
"std::__1::regex_error::regex_error(std::__1::regex_constants::error_type)",
referenced from:

  char const* std::__1::basic_regex::__parse(char const*, char const*) in src.o

  char const* std::__1::basic_regex::__parse_basic_reg_exp(char const*, char const*) in src.o

  char const* std::__1::basic_regex::__parse_extended_reg_exp(char const*, char const*) in src.o

  char const* std::__1::basic_regex::__parse_assertion(char const*, char const*) in src.o

  char const* std::__1::basic_regex::__parse_atom(char const*, char const*) in src.o

  char const* std::__1::basic_regex::__parse_ERE_dupl_symbol(char const*, char const*,
std::__1::__owns_one_state*, unsigned int, unsigned int) in src.o

  bool std::__1::basic_regex::__match_at_start_ecma >(char const*, char const*, std::__1::match_results > >&,
std::__1::regex_constants::match_flag_type, bool) const in src.o

  ...

  "std::__1::regex_error::~regex_error()", referenced from:

  char const* std::__1::basic_regex::__parse(char const*, char const*) in src.o

  char const* std::__1::basic_regex

[CMake] C++11/C++14 doesn't work in check_cxx_source_compiles

[Roman Wüger]

Hello,

 

If I use a small piece of code which uses , then it fails with
check_cxx_source_compiles. If I copy the piece of code into a file and run
the following on the command line, then it works:

 

clang++ main.cpp -std=c++14 -stdlib=libc++

 

Here is the piece of code:

 

#include 

#include 

 

int main() {

const std::string text = "Roses are #ff, other flowers have other
colors.";

const std::regex pattern("#([a-f0-9]{2})");

 

std::smatch match;

std::regex_search(text, match, pattern);

 

return 0;

}

 

I use this code in CMake as a platform check as followed:

 

# C++11 Regular Expression

set(CMAKE_REQUIRED_FLAGS "${CMAKE_CXX_FLAGS}")

check_cxx_source_compiles(

  "#include 

   #include 

 

   int main() {

   const std::string text = \"Roses are #ff, other flowers have
other colors.\";

   const std::regex pattern(\"#([a-f0-9]{2})\");

 

   std::smatch match;

   std::regex_search(text, match, pattern);

 

   return 0;

   }"

  HAVE_CXX11_REGULAR_EXPRESSIONS

)

set(CMAKE_REQUIRED_FLAGS "")

 

CMakeFiles/CMakeError.log shows:

 

Undefined symbols for architecture x86_64:

  "std::__1::basic_string::compare(char const*) const", referenced from:

  std::__1::basic_regex::__start_matching_list(bool) in src.o

  "std::__1::__vector_base_common::__throw_length_error() const",
referenced from:

  std::__1::vector >::assign(unsigned
long, std::__1::sub_match const&) in src.o

  std::__1::vector >::allocate(unsigned
long) in src.o

  void std::__1::vector
>::__push_back_slow_path(std::__1::__state&&) in src.o

  std::__1::vector >::__append(unsigned
long, std::__1::sub_match const&) in src.o

  std::__1::vector
>::__append(unsigned long) in src.o

  std::__1::vector
>::allocate(unsigned long) in src.o

  void std::__1::vector::__push_back_slow_path(char&&) in src.o

  ...

  "std::__1::__basic_string_common::__throw_length_error() const",
referenced from:

  std::__1::enable_if<__is_forward_iterator::value, void>::type
std::__1::basic_string::__init(char*, char*) in src.o

  std::__1::enable_if<__is_forward_iterator::value,
void>::type std::__1::basic_string::__init(char const*, char const*)
in src.o

  std::__1::enable_if<__is_forward_iterator
>::value, void>::type std::__1::basic_string::__init >(std::__1::__wrap_iter,
std::__1::__wrap_iter) in src.o

  "std::__1::__match_any_but_newline::__exec(std::__1::__state&)
const", referenced from:

  vtable for std::__1::__match_any_but_newline in src.o

  "std::__1::locale::name() const", referenced from:

  std::__1::basic_regex::__start_matching_list(bool) in src.o

  "std::__1::locale::use_facet(std::__1::locale::id&) const", referenced
from:

  std::__1::regex_traits::__init() in src.o

 
"std::__1::regex_error::regex_error(std::__1::regex_constants::error_type)",
referenced from:

  char const* std::__1::basic_regex::__parse(char const*, char const*) in src.o

  char const* std::__1::basic_regex::__parse_basic_reg_exp(char const*, char const*) in src.o

  char const* std::__1::basic_regex::__parse_extended_reg_exp(char const*, char const*) in src.o

  char const* std::__1::basic_regex::__parse_assertion(char const*, char const*) in src.o

  char const* std::__1::basic_regex::__parse_atom(char const*, char const*) in src.o

  char const* std::__1::basic_regex::__parse_ERE_dupl_symbol(char const*, char const*,
std::__1::__owns_one_state*, unsigned int, unsigned int) in src.o

  bool std::__1::basic_regex::__match_at_start_ecma >(char const*, char const*, std::__1::match_results > >&,
std::__1::regex_constants::match_flag_type, bool) const in src.o

  ...

  "std::__1::regex_error::~regex_error()", referenced from:

  char const* std::__1::basic_regex::__parse(char const*, char const*) in src.o

  char const* std::__1::basic_regex

Re: [cmake-developers] iwyu and clang-tidy not working under mac os

[Roman Wüger]

Ok, I've got it.
If anyone is interested, here is my configuration:
find_program(iwyu_path NAMES include-what-you-use iwyu PATHS 
${CMAKE_SOURCE_DIR}/tools/include-what-you-use/${iwyu_os}/bin) if(NOT 
iwyu_path) message(STATUS "Program include-what-you-use: Not found") else() 
message(STATUS "Program include-what-you-use: Found") 
set(CMAKE_CXX_INCLUDE_WHAT_YOU_USE ${iwyu_path}) endif() 
find_program(clang_tidy NAMES clang-tidy clang-tidy-3.8) if(NOT clang_tidy) 
message(STATUS "Program clang-tidy: Not found") else() message(STATUS "Program 
clang-tidy: Found") set(CMAKE_CXX_CLANG_TIDY 
"${clang_tidy};-checks=-*,clang-analyzer-*,-clang-analyzer-alpha*,performance-*,cppcoreguidelines-*,cert-*,modernize-*")
 endif() 

Regards
Roman

> Am 26.10.2016 um 11:50 schrieb Daniel Pfeifer <dan...@pfeifer-mail.de>:
> 
>> On Wed, Oct 26, 2016 at 11:27 AM, Roman Wüger <roman.wue...@gmx.at> wrote:
>> Hello,
>> 
>> I set CMAKE_CXX_INCLUDE_WHAT_YOU_USE and CMAKE_CXX_CLANG_TIDY. Both work as 
>> expected with CMake 3.6.2 under linux. Under Mac OS with the same sources 
>> and the same CMake version doesn't produce any output.
>> 
>> On Linux clang 3.8 is used, on Mac OS it is AppleClang 7.3.0 with clang-tidy 
>> installed from homebrew.
>> 
>> Any hints?
> 
> When you run "make VERBOSE=1" and look at what is executed, do you see any 
> "cmake --iwyu" invocations?
-- 

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] [cmake-developers] iwyu and clang-tidy not working under mac os

[Roman Wüger]

Ok, I've got it.
If anyone is interested, here is my configuration:
find_program(iwyu_path NAMES include-what-you-use iwyu PATHS 
${CMAKE_SOURCE_DIR}/tools/include-what-you-use/${iwyu_os}/bin) if(NOT 
iwyu_path) message(STATUS "Program include-what-you-use: Not found") else() 
message(STATUS "Program include-what-you-use: Found") 
set(CMAKE_CXX_INCLUDE_WHAT_YOU_USE ${iwyu_path}) endif() 
find_program(clang_tidy NAMES clang-tidy clang-tidy-3.8) if(NOT clang_tidy) 
message(STATUS "Program clang-tidy: Not found") else() message(STATUS "Program 
clang-tidy: Found") set(CMAKE_CXX_CLANG_TIDY 
"${clang_tidy};-checks=-*,clang-analyzer-*,-clang-analyzer-alpha*,performance-*,cppcoreguidelines-*,cert-*,modernize-*")
 endif() 

Regards
Roman

> Am 26.10.2016 um 11:50 schrieb Daniel Pfeifer <dan...@pfeifer-mail.de>:
> 
>> On Wed, Oct 26, 2016 at 11:27 AM, Roman Wüger <roman.wue...@gmx.at> wrote:
>> Hello,
>> 
>> I set CMAKE_CXX_INCLUDE_WHAT_YOU_USE and CMAKE_CXX_CLANG_TIDY. Both work as 
>> expected with CMake 3.6.2 under linux. Under Mac OS with the same sources 
>> and the same CMake version doesn't produce any output.
>> 
>> On Linux clang 3.8 is used, on Mac OS it is AppleClang 7.3.0 with clang-tidy 
>> installed from homebrew.
>> 
>> Any hints?
> 
> When you run "make VERBOSE=1" and look at what is executed, do you see any 
> "cmake --iwyu" invocations?
-- 

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] iwyu and clang-tidy not working under mac os

[Roman Wüger]

Hello,

I set CMAKE_CXX_INCLUDE_WHAT_YOU_USE and CMAKE_CXX_CLANG_TIDY. Both work as 
expected with CMake 3.6.2 under linux. Under Mac OS with the same sources and 
the same CMake version doesn't produce any output. 

On Linux clang 3.8 is used, on Mac OS it is AppleClang 7.3.0 with clang-tidy 
installed from homebrew.

Any hints?

Thanks in advance

Best regards
Roman
-- 

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] iwyu and clang-tidy not working under mac os

[Roman Wüger]

Hello,

I set CMAKE_CXX_INCLUDE_WHAT_YOU_USE and CMAKE_CXX_CLANG_TIDY. Both work as 
expected with CMake 3.6.2 under linux. Under Mac OS with the same sources and 
the same CMake version doesn't produce any output. 

On Linux clang 3.8 is used, on Mac OS it is AppleClang 7.3.0 with clang-tidy 
installed from homebrew.

Any hints?

Thanks in advance

Best regards
Roman
-- 

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] Problems with icons for Windows Store 10.0

[Roman Wüger]

Thanks Gilles,

I added a custom appxmanifest as you mentioned and it works, but it would 
nevertheless very helpful to customize such things via variables and let CMake 
fill out the rest.

Regards
Roman

> Am 05.10.2016 um 21:19 schrieb Gilles Khouzam <gilles.khou...@microsoft.com>:
> 
> That's most likely because you're missing an AppxManifest.
> 
> In order to build the CMake detection projects, we inject some necessary 
> files into the project when they aren't specified. This includes the manifest 
> and the icons. Can you add your app manifest to the project (look at 
> Tests\VSWinStorePhone if you want an example) and the icons should not be 
> overridden then.
> 
> Thanks
> 
> -Original Message-
> From: Brad King [mailto:brad.k...@kitware.com] 
> Sent: Wednesday, October 5, 2016 12:09
> To: Roman Wüger <roman.wue...@gmx.at>; Gilles Khouzam 
> <gilles.khou...@microsoft.com>
> Cc: CMake Developer MailingList <cmake-developers@cmake.org>; CMake 
> MailingList <cm...@cmake.org>
> Subject: Re: [cmake-developers] Problems with icons for Windows Store 10.0
> 
>> On 10/05/2016 02:56 PM, Roman Wüger wrote:
>> I tried the following to copy the required app icons to the required 
>> destination:
>> 
>> configure_file(Logo.png 
>> ${CMAKE_CURRENT_BINARY_DIR}/${PROJECT_NAME}.dir/Logo.png COPYONLY)
> 
> That's a CMake-private directory whose location is an implementation detail.
> Some other interface for configuring this behavior will be needed.
> 
>> The CMake process itself overrides those files at the end with the 
>> files from the CMake's Template directory, which are empty.
> 
> From the current implementation it doesn't look like there is anyway to 
> prevent that.  We'll need to have some configuration of where it gets those 
> files.
> 
>> So, how could I use my icon files and/or what is the preferred way of doing 
>> this?
> 
> Gilles?
> 
> -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

Re: [CMake] [cmake-developers] Problems with icons for Windows Store 10.0

[Roman Wüger]

Thanks Gilles,

I added a custom appxmanifest as you mentioned and it works, but it would 
nevertheless very helpful to customize such things via variables and let CMake 
fill out the rest.

Regards
Roman

> Am 05.10.2016 um 21:19 schrieb Gilles Khouzam <gilles.khou...@microsoft.com>:
> 
> That's most likely because you're missing an AppxManifest.
> 
> In order to build the CMake detection projects, we inject some necessary 
> files into the project when they aren't specified. This includes the manifest 
> and the icons. Can you add your app manifest to the project (look at 
> Tests\VSWinStorePhone if you want an example) and the icons should not be 
> overridden then.
> 
> Thanks
> 
> -Original Message-
> From: Brad King [mailto:brad.k...@kitware.com] 
> Sent: Wednesday, October 5, 2016 12:09
> To: Roman Wüger <roman.wue...@gmx.at>; Gilles Khouzam 
> <gilles.khou...@microsoft.com>
> Cc: CMake Developer MailingList <cmake-develop...@cmake.org>; CMake 
> MailingList <cmake@cmake.org>
> Subject: Re: [cmake-developers] Problems with icons for Windows Store 10.0
> 
>> On 10/05/2016 02:56 PM, Roman Wüger wrote:
>> I tried the following to copy the required app icons to the required 
>> destination:
>> 
>> configure_file(Logo.png 
>> ${CMAKE_CURRENT_BINARY_DIR}/${PROJECT_NAME}.dir/Logo.png COPYONLY)
> 
> That's a CMake-private directory whose location is an implementation detail.
> Some other interface for configuring this behavior will be needed.
> 
>> The CMake process itself overrides those files at the end with the 
>> files from the CMake's Template directory, which are empty.
> 
> From the current implementation it doesn't look like there is anyway to 
> prevent that.  We'll need to have some configuration of where it gets those 
> files.
> 
>> So, how could I use my icon files and/or what is the preferred way of doing 
>> this?
> 
> Gilles?
> 
> -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

[CMake] Problems with icons for Windows Store 10.0

[Roman Wüger]

Hello,

I tried the following to copy the required app icons to the required 
destination:

configure_file(Logo.png 
${CMAKE_CURRENT_BINARY_DIR}/${PROJECT_NAME}.dir/Logo.png COPYONLY)

The CMake process itself overrides those files at the end with the files from 
the CMake's Template directory, which are empty.

So, how could I use my icon files and/or what is the preferred way of doing 
this?

Thanks in advance

Best Regards
Roman
-- 

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] Problems with icons for Windows Store 10.0

[Roman Wüger]

Hello,

I tried the following to copy the required app icons to the required 
destination:

configure_file(Logo.png 
${CMAKE_CURRENT_BINARY_DIR}/${PROJECT_NAME}.dir/Logo.png COPYONLY)

The CMake process itself overrides those files at the end with the files from 
the CMake's Template directory, which are empty.

So, how could I use my icon files and/or what is the preferred way of doing 
this?

Thanks in advance

Best Regards
Roman
-- 

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] CPack [WiX] Customizations of individual features/components

[Roman Wüger]

Hello,

I want to customize some with CPack  generated *.wxs files.

For example: directories.wxs is generated with only the TARGET_DIR.

How can I add an additional directory in this file and use the newly added 
directory in the components (features.wxs)?

I read about CPACK_WIX_PATCH_FILE. Maybe it is possible to do so with it, but 
if so how?

Thanks in advance

Regards
Roman
-- 

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] CPack [WiX] Customizations of individual features/components

[Roman Wüger]

Hello,

I want to customize some with CPack  generated *.wxs files.

For example: directories.wxs is generated with only the TARGET_DIR.

How can I add an additional directory in this file and use the newly added 
directory in the components (features.wxs)?

I read about CPACK_WIX_PATCH_FILE. Maybe it is possible to do so with it, but 
if so how?

Thanks in advance

Regards
Roman
-- 

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] [cmake-developers] CPack [NSIS] Install directory per component

[Roman Wüger]

Hello,I've attached a patch with which it is now possible to set custom install directories per component.

0001-CPack-NSIS-custom-component-install-directory.patch
Description: Binary data
Best RegardsRomanAm 21.09.2016 um 23:04 schrieb Roman Wüger <roman.wue...@gmx.at>:Hello,Per default the install directory for acomponent is $INSTDIR.Is there a chance to change the install dir per component?ThanksRoman-- 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-developers-- 

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-developers] CPack [NSIS] Install directory per component

[Roman Wüger]

Hello,I've attached a patch with which it is now possible to set custom install directories per component.

0001-CPack-NSIS-custom-component-install-directory.patch
Description: Binary data
Best RegardsRomanAm 21.09.2016 um 23:04 schrieb Roman Wüger <roman.wue...@gmx.at>:Hello,Per default the install directory for acomponent is $INSTDIR.Is there a chance to change the install dir per component?ThanksRoman-- 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-developers-- 

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] Security in CMake

[Roman Wüger]

The most of the functions could be overloaded.

You could overload those functions, filter options out and pass the new options 
to the original function which starts with and '_' underscore.

The most of the CMake module files could also be overloaded.

Hope it helps

Best regards
Roman

> Am 21.08.2016 um 10:24 schrieb Tobias Hunger :
> 
> Hi Egor,
> 
> Am 20.08.2016 23:42 schrieb "Egor Pugin" :
> > You are right at many points. It's hard to really secure the system
> > from build system/build artifacts/3rd party apps.
> > But step by step it's possible to decrease number of potential sources
> > of vulnerabilities.
> 
> Retrofitting security into a product that was designed without any 
> consideration for security from the start is going to be hard.
> 
> I do not know what you want to do, so I am not going to claim it is 
> impossible:-)
> 
> > Described cmake features would be very helpful for this.
> > Right now I'm just investigating possible security improvements and
> > this is only 'nice-to-have' feature.
> 
> What are the attack scenarios you want to defend against? What should not be 
> possible in your system that currently is in CMake? How do these steps help 
> in securing against those attacks?
> 
> As a user of CMake I am very much opposed to disabling functionality based on 
> the context: That forces me to keep more state in my head when reading 
> CMakeLists.txt files. CMake does way too much in a way to obscure syntax 
> already!
> 
> Best regards,
> Tobias
> 
> > On 21 August 2016 at 00:25, Tobias Hunger  wrote:
> > > Hi Egor,
> > >
> > > Am 20.08.2016 13:48 schrieb "Egor Pugin" :
> > >>
> > >> Hi,
> > >>
> > >> I'm working on a package manager based on cmake.
> > >> And some cmake instructions are downloaded with user packages.
> > >> I'd like to have an ability to deny some cmake features in such
> > >> external untrusted insertions.
> > >
> > > I am no CMake expert, but you are talking about securing a program that is
> > > meant to take arbitrary input and run user-defined commands on that to
> > > produce possibly executable output.
> > >
> > > I do not see any safe subset of CMake commands that is still able to do
> > > anything useful.
> > >
> > > I can see a way for "insertions" to be useful, that does not involve them
> > > changing the configuration (e.g. for a cross compiler), involve running 
> > > some
> > > 3rd party program (e.g. to add support for a new documentation system,
> > > parser generator or whatnot), or the production of build artifacts (e.g.
> > > build some library for the developer to use).
> > >
> > > *All* of  these are inheritently unsafe.
> > >
> > > Configuration change: Change the C compiler to rm and pass force -rf -- / 
> > > as
> > > flags.
> > >
> > > 3rd party program: Run rm -rf / when some certain input file is seen.
> > >
> > > Build artifacts: Put running rm -rf / into the binary/library so that this
> > > is run during normal development workflow.
> > >
> > > I would try to run my package manager in an environment where running rm 
> > > -rf
> > > is harmless to the overall system health. Virtual machines or containers
> > > spring to mind there. Not sure that is feasible.
> > >
> > > Or come up with insertions signing, etc. so that users can at least know
> > > they got what was uploaded and know whom to blame when their systems get
> > > wiped.
> > >
> > > Beat Regards,
> > > Tobias
> >
> >
> >
> > --
> > Egor Pugin
> 
> -- 
> 
> 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
-- 

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-developers] CPack [NSIS] Install directory per component

[Roman Wüger]

Hello,

Per default the install directory for a
component is $INSTDIR.

Is there a chance to change the install dir per component?

Thanks
Roman
-- 

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] CPack [NSIS] Install directory per component

[Roman Wüger]

Hello,

Per default the install directory for a
component is $INSTDIR.

Is there a chance to change the install dir per component?

Thanks
Roman
-- 

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] OSX Code Signing best practice

[Roman Wüger]

Is it possible to sign after your package is complete (copying resource files 
and so on)?

I call a *.sh which is created from the CMake configure step which do the job.

Best Regards
Roman

> Am 12.07.2016 um 18:49 schrieb Harry Mallon :
> 
> Hello all,
> 
> What is the current best practice for code signing OSX .apps and binaries? I 
> am using:
> 
> 1. MAC_OSX_BUNDLE for my .app targets.
> 2. unix style executables
> 3. dylibs
> 4. A prefpane (which I haven't got working yet) using something like the 
> below:
> 
>add_library(prefpane MODULE
>${sourceFiles}
>)
> 
>set_target_properties(codexprefpane PROPERTIES
>BUNDLE YES
>BUNDLE_EXTENSION prefPane
>XCODE_ATTRIBUTE_WRAPPER_EXTENSION prefPane
>MACOSX_BUNDLE_INFO_PLIST ${prefpane_plist_file}
>)
> 
> I am not using the CPackBundle generator so I cannot use the signing in that. 
> I have tried:
> 
> 1. Using set_target_properties(  "XCODE_ATTRIBUTE_CODE_SIGN_IDENTITY" 
> "${SIGN_ID}")
> 2. Using an add_custom_command step. This code signs before all the Resources 
> are copied in so the signatures are invalid
> 
> Any ideas?
> Harry
> 
> Harry Mallon
> CODEX | Software Engineer
> 60 Poland Street | London | England | W1F 7NT
> E ha...@codexdigital.com | T +44 203 7000 989
> -- 
> 
> 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-developers] [CMake] [iOS] What is the correct way to add resources to an XCode project

[Roman Wüger]

Thanks Ben,

I know because I wrote this ticket.

I thought this was "closed/want fixed" because of the implementation for 
RESOURCE a few days ago.

Regards
Roman

> Am 29.06.2016 um 14:52 schrieb Ben Boeckel <ben.boec...@kitware.com>:
> 
>> On Tue, Jun 28, 2016 at 23:01:56 +0200, Roman Wüger wrote:
>> The target property RESOURCE does only allow files but no directories.
> 
> There's an open issue for this:
> 
>https://gitlab.kitware.com/cmake/cmake/issues/14743
> 
> --Ben

-- 

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] [cmake-developers] [iOS] What is the correct way to add resources to an XCode project

[Roman Wüger]

Thanks Ben,

I know because I wrote this ticket.

I thought this was "closed/want fixed" because of the implementation for 
RESOURCE a few days ago.

Regards
Roman

> Am 29.06.2016 um 14:52 schrieb Ben Boeckel <ben.boec...@kitware.com>:
> 
>> On Tue, Jun 28, 2016 at 23:01:56 +0200, Roman Wüger wrote:
>> The target property RESOURCE does only allow files but no directories.
> 
> There's an open issue for this:
> 
>https://gitlab.kitware.com/cmake/cmake/issues/14743
> 
> --Ben

-- 

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] Patch for CM_OVERRIDE

[Roman Wüger]

Hello,

I've attached a patch for the CM_OVERRIDE commit

Best Regards
Roman



0001-fixup-CM_OVERRIDE-Visual-Studio-2010-and-below-do-no.patch
Description: Binary data

-- 

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-developers] [CMake] [iOS] What is the correct way to add resources to an XCode project

[Roman Wüger]

No one?

The target property RESOURCE does only allow files but no directories.

Regards
Roman


> Am 22.06.2016 um 17:22 schrieb Roman Wüger <roman.wue...@gmx.at>:
> 
> Hello,
> 
> I read the mailing list but did find a way which works.
> 
> At the moment I use Xcode 7.3.1 and CMake 3.5.2 which creates a project for 
> iOS 9.3.
> 
> All I want is to add the directory "Images.xcassets" and a second directory 
> structure to be copied to the Resource folder listed in XCode.
> 
> When I manually drag'n drop the directories into the Resource folder as 
> reference or as group everything is working. How can I archive this with 
> CMake?
> 
> Thanks and regards
> Roman
> -- 
> 
> 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-developers

Re: [CMake] [iOS] What is the correct way to add resources to an XCode project

[Roman Wüger]

No one?

The target property RESOURCE does only allow files but no directories.

Regards
Roman


> Am 22.06.2016 um 17:22 schrieb Roman Wüger <roman.wue...@gmx.at>:
> 
> Hello,
> 
> I read the mailing list but did find a way which works.
> 
> At the moment I use Xcode 7.3.1 and CMake 3.5.2 which creates a project for 
> iOS 9.3.
> 
> All I want is to add the directory "Images.xcassets" and a second directory 
> structure to be copied to the Resource folder listed in XCode.
> 
> When I manually drag'n drop the directories into the Resource folder as 
> reference or as group everything is working. How can I archive this with 
> CMake?
> 
> Thanks and regards
> Roman
> -- 
> 
> 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] [iOS] What is the correct way to add resources to an XCode project

[Roman Wüger]

Hello,

I read the mailing list but did find a way which works.

At the moment I use Xcode 7.3.1 and CMake 3.5.2 which creates a project for iOS 
9.3.

All I want is to add the directory "Images.xcassets" and a second directory 
structure to be copied to the Resource folder listed in XCode.

When I manually drag'n drop the directories into the Resource folder as 
reference or as group everything is working. How can I archive this with CMake?

Thanks and regards
Roman
-- 

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] [iOS] What is the correct way to add resources to an XCode project

[Roman Wüger]

Hello,

I read the mailing list but did find a way which works.

At the moment I use Xcode 7.3.1 and CMake 3.5.2 which creates a project for iOS 
9.3.

All I want is to add the directory "Images.xcassets" and a second directory 
structure to be copied to the Resource folder listed in XCode.

When I manually drag'n drop the directories into the Resource folder as 
reference or as group everything is working. How can I archive this with CMake?

Thanks and regards
Roman
-- 

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] Problems when generating xcarchive from within Xcode

[Roman Wüger]

Hello,

I have successfully configured a project with CMake 3.5.2 so it creates a valid 
Release and Debug *.app bundle which runs on iOS. However if I build an archive 
in Xcode with "Product->Archive" then the app bundle seems not complete under 
~/Library/Developer/Xcode/Archives/YYY-MM-DD/*.xcarchive

For example the Info.plist is not the same as in the Release folder, subfolders 
and some files are not copied/created.

Did I need something special for this (the archive)?


Thanks
Roman
-- 

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] Problems when generating xcarchive from within Xcode

[Roman Wüger]

Hello,

I have successfully configured a project with CMake 3.5.2 so it creates a valid 
Release and Debug *.app bundle which runs on iOS. However if I build an archive 
in Xcode with "Product->Archive" then the app bundle seems not complete under 
~/Library/Developer/Xcode/Archives/YYY-MM-DD/*.xcarchive

For example the Info.plist is not the same as in the Release folder, subfolders 
and some files are not copied/created.

Did I need something special for this (the archive)?


Thanks
Roman
-- 

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] Productbuild CPack generator

[Roman Wüger]

Is it in CMake 3.6.x?

Regards
Roman

> Am 02.06.2016 um 18:03 schrieb clin...@elemtech.com:
> 
> Hi Harry,
> 
> I have submitted a productbuild generator this morning.
> https://cmake.org/gitweb?p=cmake.git;a=commit;h=b746bd5c
> 
> Its capabilities should be about equal to the PackageMaker generator.  The 
> code for distribution.xml is shared between PackageMaker and productbuild.
> The preflight/postflight script support should be better with this new 
> generator than with PackageMaker.
> 
> Please do help with testing and development.
> 
> From your other email with suggestions, I have implemented the --version 
> parameter for pkgbuild and product build, and fixed finding the pkgutil and 
> productbuild exectuables.
> 
> I tried a user controlled setting for --install-location but ran into some 
> difficulty getting cmCPackGenerator to cooperate.
> I decided to leave --install-location as '/' and do not see any negative 
> effects of that.  That can be revisited, of course.
> 
> Does anyone here know if we have test coverage already for some cpack 
> generators where we create a package, then unpack it to verify the results?
> 
> Clint
> 
> - On Jun 2, 2016, at 6:21 AM, Harry Mallon  wrote:
> I found this on the other mailing list but it isn't getting much love. Is 
> anyone out there who can tell me how far from being merged in it is? It would 
> really reduce the hackery in our cmake scripts here and I am happy to 
> contribute to it's testing and development if I get some time.
> http://public.kitware.com/pipermail/cmake/2016-May/063493.html
> 
> Harry
> Harry Mallon
> CODEX | Software Engineer
> 
> 60 Poland Street | London | England | W1F 7NT
> E ha...@codexdigital.com | T +44 203 7000 989 
> Website | Facebook | Twitter
> 
> 
> 
> -- 
> 
> 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
> -- 
> 
> 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
-- 

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] [cmake-developers] Empty ERROR_VARIABLE in execute_process

[Roman Wüger]

Ok, thanks Brad.

Hello Qt Mailing list,

First i thought this is a bug in CMake but it has appeared that it seems to be 
a bug in qmllint:

Here the original question:

when I run qmllint from the command line to test an error I get:

C:\Tests>C:\Qt\5.6\msvc2015\bin\qmllint.exe test.qml
test.qml:1 : Syntax error

C:\Tests>echo %ERRORLEVEL%
-1

C:\Tests>


If I call this from a CMake script

execute_process(COMMAND C:/Qt/5.6/msvc2015/bin/qmllint.exe C:/Tests/test.qml
   RESULT_VARIABLE _resVar
   OUTPUT_VARIABLE _outVar
   ERROR_VARIABLE _errVar
 OUTPUT_STRIP_TRAILING_WHITESPACE
   ERROR_STRIP_TRAILING_WHITESPACE)

message("_resVar: ${_resVar}")
message("_outVar: ${_outVar}")
message("_errVar: ${_errVar}")

The output is:

1>  _resVar: -1
1>  _outVar:
1>  _errVar:

It seems that the error pipe isn’t read correctly, because _errVar is empty.

And hints?

Regards
Roman

> Am 23.05.2016 um 19:33 schrieb Brad King <brad.k...@kitware.com>:
> 
>> On 05/23/2016 11:34 AM, Roman Wüger wrote:
>> I tried it with CMake 3.5.1 and 3.5.2 and now with the master with
>> the same result. I've attached an example which won't work.
> 
> I was able to reproduce it with that, but I also tried this:
> 
> add_custom_target(${PROJECT_NAME}-c2
>   COMMAND C:/Qt/5.6/msvc2015/bin/qmllint.exe 
> ${CMAKE_CURRENT_SOURCE_DIR}/test.qml
>   )
> 
> The output does not appear in this case either.  No execute_process
> is involved, and qmllint is invoked directly by msbuild.  This has
> something to do with qmllint changing output behavior when it is
> executed inside a VS IDE (MSBuild) build.
> 
> -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

Re: [cmake-developers] Empty ERROR_VARIABLE in execute_process

[Roman Wüger]

Ok, thanks Brad.

Hello Qt Mailing list,

First i thought this is a bug in CMake but it has appeared that it seems to be 
a bug in qmllint:

Here the original question:

when I run qmllint from the command line to test an error I get:

C:\Tests>C:\Qt\5.6\msvc2015\bin\qmllint.exe test.qml
test.qml:1 : Syntax error

C:\Tests>echo %ERRORLEVEL%
-1

C:\Tests>


If I call this from a CMake script

execute_process(COMMAND C:/Qt/5.6/msvc2015/bin/qmllint.exe C:/Tests/test.qml
   RESULT_VARIABLE _resVar
   OUTPUT_VARIABLE _outVar
   ERROR_VARIABLE _errVar
 OUTPUT_STRIP_TRAILING_WHITESPACE
   ERROR_STRIP_TRAILING_WHITESPACE)

message("_resVar: ${_resVar}")
message("_outVar: ${_outVar}")
message("_errVar: ${_errVar}")

The output is:

1>  _resVar: -1
1>  _outVar:
1>  _errVar:

It seems that the error pipe isn’t read correctly, because _errVar is empty.

And hints?

Regards
Roman

> Am 23.05.2016 um 19:33 schrieb Brad King <brad.k...@kitware.com>:
> 
>> On 05/23/2016 11:34 AM, Roman Wüger wrote:
>> I tried it with CMake 3.5.1 and 3.5.2 and now with the master with
>> the same result. I've attached an example which won't work.
> 
> I was able to reproduce it with that, but I also tried this:
> 
> add_custom_target(${PROJECT_NAME}-c2
>   COMMAND C:/Qt/5.6/msvc2015/bin/qmllint.exe 
> ${CMAKE_CURRENT_SOURCE_DIR}/test.qml
>   )
> 
> The output does not appear in this case either.  No execute_process
> is involved, and qmllint is invoked directly by msbuild.  This has
> something to do with qmllint changing output behavior when it is
> executed inside a VS IDE (MSBuild) build.
> 
> -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

Re: [cmake-developers] [CMake] Empty ERROR_VARIABLE in execute_process

[Roman Wüger]

As an addition:

If I run "C:\Qt\5.6\msvc2015\bin\qmllint.exe test.qml 1> stdout.txt 2> 
stderr.txt"

Then the error is written to stderr.txt.

Regards
Roman

> Am 23.05.2016 um 09:25 schrieb Roman Wüger <roman.wue...@gmx.at>:
> 
> Hello,
> 
> when I run qmllint from the command line to test an error I get:
> 
> C:\Tests>C:\Qt\5.6\msvc2015\bin\qmllint.exe test.qml
> test.qml:1 : Syntax error
> 
> C:\Tests>echo %ERRORLEVEL%
> -1
> 
> C:\Tests>
> 
> 
> If I call this from a CMake script
> 
> execute_process(COMMAND C:/Qt/5.6/msvc2015/bin/qmllint.exe C:/Tests/test.qml
>RESULT_VARIABLE _resVar
>OUTPUT_VARIABLE _outVar
>ERROR_VARIABLE _errVar
>  OUTPUT_STRIP_TRAILING_WHITESPACE
>ERROR_STRIP_TRAILING_WHITESPACE)
> 
> message("_resVar: ${_resVar}")
> message("_outVar: ${_outVar}")
> message("_errVar: ${_errVar}")
> 
> The output is:
> 
> 1>  _resVar: -1
> 1>  _outVar:
> 1>  _errVar:
> 
> It seems that the error pipe isn’t read correctly, because _errVar is empty.
> 
> And hints?
> 
> Regards
> Roman
> 
> -- 
> 
> 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-developers

Re: [CMake] Empty ERROR_VARIABLE in execute_process

[Roman Wüger]

As an addition:

If I run "C:\Qt\5.6\msvc2015\bin\qmllint.exe test.qml 1> stdout.txt 2> 
stderr.txt"

Then the error is written to stderr.txt.

Regards
Roman

> Am 23.05.2016 um 09:25 schrieb Roman Wüger <roman.wue...@gmx.at>:
> 
> Hello,
> 
> when I run qmllint from the command line to test an error I get:
> 
> C:\Tests>C:\Qt\5.6\msvc2015\bin\qmllint.exe test.qml
> test.qml:1 : Syntax error
> 
> C:\Tests>echo %ERRORLEVEL%
> -1
> 
> C:\Tests>
> 
> 
> If I call this from a CMake script
> 
> execute_process(COMMAND C:/Qt/5.6/msvc2015/bin/qmllint.exe C:/Tests/test.qml
>RESULT_VARIABLE _resVar
>OUTPUT_VARIABLE _outVar
>ERROR_VARIABLE _errVar
>  OUTPUT_STRIP_TRAILING_WHITESPACE
>ERROR_STRIP_TRAILING_WHITESPACE)
> 
> message("_resVar: ${_resVar}")
> message("_outVar: ${_outVar}")
> message("_errVar: ${_errVar}")
> 
> The output is:
> 
> 1>  _resVar: -1
> 1>  _outVar:
> 1>  _errVar:
> 
> It seems that the error pipe isn’t read correctly, because _errVar is empty.
> 
> And hints?
> 
> Regards
> Roman
> 
> -- 
> 
> 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] Empty ERROR_VARIABLE in execute_process

[Roman Wüger]

Hello,
 
when I run qmllint from the command line to test an error I get:
 
C:\Tests>C:\Qt\5.6\msvc2015\bin\qmllint.exe test.qml
test.qml:1 : Syntax error
 
C:\Tests>echo %ERRORLEVEL%
-1
 
C:\Tests>
 
 
If I call this from a CMake script
 
execute_process(COMMAND C:/Qt/5.6/msvc2015/bin/qmllint.exe C:/Tests/test.qml
RESULT_VARIABLE _resVar
OUTPUT_VARIABLE _outVar
ERROR_VARIABLE _errVar
  OUTPUT_STRIP_TRAILING_WHITESPACE
ERROR_STRIP_TRAILING_WHITESPACE)
 
message("_resVar: ${_resVar}")
message("_outVar: ${_outVar}")
message("_errVar: ${_errVar}")
 
The output is:
 
1>  _resVar: -1
1>  _outVar:
1>  _errVar:
 
It seems that the error pipe isn’t read correctly, because _errVar is empty.

And hints?

Regards
Roman

-- 

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] Empty ERROR_VARIABLE in execute_process

[Roman Wüger]

Hello,
 
when I run qmllint from the command line to test an error I get:
 
C:\Tests>C:\Qt\5.6\msvc2015\bin\qmllint.exe test.qml
test.qml:1 : Syntax error
 
C:\Tests>echo %ERRORLEVEL%
-1
 
C:\Tests>
 
 
If I call this from a CMake script
 
execute_process(COMMAND C:/Qt/5.6/msvc2015/bin/qmllint.exe C:/Tests/test.qml
RESULT_VARIABLE _resVar
OUTPUT_VARIABLE _outVar
ERROR_VARIABLE _errVar
  OUTPUT_STRIP_TRAILING_WHITESPACE
ERROR_STRIP_TRAILING_WHITESPACE)
 
message("_resVar: ${_resVar}")
message("_outVar: ${_outVar}")
message("_errVar: ${_errVar}")
 
The output is:
 
1>  _resVar: -1
1>  _outVar:
1>  _errVar:
 
It seems that the error pipe isn’t read correctly, because _errVar is empty.

And hints?

Regards
Roman

-- 

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-developers] Windows Phone 10.0 and Windows Phone 8.1 support

[Roman Wüger]

Hi,

I read that CMake has support for those platforms. Is there a way to modify the 
*.appxrecipe file or is there a chance to add files before packaging to an 
*.appx file?

Thanks in advance

Regards
Roman 
-- 

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] Windows Phone 10.0 and Windows Phone 8.1 support

[Roman Wüger]

Hi,

I read that CMake has support for those platforms. Is there a way to modify the 
*.appxrecipe file or is there a chance to add files before packaging to an 
*.appx file?

Thanks in advance

Regards
Roman 
-- 

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] Debug vs Release "install" area

[Roman Wüger]

You could use conditional generator expressions e.g $ with a 
combination of add_custom_command stuff like "${CMAKE_COMMAND} -P 
yourscript.cmake " to handle the rest.

Best Regards
Roman

> Am 12.05.2016 um 22:07 schrieb Scott Aron Bloom :
> 
> Looking for some advice.
>  
> In order to make our Visual Studio debugging environment, as self-contained 
> (and easy to use for the developers) as possible, we use developers must run 
> an install.  We also use the resulting release based Install for our 
> packaging into our installer.
>  
> We change the prefix variable CMAKE_INSTALL_PREFIX, to  
> ${CMAKE_BINARY_DIR}/Install, as well as having a each application call a 
> function that places a .user.vcxproj that sets the PATH appropriately.
>  
> It really works great, except there is one caveat.  VC++ has libraries that 
> are debug vs release dependent, so if your debug build happens to pick up a 
> release DLL (or vice versa) you can (will) be in trouble in random ways.
>  
> Typically, when I change over, I simply delete the install, and re-install.
>  
> Ideally, I would like to know is there any way to set the 
> CMAKE_INSTALL_PREFIX variable separately for debug vs release? If so how?
>  
> A second option, which I thought of…
>  
> Is to generate a file “DEBUG.BUILD.TXT” and then at the START of the 
> installation process, run a script for debug builds, that says if the file 
> doesn’t exist, delete everything and carry on.  If running for a release 
> install, if it DOES exist delete and carry on.
>  
>  
> Any thoughts on this?
> 
> Thanks
> 
> Scott
>  
>  
> -- 
> 
> 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 and PackageMaker

[Roman Wüger]

I think it is ok for the most of the use cases.
But what I miss are the signing options:

e.g: productbuild --component "FULLPATH_TO_OUTPUTDIR" /Applications --sign 
"DEVELOPER_CERTIFICATE" --product ".../Info.plist" MyPackage.pkg

Best regards
Roman

> Am 05.04.2016 um 03:12 schrieb clin...@elemtech.com:
> 
> Hi,
> 
> I have updated the patch I sent before and you can find some new code here:
> https://github.com/clintonstimpson/CMake/commits/productbuild
> 
> To help, perhaps you can review and test it.
> Or help in other ways you think it needs.
> 
> I have done minimal testing.  This includes making sure CMake's test suite 
> passes with this generator.
> And running those generated pkg files manually to test them.
> 
> Perhaps after a couple reviews, we can start thinking about merging into 
> CMake.
> 
> Thanks,
> Clint
> 
> 
> - On Dec 21, 2015, at 11:56 PM, Roman Wüger <roman.wue...@gmx.at> wrote:
> Is there anything I can do to support?
> 
> Best regards 
> 
> Am 11.12.2015 um 20:17 schrieb robert.bielik <robert.bie...@dirac.se>:
> 
> Dear Clint,
>  
> Thank you! Will certainly start with that as a base :)
>  
> Regards 
> /R
>  
> -- Ursprungligt meddelande--
> Från:
> Datum: fre, 11 dec 2015 20:12
> Till: Robert Bielik;
> Kopia: Attila Krasznahorkay;cmake;
> Ämne:Re: [CMake] CPack and PackageMaker
>  
> If you are interested, attached is some code I started a couple years ago but 
> never finished, nor did I do much testing.
> Perhaps that'll help, or maybe you'll find a better way.
> 
> Clint
> 
> - On Dec 11, 2015, at 9:50 AM, Robert Bielik robert.bie...@dirac.se wrote:
> 
> > Dear Attila,
> > 
> > Ok, been struggling getting an installation package to work with the
> > pkgbuild/productbild tools, so I think I got the gist of what needs to
> > be done, at least to get something going :)
> > 
> > Regards
> > /R
> > 
> > Den 2015-12-11 kl. 17:47, skrev Attila Krasznahorkay:
> >> Hi Robert,
> >>
> >> I'm afraid that the sad situation is that nobody has done this yet, or is
> >> working on it at the moment.
> >>
> >> I'm absolutely sure that if you can help with this by any amount, that 
> >> will be
> >> most welcome by the CMake developers. It will certainly be most welcome by 
> >> me,
> >> as I've been disappointed by the lack of this support as well. (But
> >> unfortunately can't spare the time to help out in writing this CPack
> >> generator.)
> >>
> >> Cheers,
> >>   Attila
> >>
> >>> On 11 Dec 2015, at 17:44, Robert Bielik  wrote:
> >>>
> >>> Really ? No one ? :)
> >>>
> >>> So it's ok to go ahead and start create a new one ? ;)
> >>>
> >>> Rgds,
> >>> /R
> >>>
> >>> Den 2015-12-09 kl. 16:56, skrev Robert Bielik:
> >>>> Mac OSX:
> >>>>
> >>>> Since PackageMaker has been deprecated by Apple, the new tools to use are
> >>>> pkgbuild [1] and productbuild [2].
> >>>>
> >>>> Simple question: Is there any work being done by the CMake community on 
> >>>> a new OS
> >>>> X CPack backend to support the above tools ?
> >>>>
> >>>> Regards
> >>>> /Robert
> >>>> [1]
> >>>> https://developer.apple.com/library/mac/documentation/Darwin/Reference/ManPages/man1/pkgbuild.1.html
> >>>> [2]
> >>>> https://developer.apple.com/library/mac/documentation/Darwin/Reference/ManPages/man1/productbuild.1.html
> >>>>
> >>> --
> >>>
> >>> 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/list

[CMake] CLang error when building iOS bundle

[Roman Wüger]

Hello list,

 

I got the following error when linking the iOS bundle:

clang: error: cannot specify -o when generating multiple output files

 

I didn’t found anything about the error in the internet, so maybe someone
has already solved such error?

Does any one have a hint what could be wrong?

 

Thank you very much in advance

 

Best Regards

Roman

 

P.S.: Here is the last output:

 

CompileC
/Users/nbuild/workspace/BuildSlave/jenkins/workspace/SimpleiPhoneApp-macos-i
OS-debug/build/appQml/SimpleApp.build/Debug-iphoneos/SimpleApp.build/Objects
-normal/armv7/main.o appQml/main.cpp normal armv7 c++
com.apple.compilers.llvm.clang.1_0.compiler

cd
/Users/nbuild/workspace/BuildSlave/jenkins/workspace/SimpleiPhoneApp-macos-i
OS-debug/source

export LANG=en_US.US-ASCII

export
PATH="/Applications/Xcode_7_3_1.app/Contents/Developer/Platforms/iPhoneOS.pl
atform/Developer/usr/bin:/Applications/Xcode_7_3_1.app/Contents/Developer/us
r/bin::/bin:/opt/Externals:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/opt
/X11/bin:/Applications/Server.app/Contents/ServerRoot/usr/bin:/Applications/
Server.app/Contents/ServerRoot/usr/sbin"

 
/Applications/Xcode_7_3_1.app/Contents/Developer/Toolchains/XcodeDefault.xct
oolchain/usr/bin/clang -x c++ -arch armv7 -fmessage-length=233
-fdiagnostics-show-note-include-stack -fmacro-backtrace-limit=0
-fcolor-diagnostics -std=c++11 -stdlib=libc++ -Wno-trigraphs
-fpascal-strings -O0 -Wno-missing-field-initializers -Wno-missing-prototypes
-Wno-return-type -Wno-non-virtual-dtor -Wno-overloaded-virtual
-Wno-exit-time-destructors -Wno-missing-braces -Wparentheses -Wswitch
-Wno-unused-function -Wno-unused-label -Wno-unused-parameter
-Wno-unused-variable -Wunused-value -Wno-empty-body -Wno-uninitialized
-Wno-unknown-pragmas -Wno-shadow -Wno-four-char-constants -Wno-conversion
-Wno-constant-conversion -Wno-int-conversion -Wno-bool-conversion
-Wno-enum-conversion -Wno-shorten-64-to-32 -Wno-newline-eof
-Wno-c++11-extensions -DCMAKE_INTDIR=\"Debug-iphoneos\" -DQT_QML_LIB
-DQT_NETWORK_LIB -DQT_CORE_LIB -DQT_QUICK_LIB -DQT_GUI_LIB -DQT_WIDGETS_LIB
-DPLATFORM_IS_IOS -DQT_NO_CAST_FROM_ASCII -DQT_NO_CAST_TO_ASCII
-DQT_NO_CAST_TO_BYTEARRAY -DWSD_HAS_GENERIC_HIGHLIGHTER -DNOMINMAX
-DQT_XML_LIB -isysroot
/Applications/Xcode_7_3_1.app/Contents/Developer/Platforms/iPhoneOS.platform
/Developer/SDKs/iPhoneOS9.3.sdk -fstrict-aliasing -Wdeprecated-declarations
-Winvalid-offsetof -miphoneos-version-min=9.3 -Wno-sign-conversion
-I/Users/nbuild/workspace/BuildSlave/jenkins/workspace/SimpleiPhoneApp-macos
-iOS-debug/build/bin/Debug/include
-I/Users/nbuild/workspace/BuildSlave/jenkins/workspace/SimpleiPhoneApp-macos
-iOS-debug/build/appQml
-I/Users/nbuild/workspace/BuildSlave/jenkins/workspace/SimpleiPhoneApp-macos
-iOS-debug/source/appQml
-I/Users/nbuild/workspace/BuildSlave/jenkins/workspace/SimpleiPhoneApp-macos
-iOS-debug/build/cmake/cmake_wsd
-I/Users/nbuild/workspace/BuildSlave/jenkins/workspace/SimpleiPhoneApp-macos
-iOS-debug/build/cmake -I/opt/Qt/5.6/ios/include
-I/opt/Qt/5.6/ios/include/QtWidgets -I/opt/Qt/5.6/ios/include/QtGui
-I/opt/Qt/5.6/ios/include/QtCore -I/opt/Qt/5.6/ios/mkspecs/macx-ios-clang
-I/Users/nbuild/workspace/BuildSlave/jenkins/workspace/SimpleiPhoneApp-macos
-iOS-debug/source/libraries/gtest/include
-I/Users/nbuild/workspace/BuildSlave/jenkins/workspace/SimpleiPhoneApp-macos
-iOS-debug/source/libraries
-I/Users/nbuild/workspace/BuildSlave/jenkins/workspace/SimpleiPhoneApp-macos
-iOS-debug/source/libraries/Screens
-I/Users/nbuild/workspace/BuildSlave/jenkins/workspace/SimpleiPhoneApp-macos
-iOS-debug/source/libraries/QmlTools
-I/Users/nbuild/workspace/BuildSlave/jenkins/workspace/SimpleiPhoneApp-macos
-iOS-debug/source/libraries/Tools
-I/Users/nbuild/workspace/BuildSlave/jenkins/workspace/SimpleiPhoneApp-macos
-iOS-debug/source/libraries/Utilities/libraries/GuiTools
-I/Users/nbuild/workspace/BuildSlave/jenkins/workspace/SimpleiPhoneApp-macos
-iOS-debug/source/libraries/Utilities/libraries/Tools
-I/Users/nbuild/workspace/BuildSlave/jenkins/workspace/SimpleiPhoneApp-macos
-iOS-debug/source/libraries/Utilities/libraries/QtTools
-I/Users/nbuild/workspace/BuildSlave/jenkins/workspace/SimpleiPhoneApp-macos
-iOS-debug/source/interfaces
-I/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Dev
eloper/SDKs/iPhoneOS9.3.sdk/System/Library/Frameworks/CoreFoundation.framewo
rk/Headers
-I/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Dev
eloper/SDKs/iPhoneOS9.3.sdk/System/Library/Frameworks/CoreGraphics.framework
/Headers
-I/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Dev
eloper/SDKs/iPhoneOS9.3.sdk/System/Library/Frameworks/CoreText.framework/Hea
ders
-I/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Dev
eloper/SDKs/iPhoneOS9.3.sdk/System/Library/Frameworks/Foundation.framework/H
eaders
-I/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Dev

[cmake-developers] CLang error when building iOS bundle

[Roman Wüger]

Hello list,

 

I got the following error when linking the iOS bundle:

clang: error: cannot specify -o when generating multiple output files

 

I didn’t found anything about the error in the internet, so maybe someone
has already solved such error?

Does any one have a hint what could be wrong?

 

Thank you very much in advance

 

Best Regards

Roman

 

P.S.: Here is the last output:

 

CompileC
/Users/nbuild/workspace/BuildSlave/jenkins/workspace/SimpleiPhoneApp-macos-i
OS-debug/build/appQml/SimpleApp.build/Debug-iphoneos/SimpleApp.build/Objects
-normal/armv7/main.o appQml/main.cpp normal armv7 c++
com.apple.compilers.llvm.clang.1_0.compiler

cd
/Users/nbuild/workspace/BuildSlave/jenkins/workspace/SimpleiPhoneApp-macos-i
OS-debug/source

export LANG=en_US.US-ASCII

export
PATH="/Applications/Xcode_7_3_1.app/Contents/Developer/Platforms/iPhoneOS.pl
atform/Developer/usr/bin:/Applications/Xcode_7_3_1.app/Contents/Developer/us
r/bin::/bin:/opt/Externals:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/opt
/X11/bin:/Applications/Server.app/Contents/ServerRoot/usr/bin:/Applications/
Server.app/Contents/ServerRoot/usr/sbin"

 
/Applications/Xcode_7_3_1.app/Contents/Developer/Toolchains/XcodeDefault.xct
oolchain/usr/bin/clang -x c++ -arch armv7 -fmessage-length=233
-fdiagnostics-show-note-include-stack -fmacro-backtrace-limit=0
-fcolor-diagnostics -std=c++11 -stdlib=libc++ -Wno-trigraphs
-fpascal-strings -O0 -Wno-missing-field-initializers -Wno-missing-prototypes
-Wno-return-type -Wno-non-virtual-dtor -Wno-overloaded-virtual
-Wno-exit-time-destructors -Wno-missing-braces -Wparentheses -Wswitch
-Wno-unused-function -Wno-unused-label -Wno-unused-parameter
-Wno-unused-variable -Wunused-value -Wno-empty-body -Wno-uninitialized
-Wno-unknown-pragmas -Wno-shadow -Wno-four-char-constants -Wno-conversion
-Wno-constant-conversion -Wno-int-conversion -Wno-bool-conversion
-Wno-enum-conversion -Wno-shorten-64-to-32 -Wno-newline-eof
-Wno-c++11-extensions -DCMAKE_INTDIR=\"Debug-iphoneos\" -DQT_QML_LIB
-DQT_NETWORK_LIB -DQT_CORE_LIB -DQT_QUICK_LIB -DQT_GUI_LIB -DQT_WIDGETS_LIB
-DPLATFORM_IS_IOS -DQT_NO_CAST_FROM_ASCII -DQT_NO_CAST_TO_ASCII
-DQT_NO_CAST_TO_BYTEARRAY -DWSD_HAS_GENERIC_HIGHLIGHTER -DNOMINMAX
-DQT_XML_LIB -isysroot
/Applications/Xcode_7_3_1.app/Contents/Developer/Platforms/iPhoneOS.platform
/Developer/SDKs/iPhoneOS9.3.sdk -fstrict-aliasing -Wdeprecated-declarations
-Winvalid-offsetof -miphoneos-version-min=9.3 -Wno-sign-conversion
-I/Users/nbuild/workspace/BuildSlave/jenkins/workspace/SimpleiPhoneApp-macos
-iOS-debug/build/bin/Debug/include
-I/Users/nbuild/workspace/BuildSlave/jenkins/workspace/SimpleiPhoneApp-macos
-iOS-debug/build/appQml
-I/Users/nbuild/workspace/BuildSlave/jenkins/workspace/SimpleiPhoneApp-macos
-iOS-debug/source/appQml
-I/Users/nbuild/workspace/BuildSlave/jenkins/workspace/SimpleiPhoneApp-macos
-iOS-debug/build/cmake/cmake_wsd
-I/Users/nbuild/workspace/BuildSlave/jenkins/workspace/SimpleiPhoneApp-macos
-iOS-debug/build/cmake -I/opt/Qt/5.6/ios/include
-I/opt/Qt/5.6/ios/include/QtWidgets -I/opt/Qt/5.6/ios/include/QtGui
-I/opt/Qt/5.6/ios/include/QtCore -I/opt/Qt/5.6/ios/mkspecs/macx-ios-clang
-I/Users/nbuild/workspace/BuildSlave/jenkins/workspace/SimpleiPhoneApp-macos
-iOS-debug/source/libraries/gtest/include
-I/Users/nbuild/workspace/BuildSlave/jenkins/workspace/SimpleiPhoneApp-macos
-iOS-debug/source/libraries
-I/Users/nbuild/workspace/BuildSlave/jenkins/workspace/SimpleiPhoneApp-macos
-iOS-debug/source/libraries/Screens
-I/Users/nbuild/workspace/BuildSlave/jenkins/workspace/SimpleiPhoneApp-macos
-iOS-debug/source/libraries/QmlTools
-I/Users/nbuild/workspace/BuildSlave/jenkins/workspace/SimpleiPhoneApp-macos
-iOS-debug/source/libraries/Tools
-I/Users/nbuild/workspace/BuildSlave/jenkins/workspace/SimpleiPhoneApp-macos
-iOS-debug/source/libraries/Utilities/libraries/GuiTools
-I/Users/nbuild/workspace/BuildSlave/jenkins/workspace/SimpleiPhoneApp-macos
-iOS-debug/source/libraries/Utilities/libraries/Tools
-I/Users/nbuild/workspace/BuildSlave/jenkins/workspace/SimpleiPhoneApp-macos
-iOS-debug/source/libraries/Utilities/libraries/QtTools
-I/Users/nbuild/workspace/BuildSlave/jenkins/workspace/SimpleiPhoneApp-macos
-iOS-debug/source/interfaces
-I/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Dev
eloper/SDKs/iPhoneOS9.3.sdk/System/Library/Frameworks/CoreFoundation.framewo
rk/Headers
-I/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Dev
eloper/SDKs/iPhoneOS9.3.sdk/System/Library/Frameworks/CoreGraphics.framework
/Headers
-I/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Dev
eloper/SDKs/iPhoneOS9.3.sdk/System/Library/Frameworks/CoreText.framework/Hea
ders
-I/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Dev
eloper/SDKs/iPhoneOS9.3.sdk/System/Library/Frameworks/Foundation.framework/H
eaders
-I/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Dev

Re: [cmake-developers] Patch for BundleUtilities to ignore specified files

[Roman Wüger]

Hello Brad,

attached is an updated patch.

Regards
Roman



0001-BundleUtilities-Add-optional-parameter-to-ignore-spe.patch
Description: Binary data


> Am 18.04.2016 um 17:28 schrieb Brad King <brad.k...@kitware.com>:
> 
>> On 04/18/2016 10:20 AM, Roman Wüger wrote:
>> attached is a patch with which files can be specified which should not be 
>> resolved.
> 
> Thanks.  Please include a documentation update too.
> 
> -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

Re: [CMake] Patch for BundleUtilities to ignore specified files

[Roman Wüger]

Hello Brad,

attached is an updated patch.

Regards
Roman



0001-BundleUtilities-Add-optional-parameter-to-ignore-spe.patch
Description: Binary data


> Am 18.04.2016 um 17:28 schrieb Brad King <brad.k...@kitware.com>:
> 
>> On 04/18/2016 10:20 AM, Roman Wüger wrote:
>> attached is a patch with which files can be specified which should not be 
>> resolved.
> 
> Thanks.  Please include a documentation update too.
> 
> -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

[CMake] Patch for BundleUtilities to ignore specified files

[Roman Wüger]

Hello,

attached is a patch with which files can be specified which should not be 
resolved.

Best regards
Roman




0001-BundleUtilities-Add-optional-parameter-to-ignore-spe.patch
Description: Binary data

-- 

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] Patch for BundleUtilities to ignore specified files

[Roman Wüger]

Hello,

attached is a patch with which files can be specified which should not be 
resolved.

Best regards
Roman




0001-BundleUtilities-Add-optional-parameter-to-ignore-spe.patch
Description: Binary data

-- 

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] [cmake-developers] CPack includes WINTRUST.DLL

[Roman Wüger]

Yes, i use fixup_bundle.
Is there a better alternative?

Regards

> Am 11.03.2016 um 14:25 schrieb Brad King <brad.k...@kitware.com>:
> 
>> On 03/11/2016 02:41 AM, Roman Wüger wrote:
>> i noticed that CPack includes the WINTRUST.dll when I
>> generate an NSIS installer.
>> How can I avoid this?
>> I have no dependencies to this library.
> 
> CMake has no mention of that dll in its source so we are not adding
> the dependency explicitly anywhere.  Are you using fixup_bundle?
> That may somehow think this dependency is needed.
> 
> -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

Re: [cmake-developers] CPack includes WINTRUST.DLL

[Roman Wüger]

Yes, i use fixup_bundle.
Is there a better alternative?

Regards

> Am 11.03.2016 um 14:25 schrieb Brad King <brad.k...@kitware.com>:
> 
>> On 03/11/2016 02:41 AM, Roman Wüger wrote:
>> i noticed that CPack includes the WINTRUST.dll when I
>> generate an NSIS installer.
>> How can I avoid this?
>> I have no dependencies to this library.
> 
> CMake has no mention of that dll in its source so we are not adding
> the dependency explicitly anywhere.  Are you using fixup_bundle?
> That may somehow think this dependency is needed.
> 
> -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-developers] CPack includes WINTRUST.DLL

[Roman Wüger]

Hello,

i noticed that CPack includes the WINTRUST.dll when I generate an NSIS 
installer.
How can I avoid this?
I have no dependencies to this library.

The problem is that the application doesn't work on older Windows versions with 
this dll. If I remove the dll after installation then everything is working 
fine.

Thanks in advance

Best regards 
Romab
-- 

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] CPack includes WINTRUST.DLL

[Roman Wüger]

Hello,

i noticed that CPack includes the WINTRUST.dll when I generate an NSIS 
installer.
How can I avoid this?
I have no dependencies to this library.

The problem is that the application doesn't work on older Windows versions with 
this dll. If I remove the dll after installation then everything is working 
fine.

Thanks in advance

Best regards 
Romab
-- 

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] Deploy Qt based App to WindowsStore using CMake

[Roman Wüger]

Do you have the developer mode under Windows 10 activated?
Do you have registered your app (Add-AppxPackage -Register AppxManifest.xml)?
See https://doc-snapshots.qt.io/qt5-5.6/winrt-support.html#building-from-source

Best regards
Roman 

> Am 03.03.2016 um 16:53 schrieb Nikita Barawade 
> :
> 
> 
> 
> Hi,
> 
> I have application based on Qt UI . My aim is to convert this app to run on 
> WindowsStore.
> 
> Project has been converted to Universal Windows and building  without errors.
> Project is using Qt version 5.6 for WInRT.
> Here is a command used ,
> 
> cmake .. -G "Visual Studio 14 2015" -DCMAKE_SYSTEM_NAME=WindowsStore 
> -DCMAKE_SYSTEM_VERSION=10.0
> 
> Target Architecture is x86. 
> 
> The problem comes when I try to deploy it on Local or remote machine.
> 
>  
>  i.e Unable to activate Windows Store app ...
> The sampleApp.exe process started but the activation request failed with 
> error "The app didn't start"
> 
> I have already gone throgh these links :
> http://stackoverflow.com/questions/13404315/unable-to-activate-windows-store-app
> http://stackoverflow.com/questions/19847563/unable-to-activate-windows-store-app-the-app-didnt-start
> http://blogs.technet.com/b/askperf/archive/2013/10/11/what-to-do-if-your-windows-8-modern-app-fails-to-start.aspx
> 
> c# - Unable to activate windows store app the app didn't ...
> stackoverflow.com
> First of all I would like to say that I already tried all the solutions I 
> could find on the internet, including Unable to Activate Windows Store App I 
> recently ...
> 
> 
> http://irisclasson.com/2012/11/04/problem-unable-to-activate-windows-store-app-the-app1-exe-process-started-but-the-activation-request-failed-with-error-the-app-didnt-start/
> 
> Problem: Unable to activate Windows Store app: The App1 ...
> irisclasson.com
> Thanks, this really helped! The other solutions I found weren’t applicable 
> for me, but this was just what I needed.
> 
> 
>  
> visual studio - Unable to Activate Windows Store App ...
> stackoverflow.com
> I installed a retail version of Windows 8 Pro. I downloaded and installed 
> Visual Studio Express 2012. I asked for and received a developers 
> certificate. Then I tried ...
> 
> 
> If anyone has tried it before ? Please guide.
> 
> 
> Regards,
> Nikita
> *
>  eInfochips Business Disclaimer: This e-mail message and all attachments 
> transmitted with it are intended solely for the use of the addressee and may 
> contain legally privileged and confidential information. If the reader of 
> this message is not the intended recipient, or an employee or agent 
> responsible for delivering this message to the intended recipient, you are 
> hereby notified that any dissemination, distribution, copying, or other use 
> of this message or its attachments is strictly prohibited. If you have 
> received this message in error, please notify the sender immediately by 
> replying to this message and please delete it from your computer. Any views 
> expressed in this message are those of the individual sender unless otherwise 
> stated. Company has taken enough precautions to prevent the spread of 
> viruses. However the company accepts no liability for any damage caused by 
> any virus transmitted by this email. 
> *
> -- 
> 
> 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] Unit Test App (Universal Windows)

[Roman Wüger]

Hello,

does anyone successfully created a unit test for Windows 10 Universal?

My current situation is that the unit tests are running if building for 
desktop. 

But if I try to build for winrt/universal/Windows 10 store then the tests 
aren't executed.

When I create a unit test for Windows universal under visual studio then the 
tests are working.

Thanks in advance 
Best regards 
Roman 
-- 

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] Run program/command before test

[Roman Wüger]

Hi Nils,

great thanks.

Regards
Roman 

> Am 17.02.2016 um 09:09 schrieb Nils Gladitz <nilsglad...@gmail.com>:
> 
>> On 17.02.2016 07:58, Roman Wüger wrote:
>> Ok thanks
>> 
>> Would it be an opinion to have a COMMAND parameter for the add_test function 
>> like execute_process where every COMMAND must return the exit code and this 
>> would be ored?
>> 
>> add_test(MyTest COMMAND myserver --port 80
>>   COMMAND mytest
>>   COMMAND myserver --graceful-shutdown)
>> 
>> Or
>> 
>> add_test(MyTest PRE_COMMAND myserver --port 80
>>   COMMAND mytest
>>   POST_COMMAND myserver --graceful-shutdown)
> 
> What you could already do is wrap your test in a cmake script.
> 
> E.g.
> 
>add_test(NAME MyTest
>COMMAND ${CMAKE_COMMAND} -DACTUAL_TEST=$ -P 
> ${CMAKE_CURRENT_SOURCE_DIR}/mywrapper.cmake
>)
> 
> Where mywrapper.cmake could do something like:
> 
>execute_process(COMMAND mysever --port 80 ...)
> 
>execute_process(COMMAND ${ACTUAL_TEST} )
> 
>execute_process(COMMAND mysever --graceful-shutdown)
> 
> To have the test fail you could call message(FATAL_ERROR "...")
> 
> For this to work myserver would have to daemonize/fork (but I assume that is 
> the case given your example).
> 
> Nils
-- 

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] Run program/command before test

[Roman Wüger]

Ok thanks

Would it be an opinion to have a COMMAND parameter for the add_test function 
like execute_process where every COMMAND must return the exit code and this 
would be ored?

add_test(MyTest COMMAND myserver --port 80
  COMMAND mytest 
  COMMAND myserver --graceful-shutdown)

Or

add_test(MyTest PRE_COMMAND myserver --port 80
  COMMAND mytest 
  POST_COMMAND myserver --graceful-shutdown)

Best Regards
Roman

> Am 16.02.2016 um 16:49 schrieb Brad King <brad.k...@kitware.com>:
> 
>> On 02/16/2016 07:17 AM, Roman Wüger wrote:
>> Is it possible with CMake >= 3.4.0 to run a program/command before the
>> test and another program after the test was run?
>> 
>> The meaning of that would be, that I want to start a small server
>> program and run the "client" test. After the test was finished,
>> kill the process of the server program or do a graceful shutdown of it.
> 
> There is currently no builtin feature for that.  Other than a few
> test output matching properties, ctest always expects the process
> to be independent and report results via its exit code.
> 
> -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-developers] Run program/command before test

[Roman Wüger]

Hello,

Is it possible with CMake >= 3.4.0 to run a program/command before the test and 
another program after the test was run?

The meaning of that would be, that I want to start a small server program and 
run the "client" test. After the test was finished, kill the process of the 
server program or do a graceful shutdown of it.

Thanks in advance

Best Regards
Roman
-- 

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-developers] CMake Windows 10 Store App

[Roman Wüger]

Hello,

I use CMAKE_SYSTEM_NAME:STRING=WindowsStore and CMAKE_SYSTEM_VERSION=10.0 to 
build an universal app. However, does CMake also support *.appxupload and such 
bundles? And if so, how?

Thanks in advance
Best regards
Roman
-- 

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] CMake can't generate Windows 10 store app with VS2015 Update 1

[Roman Wüger]

Ok, I've installed all options from the SDK 
(https://dev.windows.com/en-us/downloads/windows-10-sdk)
but it doesn't solve the issue.

Is there something other to install?
What things does CMake require?

Best Regards
Roman

> Am 05.02.2016 um 14:54 schrieb Roman Wüger <roman.wue...@gmx.at>:
> 
> Hello,
>  
> I’ve Installed Windows 10 Professional with VS2015 Update 1 and CMake 3.4.3.
> When I run configure:
>  
> cmake -G "Visual Studio 14 Win64" -DCMAKE_SYSTEM_NAME:STRING=WindowsStore 
> -DCMAKE_SYSTEM_VERSION:STRING=10.0 ..\source
>  
> Then I became the following error message:
>  
> CMake Error at CMakeLists.txt:3 (PROJECT):
>   A Windows Store component with CMake requires both the Windows Desktop SDK
>   as well as the Windows Store '10.0' SDK.  Please make sure that you have
>   both installed
>  
>  
> -- Configuring incomplete, errors occurred!
>  
> Did I need something additional to get it working?
>  
> Thanks in advance
>  
> Best Regards
> Roman
-- 

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-developers] CMake can't generate Windows 10 store app with VS2015 Update 1

[Roman Wüger]

Hello,

 

I’ve Installed Windows 10 Professional with VS2015 Update 1 and CMake 3.4.3.

When I run configure: 

 

cmake -G "Visual Studio 14 Win64" -DCMAKE_SYSTEM_NAME:STRING=WindowsStore
-DCMAKE_SYSTEM_VERSION:STRING=10.0 ..\source

 

Then I became the following error message:

 

CMake Error at CMakeLists.txt:3 (PROJECT):

  A Windows Store component with CMake requires both the Windows Desktop SDK

  as well as the Windows Store '10.0' SDK.  Please make sure that you have

  both installed

 

 

-- Configuring incomplete, errors occurred!

 

Did I need something additional to get it working?

 

Thanks in advance

 

Best Regards

Roman



smime.p7s
Description: S/MIME cryptographic signature
-- 

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] CPack and PackageMaker

[Roman Wüger]

@Brad, @Clinton: Could we add this feature into CMake 3.5.0, because on newer 
Mac OS systems the package maker is already deprecated and for those we could 
use the productbuild instead.

Thanks in advance

Best Regards
Roman 

> Am 22.12.2015 um 07:56 schrieb Roman Wüger <roman.wue...@gmx.at>:
> 
> Is there anything I can do to support?
> 
> Best regards 
> 
>> Am 11.12.2015 um 20:17 schrieb robert.bielik <robert.bie...@dirac.se>:
>> 
>> Dear Clint,
>>  
>> Thank you! Will certainly start with that as a base :)
>>  
>> Regards 
>> /R
>>  
>> -- Ursprungligt meddelande--
>> Från:
>> Datum: fre, 11 dec 2015 20:12
>> Till: Robert Bielik;
>> Kopia: Attila Krasznahorkay;cmake;
>> Ämne:Re: [CMake] CPack and PackageMaker
>>  
>> If you are interested, attached is some code I started a couple years ago 
>> but never finished, nor did I do much testing.
>> Perhaps that'll help, or maybe you'll find a better way.
>> 
>> Clint
>> 
>> - On Dec 11, 2015, at 9:50 AM, Robert Bielik robert.bie...@dirac.se 
>> wrote:
>> 
>> > Dear Attila,
>> > 
>> > Ok, been struggling getting an installation package to work with the
>> > pkgbuild/productbild tools, so I think I got the gist of what needs to
>> > be done, at least to get something going :)
>> > 
>> > Regards
>> > /R
>> > 
>> > Den 2015-12-11 kl. 17:47, skrev Attila Krasznahorkay:
>> >> Hi Robert,
>> >>
>> >> I'm afraid that the sad situation is that nobody has done this yet, or is
>> >> working on it at the moment.
>> >>
>> >> I'm absolutely sure that if you can help with this by any amount, that 
>> >> will be
>> >> most welcome by the CMake developers. It will certainly be most welcome 
>> >> by me,
>> >> as I've been disappointed by the lack of this support as well. (But
>> >> unfortunately can't spare the time to help out in writing this CPack
>> >> generator.)
>> >>
>> >> Cheers,
>> >>   Attila
>> >>
>> >>> On 11 Dec 2015, at 17:44, Robert Bielik  wrote:
>> >>>
>> >>> Really ? No one ? :)
>> >>>
>> >>> So it's ok to go ahead and start create a new one ? ;)
>> >>>
>> >>> Rgds,
>> >>> /R
>> >>>
>> >>> Den 2015-12-09 kl. 16:56, skrev Robert Bielik:
>> >>>> Mac OSX:
>> >>>>
>> >>>> Since PackageMaker has been deprecated by Apple, the new tools to use 
>> >>>> are
>> >>>> pkgbuild [1] and productbuild [2].
>> >>>>
>> >>>> Simple question: Is there any work being done by the CMake community on 
>> >>>> a new OS
>> >>>> X CPack backend to support the above tools ?
>> >>>>
>> >>>> Regards
>> >>>> /Robert
>> >>>> [1]
>> >>>> https://developer.apple.com/library/mac/documentation/Darwin/Reference/ManPages/man1/pkgbuild.1.html
>> >>>> [2]
>> >>>> https://developer.apple.com/library/mac/documentation/Darwin/Reference/ManPages/man1/productbuild.1.html
>> >>>>
>> >>> --
>> >>>
>> >>> 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 

Re: [CMake] How to include config.h.in in VS project

[Roman Wüger]

Hi,

You must add those sources to add_executable/add_library as well.

Wish you a happy new year.

Best regards 
Roman

> Am 29.12.2015 um 09:53 schrieb Mauro Ziliani :
> 
> Hi all.
> I'm using CMake 3.4.1 for my projects.
> I'm working with Visual studio 10 2010 express and wxFormBuilder 
> I'd like to include config.h.in and the wxFormBuilder projects (which has 
> .fbp extension) in source_group.
> 
> In CMakeLists.txt i put
> 
> ...
> 
> source_group("FormBiulder FBP" FILES main.fbp)
> source_group("Config IN" FILES config.h.in)
> 
> But when I generate the final solution for visual studio the tree project has 
> not the group I define.
> 
> It seems the problem is the extestion .fbp or .in. that Cmake ignores
> 
> How can I include .in e .fbp extensions has wel-known extension to put in the 
> vcxproject list?
> 
> Best regards, 
>Mauro
> -- 
> 
> 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 and PackageMaker

[Roman Wüger]

Is there anything I can do to support?

Best regards 

> Am 11.12.2015 um 20:17 schrieb robert.bielik :
> 
> Dear Clint,
>  
> Thank you! Will certainly start with that as a base :)
>  
> Regards 
> /R
>  
> -- Ursprungligt meddelande--
> Från:
> Datum: fre, 11 dec 2015 20:12
> Till: Robert Bielik;
> Kopia: Attila Krasznahorkay;cmake;
> Ämne:Re: [CMake] CPack and PackageMaker
>  
> If you are interested, attached is some code I started a couple years ago but 
> never finished, nor did I do much testing.
> Perhaps that'll help, or maybe you'll find a better way.
> 
> Clint
> 
> - On Dec 11, 2015, at 9:50 AM, Robert Bielik robert.bie...@dirac.se wrote:
> 
> > Dear Attila,
> > 
> > Ok, been struggling getting an installation package to work with the
> > pkgbuild/productbild tools, so I think I got the gist of what needs to
> > be done, at least to get something going :)
> > 
> > Regards
> > /R
> > 
> > Den 2015-12-11 kl. 17:47, skrev Attila Krasznahorkay:
> >> Hi Robert,
> >>
> >> I'm afraid that the sad situation is that nobody has done this yet, or is
> >> working on it at the moment.
> >>
> >> I'm absolutely sure that if you can help with this by any amount, that 
> >> will be
> >> most welcome by the CMake developers. It will certainly be most welcome by 
> >> me,
> >> as I've been disappointed by the lack of this support as well. (But
> >> unfortunately can't spare the time to help out in writing this CPack
> >> generator.)
> >>
> >> Cheers,
> >>   Attila
> >>
> >>> On 11 Dec 2015, at 17:44, Robert Bielik  wrote:
> >>>
> >>> Really ? No one ? :)
> >>>
> >>> So it's ok to go ahead and start create a new one ? ;)
> >>>
> >>> Rgds,
> >>> /R
> >>>
> >>> Den 2015-12-09 kl. 16:56, skrev Robert Bielik:
>  Mac OSX:
> 
>  Since PackageMaker has been deprecated by Apple, the new tools to use are
>  pkgbuild [1] and productbuild [2].
> 
>  Simple question: Is there any work being done by the CMake community on 
>  a new OS
>  X CPack backend to support the above tools ?
> 
>  Regards
>  /Robert
>  [1]
>  https://developer.apple.com/library/mac/documentation/Darwin/Reference/ManPages/man1/pkgbuild.1.html
>  [2]
>  https://developer.apple.com/library/mac/documentation/Darwin/Reference/ManPages/man1/productbuild.1.html
> 
> >>> --
> >>>
> >>> 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
> -- 
> 
> 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


smime.p7s
Description: S/MIME cryptographic signature
-- 

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 

Re: [CMake] C++11 flag not being added

[Roman Wüger]

You can use CMake 3.x on older systems. Write platform checks for specific 
C++11 features and implement "old" style code if the C++11 features (e.g. 
lambdas) are not available.

Use https://cmake.org/cmake/help/v3.1/prop_gbl/CMAKE_CXX_KNOWN_FEATURES.html 
and 
https://cmake.org/cmake/help/v3.1/module/WriteCompilerDetectionHeader.html?highlight=compiler%20detection%20header#module:WriteCompilerDetectionHeader
 to detect if your compiler supports your implementation.

Best Regards


> Am 16.10.2015 um 14:09 schrieb Hendrik Sattler :
> 
> 
> 
> Am 16. Oktober 2015 13:38:27 MESZ, schrieb Petr Bena :
>> By stable you mean Jessie that was recently released and is almost
>> nowhere in production yet? :)
>> 
>> On my debian server:
>> 
>> $ cmake --version
>> cmake version 2.8.9
>> 
>> On one of wikimedia's ubuntu servers (the newer ones):
>> 
>> $ cmake --version
>> cmake version 2.8.12.2
>> 
>> On travis-ci cmake is about 2.8.7 and on ubuntu PPA builder it's
>> probably same.
>> 
>> And we aren't even talking about 3.0, but 3.1 or newer. One would need
>> to be truly naive to expect newer version on some stable production
>> systems, that usually run well established older software (eg.
>> majority of them do).
>> 
>> On my dev PC I have last CMake of course, but I need to be able to
>> compile on other systems as well :)
>> 
>> This code is meant to be cross-platform and buildable on most of
>> supported OS'es, even on older versions. I sincerely hate programs
>> that requires extremely latest versions of tools or libraries for them
>> to work, because these are usually hard to build.
> 
> They want to self-compile the latest of your software but use several years 
> old versions of everything else?
> I'd understand the Ubuntu use case but not the Debian oldstable one. 
> 
> If everyone develops like this, the software system grinds to a halt. 
> Recursively, I mean.
> 
> Just as a reminder for you regarding people of other systems: using C++11 
> excludes a lot of older compilers, e.g. MS VS6 or 7.1 or 8 or 9 ;-)
> 
> OTOH, if you have a very specific target audience...
> 
>> On Fri, Oct 16, 2015 at 11:56 AM, Hendrik Sattler
>>  wrote:
>>> 
>>> 
>>> Am 16. Oktober 2015 11:29:48 MESZ, schrieb Petr Bena
>> :
 I think you completely misunderstood me. I know I can install it on
>> my
 machine, but I can hardly install it on PC's or servers of users who
 use my program.
 
 I want to make it as easy as possible to let users compile my
>> program.
 Having to install anything by hand instead of system package manager
 is a big overhead to majority of users. CMake 3x is too new, it's
>>> 
>>> 
>>> Hey, 3.0.2 is even available in Debian stable, and that really says
>> something about older versions!
>>> 
>>> 
 available by default almost nowhere, meaning this option is not
 available to me at this time. Maybe in few years the situation will
 change, but for now I will resort to that hack which works on older
 versions that are generally available everywhere.
 
 On Fri, Oct 16, 2015 at 11:26 AM, Pau Garcia i Quiles
  wrote:
> Hello,
> 
> CMake 3.3.1 is available from my PPA, in case it helps:
> 
> https://launchpad.net/~pgquiles/+archive/ubuntu/ppa
> 
> 
> 
> On Fri, Oct 16, 2015 at 10:58 AM, Petr Bena 
 wrote:
>> 
>> If I did that nearly nobody would be able to compile my program as
>> cmake >= 3.1 is extremely rare on most distributions. Even
>> ubuntu's
>> PPA builder has some ancient version.
>> 
>> On Fri, Oct 16, 2015 at 9:44 AM, Petr Kmoch 
 wrote:
>>> Hi Petr.
>>> 
>>> You're using a feature (`CMAKE_CXX_STANDARD`) introduced in
>> CMake
>>> version
>>> 3.1, so you should require a minimum version >= that.
>>> 
>>> You can learn the version of CMake by running `cmake --version`
>>> 
>>> Petr
>>> 
>>> On Thu, Oct 15, 2015 at 5:45 PM, Petr Bena 
 wrote:
 
 What do you mean by "target" property? I don't see any target
 mentioned there. I don't have this line in there. I don't know
 which
 CMake this is, it failed on server we use for unit tests, but I
 have
 required min. version set to 2.8.7
 
 
 
 On Thu, Oct 15, 2015 at 5:41 PM, Matthew S Wallace
  wrote:
> What version of CMake are you using?  I’m using 3.3.2.  The
 only
> other
> thing I did was:
> 
> set_property(GLOBAL PROPERTY CXX_STANDARD_REQUIRED)
> 
> I’m guessing this probably does nothing since it is probably
>> a
 target
> property.
> 
> -Matt
> 
>> On Oct 15, 2015, at 10:34 AM, Petr Bena 

Re: [CMake] C++11 flag not being added

[Roman Wüger]

Hi Petr,

you can download CMake from https://cmake.org/download/.
There are also prebuilt binaries available.

We use the *.sh files to install CMake on our linux servers.

.) Install CMake to /opt/cmake-3.4.2.
.) Create a symlink to /opt/cmake
.) Create another symlink from the /opt/cmake/bin/* to /usr/bin

With this solution you only need to update the first symlink if you want to 
upgrade/downgrade a CMake version.

Best Regards
Roman

> Am 16.10.2015 um 10:58 schrieb Petr Bena :
> 
> If I did that nearly nobody would be able to compile my program as
> cmake >= 3.1 is extremely rare on most distributions. Even ubuntu's
> PPA builder has some ancient version.
> 
>> On Fri, Oct 16, 2015 at 9:44 AM, Petr Kmoch  wrote:
>> Hi Petr.
>> 
>> You're using a feature (`CMAKE_CXX_STANDARD`) introduced in CMake version
>> 3.1, so you should require a minimum version >= that.
>> 
>> You can learn the version of CMake by running `cmake --version`
>> 
>> Petr
>> 
>>> On Thu, Oct 15, 2015 at 5:45 PM, Petr Bena  wrote:
>>> 
>>> What do you mean by "target" property? I don't see any target
>>> mentioned there. I don't have this line in there. I don't know which
>>> CMake this is, it failed on server we use for unit tests, but I have
>>> required min. version set to 2.8.7
>>> 
>>> 
>>> 
>>> On Thu, Oct 15, 2015 at 5:41 PM, Matthew S Wallace
>>>  wrote:
 What version of CMake are you using?  I’m using 3.3.2.  The only other
 thing I did was:
 
 set_property(GLOBAL PROPERTY CXX_STANDARD_REQUIRED)
 
 I’m guessing this probably does nothing since it is probably a target
 property.
 
 -Matt
 
> On Oct 15, 2015, at 10:34 AM, Petr Bena  wrote:
> 
> Can you elaborate on it a bit?
> 
> I put set(CMAKE_CXX_STANDARD 11) as first line of my CMakeLists and it
> still doesn't work, without the hack I used I get errors while
> compiling.
> 
> Can you give me example file in which it works? I guess there is more
> needed for it to work.
> 
> On Tue, Oct 13, 2015 at 7:12 PM, Matthew S Wallace
>  wrote:
>> Thanks, setting the global variable solved my issue.
>> 
>> -Matt
>> 
>>> On Oct 13, 2015, at 10:46 AM, Johannes Zarl-Zierl
>>>  wrote:
>>> 
>>> Hi,
>>> 
>>> CXX_STANDARD is a target property, not a global one. You can either
>>> set
>>> CXX_STANDARD for every target that needs it, or set it globally by
>>> changing
>>> the default value.
>>> 
>>> You can do the latter by setting the variable CMAKE_CXX_STANDARD
>>> before
>>> defining any target that depends on it:
>>> 
>>> set(CMAKE_CXX_STANDARD 11)
>>> 
>>> HTH,
>>> Johannes
>>> 
 On Tuesday 13 October 2015 10:22:36 Matthew S Wallace wrote:
 I have the following two lines in my CMakeLists.txt
 
 set_property(GLOBAL PROPERTY CXX_STANDARD 11)
 set_property(GLOBAL PROPERTY CXX_STANDARD_REQUIRED)
 
 However when compiling some of my source files, the -std=c++11 flag
 is not
 added.
 
 Just for good measure I added:
 target_compile_features(my_target PRIVATE cxx_strong_enums) to the
 target
 that was having the problem.
 
 Not sure if it matters, but in this case the compile error I’m
 getting is
 complaining because I’m referencing a fully scoped enum.  If I
 explicitly
 include -std=c++11 in my compile flags, everything works.
 
 I’m thinking I’m probably just misunderstanding how CXX_STANDARD
 works, but
 any help would be appreciated.
 
 -Matt
>>> 
>>> --
>>> 
>>> 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 

Re: [cmake-developers] Xcode build settings and BullseyeCoverage

[Roman Wüger]

Thanks,

If anyone is interested, the guys from bullseye updated their website and the 
coverage is working now.

Best Regards

Von meinem iPhone gesendet

> Am 10.10.2015 um 14:43 schrieb Gregor Jasny <gja...@googlemail.com>:
> 
> Hello,
> 
>> On 09/10/15 17:51, Roman Wüger wrote:
>> I’m trying to configure and build a project with the “Xcode” generator and
>> the bullseye coverage tool.
>> 
>> Without the bullseye coverage tool it works fine but if I want to use it I
>> had to do the following workaround:
>> http://www.bullseye.com/help/tool-xcode.html
> 
> IMHO this workaround is way to hackish for a paid tool. The proper thing
> for Bullseye would be to provide a touchless way of intercepting all
> compiler invocations like for example Fortify or Coverity provides. You
> would be able to call it like this:
> 
>  $ bullseye xcodebuild
> 
> It would trace compiler invocations from xcodebuild and all childs.
> 
>> And I got the following error:
>> 
>> 
>> 
>> -- The C compiler identification is unknown
>> 
>> -- The CXX compiler identification is unknown
>> 
>> CMake Error at CMakeLists.txt:3 (project):
>> 
>>  No CMAKE_C_COMPILER could be found.
> 
>> Is there also a way to set generator specific things during configure time?
>> 
>> At the moment it is only possible with the build command: “cmake -build . --
>> PLATFORM_DEVELOPER_BIN_DIR=PointToSomething” which sets the build settings
>> for Xcode
> 
> I have not tested it, but maybe you could add
>   -DCMAKE_C_COMPILER=$(xcrun -find clang) -DCMAKE_CXX_COMPILER=$(xcrun
> -find clang++)
> 
> to the cmake command line at configuration time.
> 
> Thanks,
> Gregor
-- 

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] [cmake-developers] Xcode build settings and BullseyeCoverage

[Roman Wüger]

Thanks,

If anyone is interested, the guys from bullseye updated their website and the 
coverage is working now.

Best Regards

Von meinem iPhone gesendet

> Am 10.10.2015 um 14:43 schrieb Gregor Jasny <gja...@googlemail.com>:
> 
> Hello,
> 
>> On 09/10/15 17:51, Roman Wüger wrote:
>> I’m trying to configure and build a project with the “Xcode” generator and
>> the bullseye coverage tool.
>> 
>> Without the bullseye coverage tool it works fine but if I want to use it I
>> had to do the following workaround:
>> http://www.bullseye.com/help/tool-xcode.html
> 
> IMHO this workaround is way to hackish for a paid tool. The proper thing
> for Bullseye would be to provide a touchless way of intercepting all
> compiler invocations like for example Fortify or Coverity provides. You
> would be able to call it like this:
> 
>  $ bullseye xcodebuild
> 
> It would trace compiler invocations from xcodebuild and all childs.
> 
>> And I got the following error:
>> 
>> 
>> 
>> -- The C compiler identification is unknown
>> 
>> -- The CXX compiler identification is unknown
>> 
>> CMake Error at CMakeLists.txt:3 (project):
>> 
>>  No CMAKE_C_COMPILER could be found.
> 
>> Is there also a way to set generator specific things during configure time?
>> 
>> At the moment it is only possible with the build command: “cmake -build . --
>> PLATFORM_DEVELOPER_BIN_DIR=PointToSomething” which sets the build settings
>> for Xcode
> 
> I have not tested it, but maybe you could add
>   -DCMAKE_C_COMPILER=$(xcrun -find clang) -DCMAKE_CXX_COMPILER=$(xcrun
> -find clang++)
> 
> to the cmake command line at configuration time.
> 
> Thanks,
> Gregor
-- 

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] Xcode build settings and BullseyeCoverage

[Roman Wüger]

Hello,

 

I’m trying to configure and build a project with the “Xcode” generator and
the bullseye coverage tool.

Without the bullseye coverage tool it works fine but if I want to use it I
had to do the following workaround:
http://www.bullseye.com/help/tool-xcode.html

 

In short words, the clang and clang++ ExecPath would be changed from “clang”
=> “$(PLATFORM_DEVELOPER_BIN_DIR)/clang” and “clang++” =>
“$(PLATFORM_DEVELOPER_BIN_DIR)/clang++”

 

Before I made the changes, CMake finds clang/clang++ under
“/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolch
ain/usr/bin/clang”, with the changes CMake tries to find clang/clang++ under
“/Applications/Xcode.app/Contents/Developer/usr/bin/clang” which doesn’t
exist.

And I got the following error:

 

-- The C compiler identification is unknown

-- The CXX compiler identification is unknown

CMake Error at CMakeLists.txt:3 (project):

  No CMAKE_C_COMPILER could be found.

 

 

 

CMake Error at CMakeLists.txt:3 (project):

  No CMAKE_CXX_COMPILER could be found.

 

 

 

-- Configuring incomplete, errors occurred!

 

 

However, without the changes I could build the project with “cmake –build .
-- -showBuildSettings” which gives me the following information

 

.

.

.

PLATFORM_DEVELOPER_APPLICATIONS_DIR =
/Applications/Xcode.app/Contents/Developer/Applications

PLATFORM_DEVELOPER_BIN_DIR =
/Applications/Xcode.app/Contents/Developer/usr/bin

PLATFORM_DEVELOPER_LIBRARY_DIR =
/Applications/Xcode.app/Contents/Developer/Library

PLATFORM_DEVELOPER_SDK_DIR =
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Develop
er/SDKs

PLATFORM_DEVELOPER_TOOLS_DIR =
/Applications/Xcode.app/Contents/Developer/Tools

PLATFORM_DEVELOPER_USR_DIR =
/Applications/Xcode.app/Contents/Developer/usr

PLATFORM_DIR =
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform

.

.

.

 

Why doesn’t find CMake Xcode with the modified path?

 

Is there also a way to set generator specific things during configure time?

At the moment it is only possible with the build command: “cmake -build . --
PLATFORM_DEVELOPER_BIN_DIR=PointToSomething” which sets the build settings
for Xcode

 

 

Thanks in advance

 

Best Regards

Roman

-- 

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] Xcode build settings and BullseyeCoverage

[Roman Wüger]

Hello,

 

I’m trying to configure and build a project with the “Xcode” generator and
the bullseye coverage tool.

Without the bullseye coverage tool it works fine but if I want to use it I
had to do the following workaround:
http://www.bullseye.com/help/tool-xcode.html

 

In short words, the clang and clang++ ExecPath would be changed from “clang”
=> “$(PLATFORM_DEVELOPER_BIN_DIR)/clang” and “clang++” =>
“$(PLATFORM_DEVELOPER_BIN_DIR)/clang++”

 

Before I made the changes, CMake finds clang/clang++ under
“/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolch
ain/usr/bin/clang”, with the changes CMake tries to find clang/clang++ under
“/Applications/Xcode.app/Contents/Developer/usr/bin/clang” which doesn’t
exist.

And I got the following error:

 

-- The C compiler identification is unknown

-- The CXX compiler identification is unknown

CMake Error at CMakeLists.txt:3 (project):

  No CMAKE_C_COMPILER could be found.

 

 

 

CMake Error at CMakeLists.txt:3 (project):

  No CMAKE_CXX_COMPILER could be found.

 

 

 

-- Configuring incomplete, errors occurred!

 

 

However, without the changes I could build the project with “cmake –build .
-- -showBuildSettings” which gives me the following information

 

.

.

.

PLATFORM_DEVELOPER_APPLICATIONS_DIR =
/Applications/Xcode.app/Contents/Developer/Applications

PLATFORM_DEVELOPER_BIN_DIR =
/Applications/Xcode.app/Contents/Developer/usr/bin

PLATFORM_DEVELOPER_LIBRARY_DIR =
/Applications/Xcode.app/Contents/Developer/Library

PLATFORM_DEVELOPER_SDK_DIR =
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Develop
er/SDKs

PLATFORM_DEVELOPER_TOOLS_DIR =
/Applications/Xcode.app/Contents/Developer/Tools

PLATFORM_DEVELOPER_USR_DIR =
/Applications/Xcode.app/Contents/Developer/usr

PLATFORM_DIR =
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform

.

.

.

 

Why doesn’t find CMake Xcode with the modified path?

 

Is there also a way to set generator specific things during configure time?

At the moment it is only possible with the build command: “cmake -build . --
PLATFORM_DEVELOPER_BIN_DIR=PointToSomething” which sets the build settings
for Xcode

 

 

Thanks in advance

 

Best Regards

Roman

-- 

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] Rename suffix of Mac OS Framework

[Roman Wüger]

Hi Brad,

A use case for example is when an InDesign plugin should be developed. The 
InDesign plugin on Mac OS is a framework with the file extension 
".InDesignPlugin".

It works if the "Xcode" generator is used and the target property 
"XCODE_ATTRIBUTE_WRAPPER_EXTENSION" is set to "InDesignPlugin".
But it doesn't work if the "Unix Makefiles" generator is used.

See also https://cmake.org/Bug/view.php?id=14742

Best Regards
Roman

> Am 05.10.2015 um 17:31 schrieb Brad King <brad.k...@kitware.com>:
> 
>> On 10/01/2015 04:07 AM, Roman Wüger wrote:
>> set_target_properties(${PROJECT_NAME} PROPERTIES FRAMEWORK TRUE)
>> 
>> Is there a way to rename the suffix ".framework"?
> 
> Not currently.  It is hard-coded here:
> 
> https://cmake.org/gitweb?p=cmake.git;a=blob;f=Source/cmGeneratorTarget.cxx;hb=679a5d21#l2981
> 
> What is the use case for changing the framework extension?
> Doing so breaks the basic layout defined in "man ld":
> 
> -framework name[,suffix]
> This option tells the linker to search for `name.frame-
> work/name' the framework search path.  If the optional
> suffix is specified the framework is first searched for
> the name with the suffix and then without (e.g. look
> for `name.framework/name_suffix' first, if not there
> try `name.framework/name').
> 
> -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

Re: [CMake] [cmake-developers] Rename suffix of Mac OS Framework

[Roman Wüger]

Hi Brad,

A use case for example is when an InDesign plugin should be developed. The 
InDesign plugin on Mac OS is a framework with the file extension 
".InDesignPlugin".

It works if the "Xcode" generator is used and the target property 
"XCODE_ATTRIBUTE_WRAPPER_EXTENSION" is set to "InDesignPlugin".
But it doesn't work if the "Unix Makefiles" generator is used.

See also https://cmake.org/Bug/view.php?id=14742

Best Regards
Roman

> Am 05.10.2015 um 17:31 schrieb Brad King <brad.k...@kitware.com>:
> 
>> On 10/01/2015 04:07 AM, Roman Wüger wrote:
>> set_target_properties(${PROJECT_NAME} PROPERTIES FRAMEWORK TRUE)
>> 
>> Is there a way to rename the suffix ".framework"?
> 
> Not currently.  It is hard-coded here:
> 
> https://cmake.org/gitweb?p=cmake.git;a=blob;f=Source/cmGeneratorTarget.cxx;hb=679a5d21#l2981
> 
> What is the use case for changing the framework extension?
> Doing so breaks the basic layout defined in "man ld":
> 
> -framework name[,suffix]
> This option tells the linker to search for `name.frame-
> work/name' the framework search path.  If the optional
> suffix is specified the framework is first searched for
> the name with the suffix and then without (e.g. look
> for `name.framework/name_suffix' first, if not there
> try `name.framework/name').
> 
> -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