[CMake] CPack [WiX] Customizations of individual features/components
Hello, I want to customize some with CPack generated *.wxs files. For example: directories.wxs is generated with only the TARGET_DIR. How can I add an additional directory in this file and use the newly added directory in the components (features.wxs)? I read about CPACK_WIX_PATCH_FILE. Maybe it is possible to do so with it, but if so how? Thanks in advance Regards Roman -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
[CMake] check_include_file for Objective C(++) triggers what looks like a clang bug (but probably isn't)
Hi, I've been trying to use the check_include_file() macro to verify if a particular ObjC header can be compiled. This turns out to be almost impossible, but I cannot put my finger on whether there isn't a compiler error involved too. Let's take the easier case for Mac OS X, where you don't have to install GNUstep. The following statement could be expected to work: check_include_file(Foundation/Foundation.h HAVE_FOUNDATION "-v -x objective-c") but it fails. The -x argument is required, the -v option is purely for debugging. The error from CMakeError.log is copied below; it seems that the intermediate object file is corrupt. However, the same symptoms occur with a comparable test file built the same way with clang: %> clang -x objective-c -c test.c %> clang -x objective-c test.o However, %> clang test.o and %> clang -x objective-c test.c work fine, and it's clear from the trace output that the -x option should NOT be passed to clang when it's used as a linker driver. Questions: - is there a more appropriate way to check if an Objective C header can be compiled? - is there a way to configure or set up things such that the trycompile functions use a single compiler invocation, or test only the object file generation (which should be enough for testing a headerfile)? Thank, René CMakeError.log extract: Building C object CMakeFiles/cmTC_61f5f.dir/CheckIncludeFile.c.o /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/cc -O3 -march=native -g -v -x objective-c -isystem /usr/include/GNUstep-o CMakeFiles/cmTC_61f5f.dir/CheckIncludeFile.c.o -c ...//src/MSWin/ SynchroTr/CMake/Release/CMakeFiles/CMakeTmp/CheckIncludeFile.c Apple LLVM version 6.0 (clang-600.0.57) (based on LLVM 3.5svn) Target: x86_64-apple-darwin13.4.0 Thread model: posix "/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang" -cc1 -triple x86_64-apple-macosx10.9 .0 -emit-obj -disable-free -disable-llvm-verifier -main-file-name CheckIncludeFile.c -mrelocation-model pic -pic-level 2 -mdisable-f p-elim -masm-verbose -munwind-tables -target-cpu corei7-avx -target-linker-version 241.9 -v -gdwarf-2 -coverage-file ...//src/MSWin/SynchroTr/CMake/Release/CMakeFiles/CMakeTmp/CMakeFiles/cmTC_61f5f.dir/CheckIncludeFile.c.o -resource-di r /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/clang/6.0 -isystem /usr/include/GNUs tep -I/opt/local/include -O3 -fdebug-compilation-dir ...//src/MSWin/SynchroTr/CMake/Release/CMakeFiles/ CMakeTmp -ferror-limit 19 -fmessage-length 0 -stack-protector 1 -mstackrealign -fblocks -fobjc-runtime=macosx-10.9.0 -fencode-extend ed-block-signature -fobjc-exceptions -fexceptions -fdiagnostics-show-option -vectorize-loops -vectorize-slp -o CMakeFiles/cmTC_61f5f .dir/CheckIncludeFile.c.o -x objective-c ...//src/MSWin/SynchroTr/CMake/Release/CMakeFiles/CMakeTmp/Che ckIncludeFile.c clang -cc1 version 6.0 based upon LLVM 3.5svn default target x86_64-apple-darwin13.4.0 ignoring nonexistent directory "/usr/include/GNUstep" #include "..." search starts here: #include <...> search starts here: /opt/local/include /usr/local/include /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/clang/6.0/include /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include /usr/include /System/Library/Frameworks (framework directory) /Library/Frameworks (framework directory) End of search list. Linking C executable cmTC_61f5f /opt/local/bin/cmake -E cmake_link_script CMakeFiles/cmTC_61f5f.dir/link.txt --verbose=1 /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/cc -O3 -march=native -g -v -x objective-c -isystem /usr/include/GNUstep -Wl,-search_paths_first -Wl,-headerpad_max_install_names CMakeFiles/cmTC_61f5f.dir/CheckIncludeFile.c.o -o cmTC_61f5f Apple LLVM version 6.0 (clang-600.0.57) (based on LLVM 3.5svn) Target: x86_64-apple-darwin13.4.0 Thread model: posix "/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang" -cc1 -triple x86_64-apple-macosx10.9.0 -emit-obj -disable-free -disable-llvm-verifier -main-file-name CheckIncludeFile.c.o -mrelocation-model pic -pic-level 2 -mdisable-fp-elim -masm-verbose -munwind-tables -target-cpu corei7-avx -target-linker-version 241.9 -v -gdwarf-2 -resource-dir /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/clang/6.0 -isystem /usr/include/GNUstep -I/opt/local/include -O3 -fdebug-compilation-dir ...//src/MSWin/SynchroTr/CMake/Release/CMakeFiles/CMakeTmp -ferror-limit 19 -fmessage-length 0 -stack-protector 1 -mstackrealign -fblocks -fobjc-runtime=macosx-10.9.0 -fencode-extended-block-signature -fobjc-exceptions -fexceptions -fdiagnostics-show-option -vectorize-loops -vectorize-slp -o /var/folders/j1/1439ppj08xj8h6006s6drbq0gs/T/Che
Re: [CMake] Converting Autoconf-based tests that compile/run a program and check its exit code
Il 29/09/2016 09:25, Eric Noulard ha scritto: > I guess that you should look at > > try_run command: > https://cmake.org/cmake/help/v3.6/command/try_run.html That's what I was looking for - I didn't catch that. Thank you very much! Cheers, Alessandro Menti -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
Re: [CMake] Converting Autoconf-based tests that compile/run a program and check its exit code
2016-09-29 9:13 GMT+02:00 Alessandro Menti : > Hi everyone, > I'm converting an Autoconf-based library (specifically, gettext [1]) to > CMake to be able to compile it easily on Windows and to mark it as a > dependency of another CMake-based project. > > I have come across a test [2] that compiles a small program, runs it and > checks its exit code to determine if some functions work correctly. > > 1) Is there a way to perform a similar check in CMake (maybe with a >custom module)? > I guess that you should look at try_run command: https://cmake.org/cmake/help/v3.6/command/try_run.html > 2) If not, what would be the best way to convert it? > > Thanks in advance, > Alessandro Menti > > [1] https://www.gnu.org/software/gettext/ > [2] > http://git.savannah.gnu.org/cgit/gettext.git/tree/gettext- > runtime/m4/fcntl-o.m4 > -- > > 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 > -- Eric -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
[CMake] Converting Autoconf-based tests that compile/run a program and check its exit code
Hi everyone, I'm converting an Autoconf-based library (specifically, gettext [1]) to CMake to be able to compile it easily on Windows and to mark it as a dependency of another CMake-based project. I have come across a test [2] that compiles a small program, runs it and checks its exit code to determine if some functions work correctly. 1) Is there a way to perform a similar check in CMake (maybe with a custom module)? 2) If not, what would be the best way to convert it? Thanks in advance, Alessandro Menti [1] https://www.gnu.org/software/gettext/ [2] http://git.savannah.gnu.org/cgit/gettext.git/tree/gettext-runtime/m4/fcntl-o.m4 -- 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
