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

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

[CMake] CPack and PackageMaker

Thanks for your work on this, I hope this can get into the main codebase soon. Currently we use internal productbuild and pkgbuild scripts from our pre-cmake days. Reading through your patch now I have some feedback: 1. Package ID: The pkgid for pkgbuild can often be something other than

Re: [CMake] How to use 'CMAKE_EXE_LINKER_FLAGS' correctly

If you know the full path to the library then I'd suggest using it as /path/to/foo/libfoo.a (or .so if it's shared) instead of -L/path/to/foo -lfoo. CMake will adjust the flags to -L and -l if needed but the preference is always to use the full library path. - Chuck On Mon, May 23, 2016 at 2:23

[CMake] Fwd: Using CPack to package things not built using CMake

Sorry, that should obviously have gone to this mailing list. -- Forwarded message -- From: Bruce Stephens Date: Mon, May 23, 2016 at 2:40 PM Subject: Using CPack to package things not built using CMake To: cmake-develop...@cmake.org Suppose I have a

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

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

[CMake] Introduction and Cmake's accessibility

Hi all. First, a brief intro. My name is Jaffar Sidek and I am a blind computer programmer and user from Singapore. Would also like to thank the list owner for helping me with my subscription since I couldn't get around to filling up the capture thingy on my own. I first came to know about

[CMake] INSTALL with PERMISSIONS changes the binary

Hi Everyone, I'm trying to solve a rather peculiar (at least to me) artifact of CMake's install(). I have a binary file (elf) that I call install() on to copy it and later package with CPack. Specifying no permissions results in a RPM extracting in 0444 mode, whereas specifying

Re: [CMake] How to Determine If a Perl Module Is Installed?

Bruce Stephens writes: > execute_process(COMMAND ${PERL_EXECUTABLE} -MSys::CPU -e "" > ERROR_QUIET RESULT_VARIABLE status) Thank you very much for the tip! The command above works very well for me. As a CMake newbie, I was afraid that I was overlooking some

Re: [CMake] How to Determine If a Perl Module Is Installed?

On Mon, May 23, 2016 at 11:30 PM, Eric Eide wrote: > Hi! I am a CMake newbie, and I have a question about examining the set of > available Perl modules on a system. > > In CMake (version 2.8.12+), how can I test for the presence of a particular > Perl module, e.g., "Sys::CPU"?

[CMake] How to Determine If a Perl Module Is Installed?

Hi! I am a CMake newbie, and I have a question about examining the set of available Perl modules on a system. In CMake (version 2.8.12+), how can I test for the presence of a particular Perl module, e.g., "Sys::CPU"? At the time that CMake is run, I would like to check for the presence of

Re: [CMake] How to use 'CMAKE_EXE_LINKER_FLAGS' correctly

Thanks a lot! `set(FOO_LIBRARY "-Wl,--whole-archive ${FOO_LIBRARY} -Wl,--no-whole-archive")` worked when the content of ${FOO_LIBRARY} look like `-Ldir -llib`, if just use lib name as the content of ${FOO_LIBRARY}, error while occur. Chuck Atkins wrote >> -rpath > > > RPATHs are automatically

[CMake] Empty ERROR_VARIABLE in execute_process

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

Re: [CMake] Cross Compilation & Source file generators

Just to clarify, although ParaView's superbuild assists you to set up and compile in either "compile TOOLS" or "CROSS compile" mode (or the default "HOST" mode) the protobuf inclusion I was speaking of in is found within paraview's source code and is not an external project. See

Re: [CMake] Empty ERROR_VARIABLE in execute_process

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 : > > Hello, > > when I run qmllint from the command line to test an

Re: [cmake-developers] the default value in CMake 3.5.2 for CMAKE_OSX_DEPLOYMENT_TARGET is too low for Xcode6

On 05/22/2016 01:27 AM, James Burgess wrote: > If you don’t set this you get 10.5. On any mac with Xcode 6 (7 is the latest) CMake's default value for CMAKE_OSX_DEPLOYMENT_TARGET is empty, which results in either no -mmacosx-version-min flag being used or in the host OS X version, depending on

Re: [cmake-developers] Developer tasks - Refactoring

On 05/19/2016 06:06 PM, Daniel Pfeifer wrote: >>> 1) Make cmLocalGenerator not inherit cmOutputConverter >>> * Change enums like cmLocalGenerator::START_OUTPUT with sed. See > Revised patch attached. Please ignore the previous one. > This one also fully qualifies the enums that were used

Re: [cmake-developers] CMake 3.5.2 conflates OSX SDK version with target deployment

On 05/22/2016 01:50 AM, James Burgess wrote: > $ cmake -D CMAKE_OSX_DEPLOYMENT_TARGET=10.8 . > CMAKE_OSX_DEPLOYMENT_TARGET is '10.8' but the matching SDK does not exist > at: > > > "/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.8.sdk" > >

Re: [cmake-developers] Custom commands with Ninja on Windows

On 05/23/2016 06:48 AM, Martin Ankerl wrote: > Here is an updated patch Thanks! > +#include This looks unnecessary. > +const std::string cmdFile = hasher.HashString(cmd.str()) + ".cmd"; > + > +// TODO fail if can't open file > +std::ofstream fout(cmdFile); Please use

Re: [cmake-developers] Empty ERROR_VARIABLE in execute_process

On 05/23/2016 03:25 AM, Roman Wüger wrote: > The output is: > > 1> _resVar: -1 > 1> _outVar: > 1> _errVar: > > It seems that the error pipe isn’t read correctly, because _errVar is empty. I cannot reproduce that. With an empty test.qml file I get: _resVar: -1 _outVar: _errVar:

Re: [cmake-developers] CMake 3.5.2 conflates OSX SDK version with target deployment

I'm away from keyboard until June 8th. everything written is from the top of my head. AFAIR the warning goes away if you properly set the OSX SYSROOT. Setting it to macosx without version number should be sufficient (maybe you have to insert a xcrun --showsdk-path there). As far as I see the

[cmake-developers] [PATCH] CPackIFW Updates

Hi again Brad! Sorry for my tardiness, and work in small pieces, but please accept my changes to CPack IFW generator (2 of the latest commit): commit 06ca7795f4c0a7503d98e856384f986a0047f811 CPackIFW: Command cpack_ifw_configure_component learned ESSENTIAL option commit

[Cmake-commits] CMake branch, next, updated. v3.5.2-1521-g05d0c64

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, next has been updated via 05d0c64015540df0512f2c5afcc27eb8af590748 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.5.2-1525-g3565b58

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, next has been updated via 3565b58ea8f6f54c9c8d3f6187361def72944672 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.5.2-1527-g75f46e9

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, next has been updated via 75f46e9143a5022405dffb5c1abd10355b4fee09 (commit) via

Re: [cmake-developers] Empty ERROR_VARIABLE in execute_process

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

[cmake-developers] Very minor doc update

A quick one, CPACK_DMG_FORMAT¶ The disk image format. Common values are UDRO (UDIF read-only), UDZO (UDIF zlib-compressed) or UDBZ (UDIF bzip2-compressed). Refer to hdiutil(1) for more information on other

[Cmake-commits] CMake branch, next, updated. v3.5.2-1523-gcd153d4

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, next has been updated via cd153d4e1865c3e1d5ac30277d6a0c15447a7bf8 (commit) via

Re: [cmake-developers] Custom commands with Ninja on Windows

On 05/23/2016 10:24 AM, Brad King wrote: > Please use cmGeneratedFileStream. Also please place the script files in the > CMakeFiles/ directory. See cmake::GetCMakeFilesDirectoryPostSlash callers > for examples. [snip] > Please also update the call sites for PRE_BUILD, PRE_LINK, and POST_BUILD >

Re: [cmake-developers] Very minor doc update

On 05/23/2016 01:24 PM, Harry Mallon wrote: > Defaults to UDZO. Thanks, applied: CPackDMG: Document CPACK_DMG_FORMAT default https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=239367f0 -Brad -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at:

Re: [cmake-developers] [PATCH] CPackIFW Updates

On 05/23/2016 12:21 PM, Konstantin Podsvirov wrote: > commit 06ca7795f4c0a7503d98e856384f986a0047f811 > > CPackIFW: Command cpack_ifw_configure_component learned ESSENTIAL option > > commit 222fa595cd6106cb6a4948eedeb55b0314338dff > > CPackIFW: Doc decoration Thanks. I've merged this topic

[Cmake-commits] CMake branch, next, updated. v3.5.2-1529-g201e524

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, next has been updated via 201e5242dfc8e3dd1af8bb5ffca76a61226c9195 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.5.2-1518-g093627b

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, next has been updated via 093627b6d828009e26d2108f69faf56670340930 (commit) via

Re: [cmake-developers] Empty ERROR_VARIABLE in execute_process

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

[Cmake-commits] CMake branch, master, updated. v3.5.2-736-gecb4ad2

_VERSION_MINOR 5) -set(CMake_VERSION_PATCH 20160523) +set(CMake_VERSION_PATCH 20160524) #set(CMake_VERSION_RC 1) --- Summary of changes: Source/CMakeVersion.cmake |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/

Re: [cmake-developers] the default value in CMake 3.5.2 for CMAKE_OSX_DEPLOYMENT_TARGET is too low for Xcode6

Hi Brad, Apologies, I didn’t look closely enough/didn’t understand that the discovery modules would be under influence of CMAKE_OSX_DEPLOYMENT_TARGET set from the CMakeFiles.txt, makes total sense now that you said that. This is the doxygen project, I just did a git clone of their latest.

[cmake-developers] Empty ERROR_VARIABLE in execute_process

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

Re: [cmake-developers] Custom commands with Ninja on Windows

Thanks for the feedback! Here is an updated patch that uses a hash as filename, .cmd as extension, boolean argument, and some error checks. Martin On Fri, May 20, 2016 at 3:40 PM Brad King wrote: > On 05/20/2016 03:41 AM, Martin Ankerl wrote: > > From what I have

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

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 : > > Hello, > > when I run qmllint from the command line to test an

[cmake-developers] Using CPack to package things not built using CMake

Suppose I have a build which uses a number of external projects (perhaps built using ExternalProject_Add) but which use a variety of build systems. And I want to package the result (so I arrange for the external projects to build expecting themselves to be installed under /opt/foo). What are

[Cmake-commits] CMake branch, master, updated. v3.5.2-733-g64d3613

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via 64d36131958c27dc135eea592f2c9944352d7544 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.5.2-735-gc75d91a

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via c75d91a05c9f442582726e3e80fec41d016da76f (commit) via

[Cmake-commits] CMake branch, master, updated. v3.5.2-731-g16b42d8

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via 16b42d842eb55989fc5ed5841b9e019872c78bf1 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.5.2-1516-g2033a96

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, next has been updated via 2033a966ff73e6e7a6d0a4d52555d565e6a1b88f (commit) via