[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

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-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

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

[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

[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

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

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

[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

[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-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-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

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-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

[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-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-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

[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-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

[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-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-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-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

[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

[cmake-developers] Rename suffix of Mac OS Framework

[Roman Wüger]

Hello,

at the moment I build my frameworks with the following property:

set_target_properties(${PROJECT_NAME} PROPERTIES FRAMEWORK TRUE)

If my project is called "Test" for example, then a folder structure with the 
name "Test.framework" is created.

Is there a way to rename the suffix ".framework"?

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] CTest threshold exceeds 1024 bytes

[Roman Wüger]

Hello Brad,

I added the required command line options, but it doesn't produce the expected 
output.
It works in a normal environment, but not in the "CTest test case". Could you 
have a look at it?

Best Regards
Roman

> -Ursprüngliche Nachricht-
> Von: Brad King [mailto:brad.k...@kitware.com]
> Gesendet: Donnerstag, 10. September 2015 17:14
> An: Roman Wüger <roman.wue...@gmx.at>
> Cc: cmake-developers@cmake.org
> Betreff: Re: [cmake-developers] CTest threshold exceeds 1024 bytes
> 
> On 09/10/2015 11:11 AM, Roman Wüger wrote:
> > I've tested it on a real world example.
> >
> > My problem is to add a "ctest unit test case".
> 
> The patch I last sent earlier in this thread adds a unit test that produces 
> and
> reads the Test.xml file.  I left a comment:
> 
>  # TODO: actually check the content
> 
> as a placeholder for you to take over with the actual check.
> At that point the "test_xml" variable holds the content to be checked.
> 
> -Brad



0001-CTest-learned-to-limit-the-output-of-passed-and-fail.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-developers] CTest threshold exceeds 1024 bytes

[Roman Wüger]

Hi Brad,

I fail on implementing the test cases, I'm not familiar with testing this way 
in general. How can we finish this change?

Best regards
Roman

> Am 31.08.2015 um 21:19 schrieb Brad King <brad.k...@kitware.com>:
> 
>> On 08/31/2015 07:36 AM, "Roman Wüger" wrote:
>> Attached you will find the corrected patch.
> 
> Thanks.  I've attached a revised version.  I renamed the options
> and added release notes.  I also started the test case.  Please
> try completing the test and getting it to pass from there.
> 
> BTW, I noticed that there is actually a way to set these values
> already.  It just is not documented.  Try this:
> 
> $ git grep CTEST_CUSTOM_MAXIMUM_.*_TEST_OUTPUT_SIZE
> 
> to see the options.  They can be set in ctest scripts but not
> on the command line.
> 
> -Brad
> 
> <0001-CTest-learned-to-limit-the-output-of-passed-and-fail.patch>
-- 

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] CTest threshold exceeds 1024 bytes

[Roman Wüger]

I know what you mean, sure I have tested it on a developer machine but not as 
part of a "ctest unit test". I've tested it on a real world example.

My problem is to add a "ctest unit test case".


> Am 10.09.2015 um 17:06 schrieb Roman Wüger <roman.wue...@gmx.at>:
> 
> I've tested it in the visual studio debugger/ide, not as a test case with 
> ctest.
> 
> Regards
> 
>>> Am 10.09.2015 um 17:02 schrieb Brad King <brad.k...@kitware.com>:
>>> 
>>> On 09/10/2015 10:57 AM, Roman Wüger wrote:
>>> I don't know where to set the variables nor where to set the command line 
>>> parameters.
>>> How can I then test that the maximum passed size is 40 bytes and the failed 
>>> size is 60 for example?
>>> Where can I produce such test data (test.xml) with the expected size?
>> 
>> Don't you have a real use case for the feature you've added?
>> Does it produce a Test.xml file?  Use that as your case for
>> manual testing.
>> 
>> -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
-- 

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] CTest threshold exceeds 1024 bytes

[Roman Wüger]

Hi Brad,

sorry for the long response time, but I was on vacation.

Attached you will find the corrected patch.

Best regards
Roman



Am 20.08.15 um 17:30 schrieb Brad King

> On 08/20/2015 06:30 AM, Roman Wüger wrote:
> 
> > I made the "atoi" change but my problem is the test itself.
> 
> > I don't know how to specify the command line parameter and
> 
> > check the generated xml file.
> 
> 
> 
> Okay, please post the latest version of the patch so far and
> 
> I'll see if I can find a chance to work on the test.
> 
> 
> 
> Thanks,
> 
> -Brad


0001-ctest-learned-to-limit-the-output-of-passed-and-fail.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

[cmake-developers] Issue: 12592 New componentwise extra install commands for NSIS-generator

[Roman Wüger]

Hello,

did someone work on this? (http://public.kitware.com/Bug/view.php?id=12592)

Is there an alternative to use extra install commands per component?

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] CTest threshold exceeds 1024 bytes

[Roman Wüger]

Hello Brad,

I made the atoi change but my problem is the test itself. I don't know how to 
specify the command line parameter and check the generated xml file.

Best Regards
RomN

 Am 27.07.2015 um 17:52 schrieb Brad King brad.k...@kitware.com:
 
 On 07/23/2015 03:23 AM, Roman Wüger wrote:
 I don't know how to use the -check.cmake scripts to check the
 length of the output.
 
 My advice to use Tests/RunCMake/CTestCommandLine turns out to be
 incorrect.  Use Tests/RunCMake/ctest_test instead because that
 one actually produces the .xml file.  See the TestChangeId case
 for another example that checks the .xml file content.
 
 Also please change from atoi to StringToLong and issue a warning
 if the conversion of the specified value fails (see --test-load
 for an example).  Then add a test covering this warning for each
 option.
 
 Thanks,
 -Brad
-- 

Powered by www.kitware.com

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

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

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

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

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

Re: [cmake-developers] check_cxx_source_compiles and include directories

[Roman Wüger]

Hi Brad,

thanks for your investigation.
I've tried it on Mac OS 10.10.4 with clang 6.1.0.6020053 from XCode 6 using 
Unix Makefiles as the generator.

Best Regards
Roman

 Am 28.07.2015 um 16:55 schrieb Brad King brad.k...@kitware.com:
 
 On 07/27/2015 03:26 PM, Roman Wüger wrote:
 SubProj1 and SubProj2 does not find mutex, but
 check_cxx_source_compiles succeeds.
 
 Did I miss configure something here?
 
 The posted example works for me on Linux with g++ 4.9.3.
 The check succeeds and an executable I create in SubProj1
 can #include mutex.  I have /usr/include/c++/4.9.3/mutex
 right next to all the other C++ headers.
 
 -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] check_cxx_source_compiles and include directories

[Roman Wüger]

Thanks Brad

yes, and that's the point.

I've found my mistake, I had set the CMAKE_OSX_DEPLOYMENT_TARGET and 
CMAKE_OSX_SYSROOT between the check_cxx_source_compiles() calls and the 
add_subdirectory() calls.
I moved the CMAKE_OSX_DEPLOYMENT_TARGET and CMAKE_OSX_SYSROOT initialization on 
top of the check_cxx_source_compiles() calls and everthing is working as 
expected.

So, in my situation the order is:
1.) CMAKE_OSX_DEPLOYMENT_TARGET and CMAKE_OSX_SYSROOT
2.) check_cxx_source_compiles() and other platform checks
3.) add_subdirectory() and other stuff

Best Regards
Roman

 -Ursprüngliche Nachricht-
 Von: Brad King [mailto:brad.k...@kitware.com]
 Gesendet: Dienstag, 28. Juli 2015 18:50
 An: Roman Wüger roman.wue...@gmx.at
 Cc: CMake MailingList cm...@cmake.org; CMake Developer MailingList
 cmake-developers@cmake.org
 Betreff: Re: [cmake-developers] check_cxx_source_compiles and include
 directories
 
 On 07/28/2015 12:23 PM, Roman Wüger wrote:
  I've tried it on Mac OS 10.10.4 with clang 6.1.0.6020053 from XCode 6
  using Unix Makefiles as the generator.
 
 Is that using the Xcode Command Line Tools or the /usr/bin/c++ stub that
 uses the /Applications/Xcode.app/.../bin/clang++ compiler underneath?
 Is CMAKE_OSX_SYSROOT set?  Does -isysroot appear on the compilation
 command line?
 
 Thanks,
 -Brad


-- 

Powered by www.kitware.com

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

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

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

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

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

Re: [cmake-developers] check_cxx_source_compiles and include directories

[Roman Wüger]

So, here is the piece of code which works

 

Main CMakeLists.txt:

 

project(MyProject)

 

list(APPEND CMAKE_MODULE_PATH ${CMAKE_SOURCE_DIR}/cmake)

 

if (APPLE)

set(CMAKE_CXX_EXTENSIONS OFF) # Use -std=c++11 instead of -std=gnu++11

endif()

set(CMAKE_CXX_STANDARD 11)

include(CheckCXXCompilerFlag)

 

# Required for check_cxx_source_cmopiles

check_cxx_compiler_flag(-std=c++11 CXX11_FLAG)

if (CXX11_FLAG)

set(CMAKE_CXX_FLAGS ${CMAKE_CXX_FLAGS} -std=c++11)

endif()

 

include(CheckMyCXX11Features.cmake)

.

.

.

add_subdirectory(SubProj1)

add_subdirectory(SubProj2)

.

.

.

 

 

CheckMyCXX11Features.cmake:

 

include(CheckCXXSourceCompiles)

 

# C++11 Unique Lock and Mutex

set(CMAKE_REQUIRED_FLAGS ${CMAKE_CXX_FLAGS})

check_cxx_source_compiles(

   #include mutex  // std::mutex, std::unique_lock

 

std::mutex mtx;   // mutex for critical section

 

void print_block (int n, char c) {

  // critical section (exclusive access to std::cout signaled by
lifetime of lck):

  std::unique_lockstd::mutex lck (mtx);

  for (int i=0; in; ++i) { /* Do Something */ }

}

 

int main ()

{

  print_block(50,'$');

 

  return 0;

}

  MY_HAVE_CXX11_MUTEX_AND_UNIQUE_LOCK

)

set(CMAKE_REQUIRED_FLAGS )

 

configure_file(${CMAKE_SOURCE_DIR}/cmake/MyCXX11Features.h.in
${CMAKE_BINARY_DIR}/cmake/MyCXX11Features.h)

 

 

SubProj1 and SubProj2 does not find mutex, but check_cxx_source_compiles
succeeds.

Did I miss configure something here?

 

Best Regards

Roman

 

 

 -Ursprüngliche Nachricht-

 Von: cmake-developers [mailto:cmake-developers-boun...@cmake.org] Im

 Auftrag von Roman Wüger

 Gesendet: Montag, 27. Juli 2015 07:35

 An: CMake MailingList cm...@cmake.org; CMake Developer MailingList

 cmake-developers@cmake.org

 Betreff: [cmake-developers] check_cxx_source_compiles and include

 directories

 

 Hello,

 

 I've a small code example to test if the mutex header file exists (with

 check_cxx_source_compiles), which sets my variable successfully to TRUE.

 

 When I compile the real code then I got an error message saying 'mutex'
file

 not found.

 

 I checked the compile flags for both situations and these are equal. So I

 thought that the include directories could be the problem.

 

 Any hints?

 

 Best Regards

 Roman

 --

 

 Powered by  http://www.kitware.com www.kitware.com

 

 Please keep messages on-topic and check the CMake FAQ at:

  http://www.cmake.org/Wiki/CMake_FAQ 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
http://cmake.org/cmake/help/support.html

 CMake Consulting:  http://cmake.org/cmake/help/consulting.html
http://cmake.org/cmake/help/consulting.html

 CMake Training Courses:  http://cmake.org/cmake/help/training.html
http://cmake.org/cmake/help/training.html

 

 Visit other Kitware open-source projects at

  http://www.kitware.com/opensource/opensource.html
http://www.kitware.com/opensource/opensource.html

 

 Follow this link to subscribe/unsubscribe:

  http://public.kitware.com/mailman/listinfo/cmake-developers
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] [CMake] CTest threshold exceeds 1024 bytes

[Roman Wüger]

Hi Brad,

i've updated the patch with the missing things, but I don't know how to use the 
-check.cmake scripts to check the length of the output.
Maybe you could have a look at it.

Best regards
Roman



Am 22.07.15 um 17:14 schrieb Brad King

 On 07/21/2015 06:16 PM, Roman Wüger wrote:
 
  I've attached a patch which learns CTest to handle it.
 
  I hope this patch could be merged.
 
 
 
 Good start.  Please also update Help/manual/ctest.1.rst with
 
 documentation for the new options.  Also please extend the test
 
 suite, likely in Tests/RunCMake/CTestCommandLine, to cover the
 
 options.  See Tests/RunCMake/README.rst for information about
 
 how the existing test works.  You could perhaps add a case that
 
 uses a -check.cmake script to verify the length of the output
 
 in a Test.xml file after running ctest -M Experimental -T Test
 
 plus the new options.
 
 
 
 Thanks,
 
 -Brad


0001-ctest-learned-to-limit-the-output-of-passed-and-fail.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-developers] [CMake] CTest threshold exceeds 1024 bytes

[Roman Wüger]

Hi Brad,

I've attached a patch which learns CTest to handle it.
I hope this patch could be merged.

Best Regards
Roman

 -Ursprüngliche Nachricht-
 Von: Brad King [mailto:brad.k...@kitware.com]
 Gesendet: Dienstag, 21. Juli 2015 15:53
 An: Roman Wüger
 Cc: CMake Developer MailingList; CMake MailingList
 Betreff: Re: [CMake] CTest threshold exceeds 1024 bytes
 
 On 07/21/2015 04:12 AM, Roman Wüger wrote:
  Is there a way to get the full output without modifying every CMake
  Script of about ~ 35 projects?
 
 CTest always truncates the output of passing tests unless the test output
 contains the literal text CTEST_FULL_OUTPUT.
 This was done long ago to limit the size of submissions of passed tests.
 
 CTest will have to be taught an option to skip this.  Take a look at the
 definition and uses of CleanTestOutput in Source/CTest.
 There are already variables like CustomMaximumPassedTestOutputSize
 internally but it looks like there is no way to configure them at runtime.
 
 -Brad



0001-CTest-learned-to-limit-the-output-of-passed-and-fail.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

[cmake-developers] CTest threshold exceeds 1024 bytes

[Roman Wüger]

Hello,

when I run CTest from the command line with the same parameters as on the build 
server, then everything is working fine.

If I run the command on the build server then I get a message which says that 
the threshold of 1024 bytes are exceeded. The output are debug messages and 
not failures.

I have the output on CDash and on Jenkins.

Here is the command which I call:
ctest -C Release --output-on-failure --no-compress-output -T test

Is there a way to get the full output without modifying every CMake Script of 
about ~ 35 projects?

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 when creating config files and add_dependencies

[Roman Wüger]

Hello Brad,

but the problem with this command is, that for multi configuration environments 
(e.g. Visual Studio), it requires $CONFIG in the filename which then creates 
4 header files. One for each configuration.

Maybe I didn't understand something, but after that I also need to call 
configure_file to resolve the rest of the CMake variables.

After the 4 header files are generated, which one should I include in the unit 
test for example? 

Do you understand the problem?

Thanks
Roman

 Am 15.06.2015 um 15:10 schrieb Brad King brad.k...@kitware.com:
 
 On 06/12/2015 07:19 AM, Roman Wüger wrote:
 It would be great if generator expressions can be used with
 configure_file to avoid such overhead.
 
 Does anyone have an idea on how to solve that?
 
 See file(GENERATE).
 
 -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] Problems when creating config files and add_dependencies

[Roman Wüger]

Hello,

 

short description: I want to have a configuration header file per unit test.

 

For this purpose I wrote the following function, which creates a header file
in “${CURRENT_BINARY_DIR}” and copy all test files into the binary
directory.

Howewer, I got it to work when I use add_custom_target as pre_build target,
but this doesn’t work on *nix systems.

 

So here is the current function:

function(CopyUnitTestFiles projectName)

set(UnitTestConfigName ${projectName}UnitTestConfig)

set(UNITTESTCONFIGNAME ${projectName}UnitTestConfig)

set(PROJECT_NAME ${projectName})

set(OUTPUT_FILENAME
${CMAKE_CURRENT_BINARY_DIR}/${UnitTestConfigName}.cmake)

set(HEADER_INPUT_FILENAME
${CMAKE_SOURCE_DIR}/cmake/UnitTestConfig.h.in)

set(HEADER_OUTPUT_FILENAME
${CMAKE_CURRENT_BINARY_DIR}/${UnitTestConfigName}.h)

set(CURRENT_FILENAME ${OUTPUT_FILENAME})

set(RELATIVE_FILEPATH testfiles/${projectName})

set(INCLUDE_GUARD ${projectName}_UNITTESTCONFIG_H)

string(TOUPPER ${INCLUDE_GUARD} INCLUDE_GUARD)

 

set(TARGET_FILE_DIR $TARGET_FILE_DIR:${projectName})

set(CopyUnitTestFilesProjectName  CopyUnitTestFiles_${projectName})

configure_file(${CMAKE_SOURCE_DIR}/cmake/UnitTestConfig.cmake.in
${OUTPUT_FILENAME} @ONLY)

add_custom_target(${CopyUnitTestFilesProjectName}

  COMMAND ${CMAKE_COMMAND}
-DABSFILEPATH=${TARGET_FILE_DIR} -P ${OUTPUT_FILENAME}

  COMMAND ${CMAKE_COMMAND} -E remove_directory
${TARGET_FILE_DIR}/testfiles/${projectName}

  COMMAND ${CMAKE_COMMAND} -E copy_directory
${CMAKE_CURRENT_SOURCE_DIR}/data/testfiles
${TARGET_FILE_DIR}/testfiles/${projectName}

 )

set_property(TARGET ${CopyUnitTestFilesProjectName} PROPERTY FOLDER
Custom Targets/CopyUnitTestFiles)

add_dependencies(${projectName} ${CopyUnitTestFilesProjectName})

endfunction(CopyUnitTestFiles)

 

The function should be called like:

 

project(UnitTest1)

add_executable(${PROJECT_NAME} ${HEADERS} ${SOURCES})

target_link_libraries(${PROJECT_NAME} gtest gtest_main)

 

CopyUnitTestFiles(${PROJECT_NAME})

 

 

The error message which I get:

-- Configuring done

CMake Error: The inter-target dependency graph contains the following
strongly connected component (cycle):

  CopyUnitTestFiles_UnitTest1 of type UTILITY

depends on UnitTest1 (strong)

  UnitTest1 of type EXECUTABLE

depends on CopyUnitTestFiles_UnitTest1 (strong)

At least one of these targets is not a STATIC_LIBRARY.  Cyclic dependencies
are allowed only among static libraries.

 

 

UnitTestConfig.cmake.in:

set(ProjectName @PROJECT_NAME@)

set(UnitTestConfigName @UNITTESTCONFIGNAME@)

set(NAMESPACE ${UnitTestConfigName})

set(UNITTESTNAME ${ProjectName})

set(RELATIVE_FILEPATH testfiles/${ProjectName})

set(ABSOLUTE_FILEPATH ${ABSFILEPATH}/testfiles/${ProjectName})

set(INCLUDE_GUARD ${ProjectName}_UNITTESTCONFIG_H)

string(TOUPPER ${INCLUDE_GUARD} INCLUDE_GUARD)

 

configure_file(@HEADER_INPUT_FILENAME@ @HEADER_OUTPUT_FILENAME@)

 

UnitTestConfig.h.in:

#ifndef @INCLUDE_GUARD@

#define @INCLUDE_GUARD@

 

namespace @NAMESPACE@ {

const char *const UnitTestName = @UNITTESTNAME@;

const char *const RelativeTestFilesPath = @RELATIVE_FILEPATH@;

const char *const AbsoluteTestFilesPath = @ABSOLUTE_FILEPATH@;

const wchar_t *const UnitTestNameW= L@UNITTESTNAME@;

const wchar_t *const RelativeTestFilesPathW = L@RELATIVE_FILEPATH@;

const wchar_t *const AbsoluteTestFilesPathW = L@ABSOLUTE_FILEPATH@;

}

 

#endif // @INCLUDE_GUARD@

 

It would be great if generator expressions can be used with configure_file
to avoid such overhead.

Does anyone have an idea on how to solve that?

 

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] Virtual folders in Visual studio get expanded on reload

[Roman Wüger]

Hi,

I noticed that sometimes when a target is reloaded, that the virtual folders 
and targets for the complete visual studio solution get expanded.
For a small project this isn't a problem, but in a large project (~ 100 
targets) this is a really big problem to close all targets every time.

Did anybody noticed this behavior and has a solution for it?

Thanks

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] Identify used source files

[Roman Wüger]

If someone is interessted in this solution:

 
set(FilenameUsedFiles ${CMAKE_BINARY_DIR}/UsedFiles.lst)
file(WRITE ${FilenameUsedFiles} )
 
function (parseArguments)
set(options)
set(oneValueArgs)
set(multiValueArgs)
cmake_parse_arguments(CFG ${options}${oneValueArgs} 
${multiValueArgs}${ARGN} )
 
foreach(file ${ARGN})
get_filename_component(tempPath ${file} DIRECTORY)
string(FIND ${file} ${CMAKE_BINARY_DIR}buildPathFoundPos)
string(FIND ${file} ${CMAKE_SOURCE_DIR}sourcePathFoundPos)
 
if ((NOT ${file} STREQUALIMPORTED) AND
(NOT ${file} STREQUAL MODULE)AND
(NOT ${file} STREQUAL STATIC)AND
(NOT ${file} STREQUAL SHARED)AND
(NOT ${file} STREQUAL WIN32)AND
${buildPathFoundPos} EQUAL -1)
if (${sourcePathFoundPos} EQUAL -1)
file(APPEND ${FilenameUsedFiles} 
${CMAKE_CURRENT_SOURCE_DIR}/${file}\n)
else()
file(APPEND ${FilenameUsedFiles} ${file}\n)
endif()
endif()
endforeach()
endfunction(parseArguments)
 
function(add_library name)
  parseArguments(${ARGN})
  _add_library(${name} ${ARGN})
endfunction()
 
function(add_executable name)
  parseArguments(${ARGN})
  _add_executable(${name} ${ARGN})
endfunction()

Best Regards 
Roman

 Am 28.04.2015 um 07:00 schrieb Roman Wüger roman.wue...@gmx.at:
 
 Hello,
 
 is there a proper solution to get all used source files for all defined 
 librarys and executables?
 
 My first idea was to overload the main functions such as add_executable() and 
 add_library() temporarily in the main CMakeLists.txt and write a text file or 
 whatever, but I thought there were a better way.
 
 Did anybody know a better way?
 
 Maybe CMake has a way to get a list of used files?
 
 The reason is to clean a big old source tree.
 
 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
-- 

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] Identify used source files

[Roman Wüger]

Hello,

is there a proper solution to get all used source files for all defined 
librarys and executables?

My first idea was to overload the main functions such as add_executable() and 
add_library() temporarily in the main CMakeLists.txt and write a text file or 
whatever, but I thought there were a better way.

Did anybody know a better way?

Maybe CMake has a way to get a list of used files?

The reason is to clean a big old source tree.

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] Problems with WriteCompilerDetectionHeader and cxx_nullptr

[Roman Wüger]

Hi Brad,

attached is an updated patch.

Roman

From ea75cb1a3d866d923b6711c9e0c0bbf1f66d7dbf Mon Sep 17 00:00:00 2001
From: Roman Wüger roman.wue...@gmx.at
Date: Fri, 13 Mar 2015 09:18:19 +0100
Subject: [PATCH] WCDH: Fix cxx_nullptr for compilers which doesn't support
 C++11

---
 Modules/WriteCompilerDetectionHeader.cmake | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Modules/WriteCompilerDetectionHeader.cmake 
b/Modules/WriteCompilerDetectionHeader.cmake
index d18f47c..f4dcb21 100644
--- a/Modules/WriteCompilerDetectionHeader.cmake
+++ b/Modules/WriteCompilerDetectionHeader.cmake
@@ -586,7 +586,7 @@ function(write_compiler_detection_header
 #  if ${def_name}
 #define ${def_value} nullptr
 #  else
-#define ${def_value} static_castvoid*(0)
+#define ${def_value} 0
 #  endif
 \n)
   endif()
-- 
1.9.5.msysgit.0







-- 

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] Problems with WriteCompilerDetectionHeader and cxx_nullptr

[Roman Wüger]

Hello,

 

i tried to use the generated compiler detection header but get an error if I
use the cxx_nullptr feature on a compiler which doesn’t support C++11.

 

void doSomething(int n, bool *ok = 0) {

if (ok)

*ok = true;

 

if (n != 0) {

if (ok)

*ok = false;

}

}

 

This simple example produces the following error on Mac OS:

error: cannot initialize a parameter of type 'bool *' with an rvalue of type
'void *'

void doSomething(int n = 1, bool *ok = static_castvoid*(0)) {   

  ^~

 

However, if C++11 could be used then the „nullptr“ is working fine.

Couldn‘t „static_castvoid*(0)“ simply be replaced with „0“?

 

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:
http://public.kitware.com/mailman/listinfo/cmake-developers

[cmake-developers] Problems with WriteCompilerDetectionHeader and cxx_nullptr

[Roman Wüger]

Hello,

I've attached a patch for this problem.

Best Regards

From 3b77b957a41ce00c8e5d8d47ce442887181d669d Mon Sep 17 00:00:00 2001
From: Roman Wüger roman.wue...@gmx.at
Date: Thu, 12 Mar 2015 11:51:24 +0100
Subject: [PATCH] WCDH: Fix cxx_nullptr for compilers which doesn't support
 C++11

---
 Modules/WriteCompilerDetectionHeader.cmake | 6 +-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/Modules/WriteCompilerDetectionHeader.cmake 
b/Modules/WriteCompilerDetectionHeader.cmake
index d18f47c..721bbdb 100644
--- a/Modules/WriteCompilerDetectionHeader.cmake
+++ b/Modules/WriteCompilerDetectionHeader.cmake
@@ -586,7 +586,11 @@ function(write_compiler_detection_header
 #  if ${def_name}
 #define ${def_value} nullptr
 #  else
-#define ${def_value} static_castvoid*(0)
+#ifdef NULL
+#  define ${def_value} NULL
+#else
+#  define ${def_value} 0
+#endif
 #  endif
 \n)
   endif()
-- 
1.9.5.msysgit.0




-- 

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] Wrong behavior with 3.2.0-rc2

[Roman Wüger]

Hello Brad,

if CMake 3.2.0 will not be released, when is the expected release date for 
CMake 3.2.1?

Regards
Roman

 Am 06.03.2015 um 21:38 schrieb Brad King brad.k...@kitware.com:
 
 On 03/06/2015 06:57 AM, Nils Gladitz wrote:
 On 03/06/2015 10:22 AM, Pere Mato Vila wrote:
 [100%] [100%] *Generating A.txt, B.txt*
 *Generating A.txt, B.txt*
 
 Thanks for trying the release candidate and reporting this.
 
 This seems to be the case since
 [644b4688d71cc52f8499d6103495de0909319557] Makefile: Fix rebuild with 
 multiple custom command outputs (#15116)
 
 Yes.  I've re-opened the corresponding issue with a note about this:
 
 http://www.cmake.org/Bug/view.php?id=15116#c38168
 
 Please follow that issue for further updates.
 
 We've already tagged v3.2.0 but it was not announced yet.  It looks
 like 3.2.0 is DOA and we will have to skip to 3.2.1 to fix this.
 
 Thanks,
 -Brad
 
 -- 
 
 Powered by www.kitware.com
 
 Please keep messages on-topic and check the CMake FAQ at: 
 http://www.cmake.org/Wiki/CMake_FAQ
 
 Kitware offers various services to support the CMake community. For more 
 information on each offering, please visit:
 
 CMake Support: http://cmake.org/cmake/help/support.html
 CMake Consulting: http://cmake.org/cmake/help/consulting.html
 CMake Training Courses: http://cmake.org/cmake/help/training.html
 
 Visit other Kitware open-source projects at 
 http://www.kitware.com/opensource/opensource.html
 
 Follow this link to subscribe/unsubscribe:
 http://public.kitware.com/mailman/listinfo/cmake
-- 

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] [ANNOUNCE] CMake 3.2.0-rc2 now ready for testing!

[Roman Wüger]

Hello Robert,

is there a list which showing the changes between rc1 and rc2, to test such 
things explicitly?

Regards
Roman 


 Am 24.02.2015 um 16:01 schrieb Robert Maynard robert.mayn...@kitware.com:
 
 I am proud to announce the CMake 3.2 second release candidate.
 
 Sources and binaries are available at:
  http://www.cmake.org/download/
  http://www.cmake.org/files/v3.2/?C=M;O=D
 
 Documentation is available at:
  http://www.cmake.org/cmake/help/v3.2
 
 Release notes appear below and are also published at
  http://www.cmake.org/cmake/help/v3.2/release/3.2.html
 Some of the more significant features of CMake 3.2 are:
 
 * CMake learned to support unicode characters *encoded as UTF-8* on
  Windows.  This was already supported on platforms whose system APIs
  accept UTF-8 encoded strings. Unicode characters may now be used in
  CMake code, paths to source files, configured files such as .h.in
  files, and other files read and written by CMake.  Note that because
  CMake interoperates with many other tools, there may still be some
  limitations when using certain unicode characters.
 
 * The Compile Features functionality is now aware of features
  supported by more compilers, including:
 
  * Apple Clang (AppleClang) for Xcode versions 4.4 though 6.1.
 
  * GNU compiler versions 4.4 through 5.0 on UNIX and Apple (GNU).
 
  * Microsoft Visual Studio (MSVC) for versions 2010 through 2015.
 
  * Oracle SolarisStudio (SunPro) version 12.4.
 
 * The add_custom_command() and add_custom_target() commands
  learned a new BYPRODUCTS option to specify files produced as side
  effects of the custom commands.  These are not outputs because they
  do not always have to be newer than inputs.
 
 * The file(GENERATE) command can now generate files which are used
  as source files for buildsystem targets.  Generated files
  automatically get their GENERATED property set to TRUE.
 
 Deprecated and Removed Features:
 
 * Files written in the cmake-language(7), such as CMakeLists.txt
  or *.cmake files, are now expected to be encoded as UTF-8.  If
  files are already ASCII, they will be compatible.  If files were in
  a different encoding, including Latin 1, they will need to be
  converted.
 
 * The FindOpenGL module no longer explicitly searches for any
  dependency on X11 libraries with the FindX11 module.  Such
  dependencies should not need to be explicit. Applications using X11
  APIs themselves should find and link to X11 libraries explicitly.
 
 
 CMake 3.2 Release Notes
 ***
 
 Changes made since CMake 3.1 include the following.
 
 
 New Features
 
 
 
 Syntax
 --
 
 * CMake learned to support unicode characters *encoded as UTF-8* on
  Windows.  This was already supported on platforms whose system APIs
  accept UTF-8 encoded strings. Unicode characters may now be used in
  CMake code, paths to source files, configured files such as .h.in
  files, and other files read and written by CMake.  Note that because
  CMake interoperates with many other tools, there may still be some
  limitations when using certain unicode characters.
 
 
 Commands
 
 
 * The add_custom_command() and add_custom_target() commands
  learned a new BYPRODUCTS option to specify files produced as side
  effects of the custom commands.  These are not outputs because they
  do not always have to be newer than inputs.
 
 * The add_custom_command() and add_custom_target() commands
  learned a new USES_TERMINAL option to request that the command be
  given direct access to the terminal if possible. The Ninja
  generator will places such commands in the console pool.  Build
  targets provided by CMake that are meant for individual interactive
  use, such as install, are now placed in this pool.
 
 * A new continue() command was added that can be called inside
  loop contexts to end the current iteration and start the next one at
  the top of the loop block.
 
 * The file(LOCK) subcommand was created to allow CMake processes
  to synchronize through file and directory locks.
 
 * The file(STRINGS) now supports UTF-16LE, UTF-16BE, UTF-32LE,
  UTF- 32BE as ENCODING options.
 
 * The install(EXPORT) command now works with an absolute
  DESTINATION even if targets in the export set are installed with a
  destination or *usage requirements* specified relative to the
  install prefix.  The value of the CMAKE_INSTALL_PREFIX variable is
  hard-coded into the installed export file as the base for relative
  references.
 
 * The try_compile() command source file signature now honors link
  flags (e.g. CMAKE_EXE_LINKER_FLAGS) in the generated test project.
  See policy CMP0056.
 
 * The try_run() command learned to honor the LINK_LIBRARIES
  option just as try_compile() already does.
 
 * The file(GENERATE) command now generates the output file with
  the same permissions as the input file if set.
 
 * The file(GENERATE) command can now generate files which are used
  as source files for buildsystem targets.  

Re: [cmake-developers] [ANNOUNCE] CMake 3.2.0-rc2 now ready for testing!

[Roman Wüger]

Thank you very much


 Am 25.02.2015 um 15:12 schrieb Robert Maynard robert.mayn...@kitware.com:
 
 Hi Roman,
 
 We do attach the short-log of all changes made between each RC version
 to the bottom of the annoucement. But here are the changes plus the
 git SHA1's for each ( produced with git log --no-merges  --oneline
 v3.2.0-rc1..v3.2.0-rc2)
 
 99575c9 CMake 3.2.0-rc2
 b4005a3 FindCurses: Drop unused check for cbreak in tinfo library
 a41d621 bootstrap: Add --(no-)system-jsoncpp options
 a576844 FindJsonCpp: Drop new module due to upstream jsoncpp providing package
 1ade687 cmake-gui: Reset generator platform and toolset on configure (#15411)
 7e6608f Utilities/Release: Build OS X and Win binaries without OpenSSL
 bce4e20 FindJNI: Add arch-specific library dir for JDK 9 layout (#15408)
 6d19ef9 Help: In 3.2 relnotes move OpenGL/X11 to deprecated/removed section
 029d38f Help: Revise configure_file documentation (#15403)
 
 On Wed, Feb 25, 2015 at 9:07 AM, Roman Wüger roman.wue...@gmx.at wrote:
 Hello Robert,
 
 is there a list which showing the changes between rc1 and rc2, to test such 
 things explicitly?
 
 Regards
 Roman
 
 
 Am 24.02.2015 um 16:01 schrieb Robert Maynard robert.mayn...@kitware.com:
 
 I am proud to announce the CMake 3.2 second release candidate.
 
 Sources and binaries are available at:
 http://www.cmake.org/download/
 http://www.cmake.org/files/v3.2/?C=M;O=D
 
 Documentation is available at:
 http://www.cmake.org/cmake/help/v3.2
 
 Release notes appear below and are also published at
 http://www.cmake.org/cmake/help/v3.2/release/3.2.html
 Some of the more significant features of CMake 3.2 are:
 
 * CMake learned to support unicode characters *encoded as UTF-8* on
 Windows.  This was already supported on platforms whose system APIs
 accept UTF-8 encoded strings. Unicode characters may now be used in
 CMake code, paths to source files, configured files such as .h.in
 files, and other files read and written by CMake.  Note that because
 CMake interoperates with many other tools, there may still be some
 limitations when using certain unicode characters.
 
 * The Compile Features functionality is now aware of features
 supported by more compilers, including:
 
 * Apple Clang (AppleClang) for Xcode versions 4.4 though 6.1.
 
 * GNU compiler versions 4.4 through 5.0 on UNIX and Apple (GNU).
 
 * Microsoft Visual Studio (MSVC) for versions 2010 through 2015.
 
 * Oracle SolarisStudio (SunPro) version 12.4.
 
 * The add_custom_command() and add_custom_target() commands
 learned a new BYPRODUCTS option to specify files produced as side
 effects of the custom commands.  These are not outputs because they
 do not always have to be newer than inputs.
 
 * The file(GENERATE) command can now generate files which are used
 as source files for buildsystem targets.  Generated files
 automatically get their GENERATED property set to TRUE.
 
 Deprecated and Removed Features:
 
 * Files written in the cmake-language(7), such as CMakeLists.txt
 or *.cmake files, are now expected to be encoded as UTF-8.  If
 files are already ASCII, they will be compatible.  If files were in
 a different encoding, including Latin 1, they will need to be
 converted.
 
 * The FindOpenGL module no longer explicitly searches for any
 dependency on X11 libraries with the FindX11 module.  Such
 dependencies should not need to be explicit. Applications using X11
 APIs themselves should find and link to X11 libraries explicitly.
 
 
 CMake 3.2 Release Notes
 ***
 
 Changes made since CMake 3.1 include the following.
 
 
 New Features
 
 
 
 Syntax
 --
 
 * CMake learned to support unicode characters *encoded as UTF-8* on
 Windows.  This was already supported on platforms whose system APIs
 accept UTF-8 encoded strings. Unicode characters may now be used in
 CMake code, paths to source files, configured files such as .h.in
 files, and other files read and written by CMake.  Note that because
 CMake interoperates with many other tools, there may still be some
 limitations when using certain unicode characters.
 
 
 Commands
 
 
 * The add_custom_command() and add_custom_target() commands
 learned a new BYPRODUCTS option to specify files produced as side
 effects of the custom commands.  These are not outputs because they
 do not always have to be newer than inputs.
 
 * The add_custom_command() and add_custom_target() commands
 learned a new USES_TERMINAL option to request that the command be
 given direct access to the terminal if possible. The Ninja
 generator will places such commands in the console pool.  Build
 targets provided by CMake that are meant for individual interactive
 use, such as install, are now placed in this pool.
 
 * A new continue() command was added that can be called inside
 loop contexts to end the current iteration and start the next one at
 the top of the loop block.
 
 * The file(LOCK) subcommand was created to allow CMake processes
 to synchronize through

Re: [cmake-developers] Commit 4c98de33: cmLocalGenerator: fix the default configuration check

[Roman Wüger]

Hello Ben,

 

I think the change is also required for the following line (line 424):

 

if(!default_config  !configurationTypes.empty())

 

Because here the „default_config“ could also be a valid pointer with an
empty content/string.

Nevertheless I had already posted a working patch which uses a std::vector
and std::string instead to prevent such pointer problems.

 

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] Fix for the default configuration for CMAKE_INSTALL_CONFIG_NAME

[Roman Wüger]

Hello,



since version 3.1.0 CMake generates cmake_install.cmake files where the default configuration is empty.
(e.g.: set(CMAKE_INSTALL_CONFIG_NAME ))



In previous versions = 3.0.2 the default_config variable points to a NULL pointer for invalid configurations.
In later releases the variable points to valid objects, even if the configuration is empty.



Attached is a patch to fix this issue.



Best Regards

Roman

0001-Bugfix-Fix-default-config-for-CMAKE_INSTALL_CONFIG_N.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