Re: [CMake] CTest threshold exceeds 1024 bytes

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;

Re: [CMake] Fortran build dependency on Windows

Initial test seems to work, Will wait for the Nightly tests to verify that using custom target works. Allen On Tuesday, July 21, 2015 04:17:39 PM Brad King wrote: > On 07/21/2015 01:06 PM, Brad King wrote: > > It looks like OBJECT_DEPENDS is not fully implemented for VS >= 10. > > I'll look at f

Re: [CMake] OS X framework headers with capital letters

Thanks David, That change appears to have corrected the issue. Steve On Tue, Jul 21, 2015 at 4:30 PM, David Cole wrote: > Try putting ${FOO_HEADER_FILES} in the add_library call, too. > > I reproduced this by adding a file, with **ANY** name, to the > PUBLIC_HEADER list of the > [CMake/Tests/F

Re: [CMake] OS X framework headers with capital letters

Try putting ${FOO_HEADER_FILES} in the add_library call, too. I reproduced this by adding a file, with **ANY** name, to the PUBLIC_HEADER list of the [CMake/Tests/Framework/CMakeLists.txt](https://github.com/Kitware/CMake/blob/master/Tests/Framework/CMakeLists.txt) file... but NOT adding it to the

Re: [CMake] Fortran build dependency on Windows

On 07/21/2015 01:06 PM, Brad King wrote: > It looks like OBJECT_DEPENDS is not fully implemented for VS >= 10. > I'll look at fixing that. It turns out that is because .vcxproj files do not support it. The ClCompile task is documented here: https://msdn.microsoft.com/en-us/library/ee862477.aspx

Re: [CMake] OS X framework headers with capital letters

I am saying the file does not exist in the either installed framework or in the framework in the build directory. CMake is not moving the header files that start with a capital letter into the framework headers directory. Now I did double check and it *is* moving the .hpp header that matches th

[CMake] Option to halt on first error?

A user was confused just now by cmake continuing to output lots and lots of stuff after an error. How can we convince cmake to stop immediately upon first error? The error in this case was CMake Error at CMakeLists.txt:690 (add_executable): add_executable cannot create target "ImageClotTest" b

Re: [CMake] Possible to dynamically construct macro/function names to invoke?

On 07/20/2015 12:52 AM, Eric Wing wrote: > I would like to dynamically construct a macro or function name to > invoke. I basically have a core CMake system I want users to be able > to extend/plug stuff into without knowing about a lot of the core > CMake implementation. Callback functions would be

Re: [CMake] grep at build time?

On 07/18/2015 08:17 AM, Alexandre GOUAILLARD wrote: > dear all, > > I'm trying to use cmake as a super build script for another library > build system. > > Using add_custom_command and add_custom_target I have managed to > handle most of the steps so far. My libraries and executable are being > bui

Re: [CMake] Fortran build dependency on Windows

On 07/20/2015 05:10 PM, Allen Byrne wrote: > We use the OBJECT_DEPENDS property as follows; > > Environment: Windows 7, Visual Studio 2012, Intel Fortran 15, and CMake 3.1 It looks like OBJECT_DEPENDS is not fully implemented for VS >= 10. I'll look at fixing that. Meanwhile you can work around

Re: [CMake] OS X framework headers with capital letters

Are you saying the file does not exist in the installed framework, or that you do not see "copying Foo.h" in the install output ...? This seems very unlikely. The header files are supposed to be in the framework in the build tree, and the built framework in its entirety is supposed to be recursivel

Re: [CMake] OS X framework headers with capital letters

Well the definitely removes the case sensitivity issue. Do you have a compact example that shows the failure? I took a look in our project and we don't have any cases like this. I would find it a very odd and subtle bug it this really were an issue. one of those edge cases that just did not get

Re: [CMake] OS X framework headers with capital letters

Not to be picky, but the issue of case sensitivity ignores the original question. If it helps someone think about the issue better, change: set(FOO_HEADER_FILES "foo.h;bar.h;bat.h;Foo.h;Foo.hpp") to set(FOO_HEADER_FILES "bar.h;bat.h;Foo.h;Foo.hpp") Thanks, Steve On Tue, Jul 21, 2015 at 10:5

Re: [CMake] Difference in CMake 2.8 / 3.1+ behaviour when looking at SOURCES property

On 07/20/2015 03:45 PM, Berteun Damman wrote: > Note that it displays the full path for foo.txt! With later CMake > versions (3.1 and up is my suspicion), it will display: > > build$ cmake .. > foo.cc > foo.txt > > I tried looking trough the release notes, and I've found that > add_library gained

Re: [CMake] OS X framework headers with capital letters

to be very precise, OS X is a "Case Preserving but NOT Case sensitive" be default. OS X can be made to be case sensitive but no one actually recommends it. this means that on OS X foo.h and Foo.h resolve to be the same file, where as on Linux they would be 2 different files. You would have

Re: [CMake] OS X framework headers with capital letters

It can't installiert both foo.h and Foo.h in the mac, better correct your example. Am 21.07.2015 5:19 vorm. schrieb "Steven Wilson" < steven.wesley.wil...@gmail.com>: > I've noticed that CMake 3.3.0-rc3 will not install a header file in a Mac > OS X framework if the header file starts with a capi

Re: [CMake] find_package and lib/cmake/Foo

Have you tried setting CMAKE_PREFIX_PATH (http://www.cmake.org/cmake/help/v3.0/variable/CMAKE_PREFIX_PATH.html) as a -D option on the initial configure? On Tue, Jul 21, 2015 at 9:43 AM, Biddiscombe, John A. wrote: > Just to follow up my own question. I have found the answer > > export Foo_DIR=/my

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

Re: [CMake] find_package and lib/cmake/Foo

Just to follow up my own question. I have found the answer export Foo_DIR=/my/path/prefix followed by cmake ... will correctly locate the package unfortunately, cmake -DFoo_DIR=/my/path/prefix will not. Is there a reason why the cmake variable is not searched, whereas the env var is? thanks J

Re: [CMake] Toolchain file for VS2013 + November CTP compiler toolset?

On Fri, Jul 17, 2015 at 11:25 AM, Robert Dailey wrote: > Hello, > > How would I define a toolchain file for the Visual Studio 2013 > generator that also defines the toolset for that generator to be the > November CTP compiler? > > I'd rather use a toolchain for this than do -D definitions when I >

[CMake] find_package and lib/cmake/Foo

I've asked this before, but never resolved it... if I stall package Foo into CMAKE_INSTALL_PREFIX=/my/path/prefix and generate /my/path/prefix/lib/cmake/Foo/FooConfig.cmake etc then with Foo_DIR=/my/path/prefix Foo_ROOT=/my/path/prefix find_package(Foo) does not find package Foo One needs to set

[CMake] OS X framework headers with capital letters

I've noticed that CMake 3.3.0-rc3 will not install a header file in a Mac OS X framework if the header file starts with a capital letter (either that or has the same name as the framework). For example if I have the following: set(FOO_HEADER_FILES "foo.h;bar.h;bat.h;Foo.h;Foo.hpp") add_library(

[CMake] CTest threshold exceeds 1024 bytes

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 failur