http://blog.gmane.org/gmane.comp.programming.tools.cmake.user hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://comments.gmane.org/gmane.comp.programming.tools.cmake.user/46766 <pre>Hi, I have yet another static library order question when using target_link_libraries In my case, I've developed a new FindHDF5.cmake that calls the hdf5 compiler wrapper and sets the usual variables HDF5_&lt;lang&gt;_COMPILE_FLAGS, HDF5_&lt;lang&gt;_INCLUDE_PATH, HDF5_&lt;lang&gt;_LINK_FLAGS and HDF5_&lt;lang&gt;_LIBRARIES In my application I'm using both C and Fortran so I'm adding the libraries with: target_link_libraries(myapp ${HDF5_C_LIBRARIES} ${HDF5_Fortran_LIBRARIES}) I'm using this on a bluegene/q computer where the found libraries are HDF5_Fortran_LIBRARIES: /usr/local/hdf5/v1.8.10p1_serial/lib/libhdf5hl_fortran.a /usr/local/hdf5/v1.8.10p1_serial/lib/libhdf5_hl.a /usr/local/hdf5/v1.8.10p1_serial/lib/libhdf5_fortran.a /usr/local/hdf5/v1.8.10p1_serial/lib/libhdf5.a /usr/local/szip/lib/libsz.a;/usr/local/zlib/lib/libz.a /bgsys/drivers/toolchain/V1R2M0/gnu-linux/powerpc64-bgq-linux/lib/librt.a /bgsys/drivers/toolchain/V1R2M0/gnu-linux/powerpc64-bgq-linux/lib/libm.a HDF5_C_LIBRARIES: /usr/local/hdf5/v1.8.10p1_serial/lib/libhdf5_hl.a /usr/local/hdf5/v1.8.10p1_serial/lib/libhdf5.a /usr/local/szip/lib/libsz.a;/usr/local/zlib/lib/libz.a /bgsys/drivers/toolchain/V1R2M0/gnu-linux/powerpc64-bgq-linux/lib/librt.a /bgsys/drivers/toolchain/V1R2M0/gnu-linux/powerpc64-bgq-linux/lib/libm.a the order match the dependencies: hdf5hl_fortran -&gt; hdf5_hl + hdf5_fortran + hdf5 hdf5_hl -&gt; hdf5 hdf5_fortran -&gt; hdf5 However cmake removes duplicates from the library list in target_link_libraries ... unfortunately, it leaves the first duplicate and rmoves the following ones which results in the order "hdf5_hl hdf5 hdf5hl_fortran hdf5_fortran" That doesn't work due to the dependencies hdf5hl_fortran -&gt; hdf5_hl + hdf5 hdf5_fortran -&gt; hdf5 I don't get what I'm doing wrong here (apart from trying to use both static libs and cmake :/ ) ... For now I've worked around this problem by putting the C libs after the fortran ones in the call to target_link_libraries but I don't want to distribute my module with this limitation ... Could someone help me there ? Regards, </pre> Julien Bigot 2013-05-25T21:59:16 http://comments.gmane.org/gmane.comp.programming.tools.cmake.user/46765 <pre>It seems hard to find documentation for this variable. Is it set by enable_language(&lt;LANG&gt;)? Can I call enable_language(&lt;LANG&gt;) BEFORE I call project()? Does anyone know a good way to provide default, compiler specific values for CMAKE_&lt;LANG&gt;_FLAGS in the cache? It seems that calling set() with the CACHE option won't do anything if the variable is already set, and that perhaps CMAKE_&lt;LANG&gt;_FLAGS and CMAKE_&lt;LANG&gt;_COMPILER_ID are both set by project() and/or enable_language(). Do I need to define my own variable with a default value after CMAKE_&lt;LANG&gt;_COMPILER_ID is created (so that the default value is specific to the compiler) and then concatenate/append CMAKE_&lt;LANG&gt;_FLAGS with its value? Any and all help much appreciated, Izaak Beekman =================================== (301)244-9367 Princeton University Doctoral Candidate Mechanical and Aerospace Engineering ibeekman-uX/v2g6dJhCyum0STUha2w&lt; at &gt;public.gmane.org UMD-CP Visiting Graduate Student Aerospace Engineering ibeekman-+0HnD9Kv66LFajBVf7NWsQ&lt; at &gt;public.gmane.org ibeekman-e45ueOrobK4&lt; at &gt;public.gmane.org -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake</pre> Zaak Beekman 2013-05-25T18:49:48 http://comments.gmane.org/gmane.comp.programming.tools.cmake.user/46764 <pre>Does anyone have any experience adding tests to check for memory leaks on Macs? I come from more of a Linux background and am new to CMake and CTest. I am not using CDash yet, and writing software in C and Fortran. It seems that Valgrind is still very experimental for Mac, especially for Mountain lion, and produces unreliable/buggy results complaining about memory leaks which are allegedly in system libraries, etc. It seems that there is a 'leaks' tool that can be used to perform dynamic memory analysis, but you must attach it to the process after it's started. Is there a way to tell a process to start without actually executing, then attach leaks to it, and start/resume executing? Is there a better/different approach? Thanks, Izaak Beekman =================================== (301)244-9367 Princeton University Doctoral Candidate Mechanical and Aerospace Engineering ibeekman-uX/v2g6dJhCyum0STUha2w&lt; at &gt;public.gmane.org UMD-CP Visiting Graduate Student Aerospace Engineering ibeekman-+0HnD9Kv66LFajBVf7NWsQ&lt; at &gt;public.gmane.org ibeekman-e45ueOrobK4&lt; at &gt;public.gmane.org -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake</pre> Zaak Beekman 2013-05-25T18:40:56 http://comments.gmane.org/gmane.comp.programming.tools.cmake.user/46761 <pre>Hello, I have installed a very recent version of Cygwin on Windows 7 (64 bits) and the version of CMake that comes with it (2.8.9-2). When I use this however to configure and build projects that work fine under Windows (various versions0, then I get either configuration problems or build problems that turn out to be caused by a strange permission set on "configured" files. Using one of these projects I have created an almost minimal project to demonstrate the problem. If you configure it via CMake under Windows 7, the file "gnulliver.h" has "special permissions". I have no clue what that means or how it arises, but the consequence is that a program can not open it. Not even a program running under Administrator rights. Oddly enough, you can change the permissions from Windows Explorer by opening the permissions dialogue and giving the user full access. I have tried to reproduce it in an even smaller project than the one attached, that is: just a CMakeListst.txt file and gnulliver.h.in, but that worked without this problem. So it seems a combination of steps is required to trigger this issue. Can anyone shed some light on this? It makes it impossible to use Cygwin in combination with Windows 7 (I have not tried on other platforms, quite possibly it is specific to this combination.) Regards, Arjen DISCLAIMER: This message is intended exclusively for the addressee(s) and may contain confidential and privileged information. If you are not the intended recipient please notify the sender immediately and destroy this message. Unauthorized use, disclosure or copying of this message is strictly prohibited. The foundation 'Stichting Deltares', which has its seat at Delft, The Netherlands, Commercial Registration Number 41146461, is not liable in any way whatsoever for consequences and/or damages resulting from the improper, incomplete and untimely dispatch, receipt and/or content of this e-mail. -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake</pre> Arjen Markus 2013-05-25T11:06:12 http://comments.gmane.org/gmane.comp.programming.tools.cmake.user/46756 <pre>Hi all; We have a large-ish set of cmake files building our project which results in various executables, libraries, scripts, etc. Currently these are just left lying where they were created, and all our tests etc. expect to find them there. Then we then have a subsequent script that we run to collect the build products into a temporary staging area and create the installation packages (RPMs, EXEs, etc.) Then to run our tests on the packages we have to put them in a mode where they expect to find things in those "release" locations instead of the "build" location. This is annoying for many reasons and I want to change it so that the build installs into the staging area, which has the same layout as the package installation, then all our tests will use that layout and our packager can just package up that staging area with little extra work. I guess that the "install" capabilities of CMake are the right way to go about it. One major concern I have is that everyone has scripts, macros, etc. which just run "make", or use XCode or MSVC with the default target. If I make this change, then when people forget and run the default target instead of the "install" target they'll be running against the results of a previous build (when they did run the "install" step), not the results of the current build (where they forgot to run the "install" step). Much confusion and swearing will ensue. It doesn't take hardly any time to do the extra few file copies, so I just want to ALWAYS install to the staging area after building. Is there a way to make it so that the "install" step is the default step selected if you don't provide a different one? Or is CMake install capability not the right answer for this problem? Or, is a solution like this one: http://marc.info/?l=cmake&amp;m=130365717914933&amp;w=2 still the recommended way to handle a situation like this? Are there more "official" solutions available? -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake </pre> Paul Smith 2013-05-24T15:41:49 http://comments.gmane.org/gmane.comp.programming.tools.cmake.user/46755 <pre>Hi CMake, in our code we have different related CMake projects but CMake does not really know about dependencies between the projects. It would be handy to have only one CMakeCache.txt for all projects to reduce multiple execution of the Find*.cmake tests. Is there a possibility to define the path to the cache file? Or is there another way to handle this? Bye Christoph </pre> Christoph Grüninger 2013-05-24T15:28:29 http://comments.gmane.org/gmane.comp.programming.tools.cmake.user/46752 <pre>Hi, I just inherited a project which uses Qt GUI along with VTK and mingw-nmake under Windows 7 I installed the QT in a directory and added its bin folder to my path, then I tried to use cmake to built the VTK where I set the entry VTK_USE_QT to TRUE (I am using the cmake gui) but keep getting the error message:" Could NOT find Qt4 (missing: QT_MOC_EXECUTABLE QT_RCC_EXECUTABLE QT_UIC_EXECUTABLE) (found suitable version "4.8.4", required is "4.5.0") CMake Error at CMakeLists.txt:387 (MESSAGE): Qt 4.5.0 or greater not found. Please check the QT_QMAKE_EXECUTABLE variable. Qt QTSQL library not found. Qt QTSQL library not found. Qt QTNETWORK library not found. Qt QTSQL library not found. Configuring incomplete, errors occurred!" It seems like the message indicates that my QT version is not correct, but this is the only 64 bit version I found (http://superb-dca2.dl.sourceforge.net/project/mingwbuilds/external-binary-packages/Qt-Builds/Qt-4.8.4-x64.7z) &lt;http://superb-dca2.dl.sourceforge.net/project/mingwbuilds/external-binary-packages/Qt-Builds/Qt-4.8.4-x64.7z&gt; AND the person who used to work on the project said that that's the version I should be using. Any help will be appreciated (the person above cannot be contacted anymore) Thanks a lot &lt;http://superb-dca2.dl.sourceforge.net/project/mingwbuilds/external-binary-packages/Qt-Builds/Qt-4.8.4-x64.7z&gt; -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake</pre> Ronny Shalev 2013-05-24T13:43:25 http://comments.gmane.org/gmane.comp.programming.tools.cmake.user/46749 <pre>Hello All, I am kind of noob to CMake and this is my first question so i hope you all will not go hard on me :) . I am trying to build pyside and for that i need to build CMake for RHEL 5 machine, i follow the procedure mentioned in Readme.txt which is very straight forward. First i run the command: ./bootstrap --prefix=some path this operation generates lots of .o files but at the end gives me a following message: loading initial cache file /user/username/Desktop/pyside/cmake-2.8.11/Bootstrap.cmk/InitialCacheFlags.cmake </pre> Gargi Das 2013-05-24T04:31:38 http://comments.gmane.org/gmane.comp.programming.tools.cmake.user/46742 <pre>Hi I have noticed that the latest cmake release, 2.8.11, does not detect sgemm using check_function_exists macro from mkl_rt.lib library. The error message says; Cannot find C:\Program.obj It seems to me that the paths with spaces are no longer handled correctly. Installing the previous version, 2.8.10, everything works as expected. Also I have noticed that the 2.8.11 installer seems to create two entries in Windows program database. I am using Windows 8 x86_64 regards </pre> Bogdan Cristea 2013-05-23T16:59:14 http://comments.gmane.org/gmane.comp.programming.tools.cmake.user/46732 <pre>Hello, The maintener of Jenkins' xUnit plugin has added the support of CTest xml output format. It uses rpavlik xslt file to transform CTest xml format to JUnit's. https://wiki.jenkins-ci.org/display/JENKINS/xUnit+Plugin https://github.com/rpavlik/jenkins-ctest-plugin Regards, Gregoire -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake</pre> Gregoire Aujay 2013-05-22T07:44:58 http://comments.gmane.org/gmane.comp.programming.tools.cmake.user/46721 <pre>Hi, I am trying to checkout a specific revision of external dependencies from our repositoty using the SVN_REPOSITOTY parameter of ExternalProject_Add, but always get the following error: 2&gt; Creating directories for 'Hippomocks' 2&gt; Performing download step (SVN checkout) for 'Hippomocks' 2&gt; A Hippomocks\hippomocks\include 2&gt; A Hippomocks\hippomocks\include\hippomocks 2&gt; A Hippomocks\hippomocks\include\hippomocks\hippomocks.h 2&gt; A Hippomocks\hippomocks\CMakeLists.txt 2&gt; Checked out revision 8888. 2&gt; svn: E125002: '8887' does not appear to be a URL When I looked into the source code, I see that the command line for svn is created as set(cmd ${Subversion_SVN_EXECUTABLE} co ${svn_repository} ${svn_revision} --non-interactive ${svn_trust_cert_args} ${svn_user_pw_args} ${src_name}) According to the svn documentation page, I would have to give the revision with a special option -revision. Is this a bug or am I misinterpreting the ExternalProject_Add command parameters? Is SVN_REVISION the path in the repository I specify with SVN_REPOSITORY? -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake </pre> Jens Auer 2013-05-21T15:08:26 http://comments.gmane.org/gmane.comp.programming.tools.cmake.user/46720 <pre>Hi, A number of compilers have some options to do syntax checking, as well as produce warnings about questionable constructs. Does anyone know a good way to create phony targets based on the normal targets? e.g. in the compile step you pass flags like -warn -syntax-only and skip the linking step, as well as object file dependency checking. Note that I am using Fortran here, so the dependency graph still needs to be considered for the .mod files, which will be produced when -syntax-only is passed, but the object files will not be. It would be great if there was a way to do this, so that I could use flymake-mode in Emacs AND not have to completely build my project every time I save a source code file. (See for example, emacs-cmake-project &lt;https://github.com/alamaison/emacs-cmake-project&gt; on github.) Thanks, Izaak Beekman =================================== (301)244-9367 UMD-CP Visiting Graduate Student Aerospace Engineering ibeekman-+0HnD9Kv66LFajBVf7NWsQ&lt; at &gt;public.gmane.org ibeekman-e45ueOrobK4&lt; at &gt;public.gmane.org -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake</pre> Izaak Beekman 2013-05-21T13:37:05 http://comments.gmane.org/gmane.comp.programming.tools.cmake.user/46705 <pre>Not sure how to begin to investigate these but, I was surprised to see : $ gmake test Running tests... Test project /usr/local/build/cmake-2.8.11_SunOS5.10_sparcv9.001 Guessing configuration NoConfig Start 1: SystemInformationNew 1/270 Test #1: SystemInformationNew ............................. Passed 4.88 sec Start 2: cmIML.test 2/270 Test #2: cmIML.test ....................................... Passed 0.03 sec Start 3: kwsys.testEncode 3/270 Test #3: kwsys.testEncode ................................. Passed 0.01 sec Start 4: kwsys.testTerminal 4/270 Test #4: kwsys.testTerminal ............................... Passed 0.01 sec Start 5: kwsys.testAutoPtr 5/270 Test #5: kwsys.testAutoPtr ................................ Passed 0.02 sec Start 6: kwsys.testHashSTL 6/270 Test #6: kwsys.testHashSTL ................................ Passed 0.02 sec Start 7: kwsys.testIOS 7/270 Test #7: kwsys.testIOS .................................... Passed 0.02 sec Start 8: kwsys.testSystemTools 8/270 Test #8: kwsys.testSystemTools ............................ Passed 0.02 sec Start 9: kwsys.testCommandLineArguments 9/270 Test #9: kwsys.testCommandLineArguments ................... Passed 0.05 sec Start 10: kwsys.testCommandLineArguments1 10/270 Test #10: kwsys.testCommandLineArguments1 .................. Passed 0.02 sec Start 11: kwsys.testSystemInformation 11/270 Test #11: kwsys.testSystemInformation ...................... Passed 0.66 sec Start 12: kwsys.testDynamicLoader 12/270 Test #12: kwsys.testDynamicLoader .......................... Passed 0.02 sec Start 13: kwsys.testProcess-1 13/270 Test #13: kwsys.testProcess-1 .............................. Passed 0.02 sec Start 14: kwsys.testProcess-2 14/270 Test #14: kwsys.testProcess-2 .............................. Passed 0.02 sec Start 15: kwsys.testProcess-3 15/270 Test #15: kwsys.testProcess-3 .............................. Passed 10.04 sec Start 16: kwsys.testProcess-4 16/270 Test #16: kwsys.testProcess-4 .............................. Passed 0.52 sec Start 17: kwsys.testProcess-5 17/270 Test #17: kwsys.testProcess-5 .............................. Passed 0.75 sec Start 18: kwsys.testProcess-6 18/270 Test #18: kwsys.testProcess-6 .............................. Passed 10.04 sec Start 19: kwsys.testProcess-7 19/270 Test #19: kwsys.testProcess-7 .............................. Passed 1.22 sec Start 20: kwsys.testSharedForward 20/270 Test #20: kwsys.testSharedForward .......................... Passed 0.03 sec Start 21: CMake.HTML 21/270 Test #21: CMake.HTML ....................................... Passed 2.03 sec Start 22: CMake.DocBook 22/270 Test #22: CMake.DocBook .................................... Passed 3.59 sec Start 23: CommandLineTest 23/270 Test #23: CommandLineTest .................................. Passed 21.84 sec Start 24: FindPackageTest 24/270 Test #24: FindPackageTest ..................................***Failed 13.31 sec Start 25: FindModulesExecuteAll 25/270 Test #25: FindModulesExecuteAll ............................ Passed 121.28 sec Start 26: StringFileTest 26/270 Test #26: StringFileTest ................................... Passed 7.00 sec Start 27: TryCompile 27/270 Test #27: TryCompile ....................................... Passed 27.81 sec Start 28: TarTest 28/270 Test #28: TarTest .......................................... Passed 9.25 sec Start 29: SystemInformation 29/270 Test #29: SystemInformation ................................ Passed 8.94 sec Start 30: MathTest 30/270 Test #30: MathTest ......................................... Passed 5.98 sec Start 31: Simple 31/270 Test #31: Simple ........................................... Passed 7.47 sec Start 32: PreOrder 32/270 Test #32: PreOrder ......................................... Passed 7.00 sec Start 33: MissingSourceFile 33/270 Test #33: MissingSourceFile ................................ Passed 2.06 sec Start 34: FortranOnly 34/270 Test #34: FortranOnly ...................................... Passed 7.90 sec Start 35: VSGNUFortran 35/270 Test #35: VSGNUFortran .....................................***Failed 23.06 sec Start 36: COnly 36/270 Test #36: COnly ............................................ Passed 6.09 sec Start 37: CxxOnly 37/270 Test #37: CxxOnly .......................................... Passed 6.83 sec Start 38: IPO 38/270 Test #38: IPO .............................................. Passed 12.54 sec Start 39: OutDir 39/270 Test #39: OutDir ........................................... Passed 7.35 sec Start 40: ObjectLibrary 40/270 Test #40: ObjectLibrary .................................... Passed 13.63 sec Start 41: NewlineArgs 41/270 Test #41: NewlineArgs ...................................... Passed 5.05 sec Start 42: SetLang 42/270 Test #42: SetLang .......................................... Passed 6.93 sec Start 43: ExternalOBJ 43/270 Test #43: ExternalOBJ ...................................... Passed 10.61 sec Start 44: LoadCommand 44/270 Test #44: LoadCommand ...................................... Passed 12.49 sec Start 45: LinkDirectory 45/270 Test #45: LinkDirectory .................................... Passed 13.05 sec Start 46: LinkLanguage 46/270 Test #46: LinkLanguage ..................................... Passed 6.81 sec Start 47: LinkLine 47/270 Test #47: LinkLine ......................................... Passed 7.49 sec Start 48: MacroTest 48/270 Test #48: MacroTest ........................................ Passed 6.47 sec Start 49: FunctionTest 49/270 Test #49: FunctionTest ..................................... Passed 6.20 sec Start 50: ReturnTest 50/270 Test #50: ReturnTest ....................................... Passed 6.01 sec Start 51: Properties 51/270 Test #51: Properties ....................................... Passed 6.00 sec Start 52: Assembler 52/270 Test #52: Assembler ........................................ Passed 3.78 sec Start 53: SourceGroups 53/270 Test #53: SourceGroups ..................................... Passed 6.92 sec Start 54: Preprocess 54/270 Test #54: Preprocess ....................................... Passed 6.50 sec Start 55: ExportImport 55/270 Test #55: ExportImport ..................................... Passed 54.76 sec Start 56: Unset 56/270 Test #56: Unset ............................................ Passed 3.43 sec Start 57: PolicyScope 57/270 Test #57: PolicyScope ...................................... Passed 3.57 sec Start 58: EmptyLibrary 58/270 Test #58: EmptyLibrary ..................................... Passed 4.46 sec Start 59: CompileDefinitions 59/270 Test #59: CompileDefinitions ............................... Passed 8.88 sec Start 60: CompatibleInterface 60/270 Test #60: CompatibleInterface .............................. Passed 10.24 sec Start 61: CrossCompile 61/270 Test #61: CrossCompile ..................................... Passed 4.95 sec Start 62: Policy0002 62/270 Test #62: Policy0002 ....................................... Passed 4.27 sec Start 63: CMakeBuildTest 63/270 Test #63: CMakeBuildTest ................................... Passed 8.32 sec Start 64: CMakeDoubleProject 64/270 Test #64: CMakeDoubleProject ............................... Passed 6.81 sec Start 65: Module.CheckTypeSize 65/270 Test #65: Module.CheckTypeSize ............................. Passed 12.67 sec Start 66: Module.ExternalData 66/270 Test #66: Module.ExternalData .............................. Passed 24.21 sec Start 67: Module.GenerateExportHeader 67/270 Test #67: Module.GenerateExportHeader ...................... Passed 119.34 sec Start 68: PositionIndependentTargets 68/270 Test #68: PositionIndependentTargets ....................... Passed 12.53 sec Start 69: LinkFlags-prepare 69/270 Test #69: LinkFlags-prepare ................................ Passed 4.31 sec Start 70: LinkFlags-lib 70/270 Test #70: LinkFlags-lib .................................... Passed 1.06 sec Start 71: LinkFlags-dll 71/270 Test #71: LinkFlags-dll .................................... Passed 1.02 sec Start 72: LinkFlags-exe 72/270 Test #72: LinkFlags-exe .................................... Passed 1.01 sec Start 73: LinkFlags-lib_config 73/270 Test #73: LinkFlags-lib_config ............................. Passed 1.06 sec Start 74: LinkFlags-dll_config 74/270 Test #74: LinkFlags-dll_config ............................. Passed 1.01 sec Start 75: LinkFlags-exe_config 75/270 Test #75: LinkFlags-exe_config ............................. Passed 1.02 sec Start 76: SubProject 76/270 Test #76: SubProject ....................................... Passed 6.21 sec Start 77: SubProject-Stage2 77/270 Test #77: SubProject-Stage2 ................................ Passed 2.16 sec Start 78: Framework 78/270 Test #78: Framework ........................................ Passed 12.12 sec Start 79: TargetName 79/270 Test #79: TargetName ....................................... Passed 6.03 sec Start 80: LibName 80/270 Test #80: LibName .......................................... Passed 9.11 sec Start 81: CustComDepend 81/270 Test #81: CustComDepend .................................... Passed 6.90 sec Start 82: ArgumentExpansion 82/270 Test #82: ArgumentExpansion ................................ Passed 4.81 sec Start 83: GeneratorExpression 83/270 Test #83: GeneratorExpression .............................. Passed 8.82 sec Start 84: CustomCommand 84/270 Test #84: CustomCommand .................................... Passed 25.16 sec Start 85: EmptyDepends 85/270 Test #85: EmptyDepends ..................................... Passed 10.76 sec Start 86: CustomCommandWorkingDirectory 86/270 Test #86: CustomCommandWorkingDirectory .................... Passed 8.29 sec Start 87: OutOfSource 87/270 Test #87: OutOfSource ...................................... Passed 8.70 sec Start 88: BuildDepends 88/270 Test #88: BuildDepends ..................................... Passed 19.92 sec Start 89: SimpleInstall 89/270 Test #89: SimpleInstall .................................... Passed 24.70 sec Start 90: SimpleInstall-Stage2 90/270 Test #90: SimpleInstall-Stage2 ............................. Passed 11.47 sec Start 91: CPackComponents 91/270 Test #91: CPackComponents .................................. Passed 16.28 sec Start 92: CPackComponentsForAll-ZIP-default 92/270 Test #92: CPackComponentsForAll-ZIP-default ................ Passed 11.78 sec Start 93: CPackComponentsForAll-ZIP-OnePackPerGroup 93/270 Test #93: CPackComponentsForAll-ZIP-OnePackPerGroup ........ Passed 11.74 sec Start 94: CPackComponentsForAll-ZIP-IgnoreGroup 94/270 Test #94: CPackComponentsForAll-ZIP-IgnoreGroup ............ Passed 11.33 sec Start 95: CPackComponentsForAll-ZIP-AllInOne 95/270 Test #95: CPackComponentsForAll-ZIP-AllInOne ............... Passed 11.59 sec Start 96: CPackTestAllGenerators 96/270 Test #96: CPackTestAllGenerators ........................... Passed 23.28 sec Start 97: X11 97/270 Test #97: X11 .............................................. Passed 20.61 sec Start 98: CMakeTestAllGenerators 98/270 Test #98: CMakeTestAllGenerators ........................... Passed 32.41 sec Start 99: CMakeTestBadCommandLines 99/270 Test #99: CMakeTestBadCommandLines ......................... Passed 15.28 sec Start 100: CMakeTestMultipleConfigures 100/270 Test #100: CMakeTestMultipleConfigures ...................... Passed 13.25 sec Start 101: LoadedCommandOneConfig 101/270 Test #101: LoadedCommandOneConfig ........................... Passed 13.15 sec Start 103: complexOneConfig 102/270 Test #103: complexOneConfig ................................. Passed 36.95 sec Start 102: complex 103/270 Test #102: complex .......................................... Passed 38.64 sec Start 104: Example 104/270 Test #104: Example .......................................... Passed 7.02 sec Start 105: Environment 105/270 Test #105: Environment ...................................... Passed 6.06 sec Start 106: QtAutomocNoQt 106/270 Test #106: QtAutomocNoQt .................................... Passed 5.54 sec Start 107: ExternalProject 107/270 Test #107: ExternalProject .................................. Passed 77.25 sec Start 108: ExternalProjectUpdateSetup 108/270 Test #108: ExternalProjectUpdateSetup ....................... Passed 1.14 sec Start 109: ExternalProjectUpdate 109/270 Test #109: ExternalProjectUpdate ............................ Passed 0.18 sec Start 110: TutorialStep1 110/270 Test #110: TutorialStep1 .................................... Passed 6.02 sec Start 111: TutorialStep2 111/270 Test #111: TutorialStep2 .................................... Passed 7.10 sec Start 112: TutorialStep3 112/270 Test #112: TutorialStep3 .................................... Passed 7.20 sec Start 113: TutorialStep4 113/270 Test #113: TutorialStep4 .................................... Passed 8.36 sec Start 114: TutorialStep5 114/270 Test #114: TutorialStep5 .................................... Passed 9.52 sec Start 115: TutorialStep6 115/270 Test #115: TutorialStep6 .................................... Passed 11.54 sec Start 116: TutorialStep7 116/270 Test #116: TutorialStep7 .................................... Passed 16.01 sec Start 117: testing 117/270 Test #117: testing .......................................... Passed 13.97 sec Start 118: wrapping 118/270 Test #118: wrapping ......................................... Passed 11.29 sec Start 119: qtwrapping 119/270 Test #119: qtwrapping ....................................... Passed 7.12 sec Start 120: testdriver1 120/270 Test #120: testdriver1 ...................................... Passed 7.60 sec Start 121: testdriver2 121/270 Test #121: testdriver2 ...................................... Passed 3.47 sec Start 122: testdriver3 122/270 Test #122: testdriver3 ...................................... Passed 3.47 sec Start 123: Dependency 123/270 Test #123: Dependency ....................................... Passed 36.32 sec Start 124: JumpWithLibOut 124/270 Test #124: JumpWithLibOut ................................... Passed 7.68 sec Start 125: JumpNoLibOut 125/270 Test #125: JumpNoLibOut ..................................... Passed 7.70 sec Start 126: Plugin 126/270 Test #126: Plugin ........................................... Passed 33.99 sec Start 127: RuntimePath 127/270 Test #127: RuntimePath ...................................... Passed 6.66 sec Start 128: linkorder1 128/270 Test #128: linkorder1 ....................................... Passed 14.54 sec Start 129: linkorder2 129/270 Test #129: linkorder2 ....................................... Passed 10.38 sec Start 130: kwsys 130/270 Test #130: kwsys ............................................ Passed 85.38 sec Start 131: SubDirSpaces 131/270 Test #131: SubDirSpaces ..................................... Passed 9.47 sec Start 132: SubDir 132/270 Test #132: SubDir ........................................... Passed 9.39 sec Start 133: CheckCompilerRelatedVariables 133/270 Test #133: CheckCompilerRelatedVariables .................... Passed 6.01 sec Start 134: MakeClean 134/270 Test #134: MakeClean ........................................ Passed 12.01 sec Start 135: WarnUnusedUnusedViaSet 135/270 Test #135: WarnUnusedUnusedViaSet ........................... Passed 5.45 sec Start 136: WarnUnusedUnusedViaUnset 136/270 Test #136: WarnUnusedUnusedViaUnset ......................... Passed 5.43 sec Start 137: WarnUnusedCliUnused 137/270 Test #137: WarnUnusedCliUnused .............................. Passed 4.76 sec Start 138: WarnUnusedCliUsed 138/270 Test #138: WarnUnusedCliUsed ................................ Passed 4.74 sec Start 139: WarnUninitialized 139/270 Test #139: WarnUninitialized ................................ Passed 4.75 sec Start 140: TestsWorkingDirectory 140/270 Test #140: TestsWorkingDirectory ............................ Passed 6.01 sec Start 141: CTest.NoNewline 141/270 Test #141: CTest.NoNewline .................................. Passed 0.07 sec Start 142: CTestTestNoBuild 142/270 Test #142: CTestTestNoBuild ................................. Passed 7.16 sec Start 143: CTestTestNoExe 143/270 Test #143: CTestTestNoExe ................................... Passed 0.69 sec Start 144: CTestTestUpload 144/270 Test #144: CTestTestUpload .................................. Passed 9.18 sec Start 145: CTestTestConfigFileInBuildDir1 145/270 Test #145: CTestTestConfigFileInBuildDir1 ................... Passed 5.63 sec Start 146: CTestTestConfigFileInBuildDir2 146/270 Test #146: CTestTestConfigFileInBuildDir2 ................... Passed 5.61 sec Start 147: CTestGTMCoverage 147/270 Test #147: CTestGTMCoverage ................................. Passed 1.25 sec Start 148: CTestCacheCoverage 148/270 Test #148: CTestCacheCoverage ............................... Passed 1.04 sec Start 149: CTestConfig.Script.Debug 149/270 Test #149: CTestConfig.Script.Debug ......................... Passed 7.66 sec Start 150: CTestConfig.Dashboard.Debug 150/270 Test #150: CTestConfig.Dashboard.Debug ...................... Passed 8.78 sec Start 151: CTestConfig.Script.MinSizeRel 151/270 Test #151: CTestConfig.Script.MinSizeRel .................... Passed 7.80 sec Start 152: CTestConfig.Dashboard.MinSizeRel 152/270 Test #152: CTestConfig.Dashboard.MinSizeRel ................. Passed 8.86 sec Start 153: CTestConfig.Script.Release 153/270 Test #153: CTestConfig.Script.Release ....................... Passed 7.77 sec Start 154: CTestConfig.Dashboard.Release 154/270 Test #154: CTestConfig.Dashboard.Release .................... Passed 8.90 sec Start 155: CTestConfig.Script.RelWithDebInfo 155/270 Test #155: CTestConfig.Script.RelWithDebInfo ................ Passed 7.75 sec Start 156: CTestConfig.Dashboard.RelWithDebInfo 156/270 Test #156: CTestConfig.Dashboard.RelWithDebInfo ............. Passed 8.86 sec Start 157: CTestConfig.ScriptWithArgs 157/270 Test #157: CTestConfig.ScriptWithArgs ....................... Passed 0.20 sec Start 158: CMakeCommands.target_link_libraries 158/270 Test #158: CMakeCommands.target_link_libraries .............. Passed 20.22 sec Start 159: CMakeCommands.target_include_directories 159/270 Test #159: CMakeCommands.target_include_directories ......... Passed 6.92 sec Start 160: CMakeCommands.target_compile_definitions 160/270 Test #160: CMakeCommands.target_compile_definitions ......... Passed 6.86 sec Start 161: CTestTestCrash 161/270 Test #161: CTestTestCrash ................................... Passed 8.51 sec Start 162: CTestTestBadExe 162/270 Test #162: CTestTestBadExe .................................. Passed 6.88 sec Start 163: CTestTestParallel 163/270 Test #163: CTestTestParallel ................................ Passed 9.42 sec Start 164: CTestLimitDashJ 164/270 Test #164: CTestLimitDashJ .................................. Passed 38.28 sec Start 165: CTestTestPrintLabels 165/270 Test #165: CTestTestPrintLabels ............................. Passed 0.35 sec Start 166: CTestTestResourceLock 166/270 Test #166: CTestTestResourceLock ............................ Passed 8.73 sec Start 167: CTestTestScheduler 167/270 Test #167: CTestTestScheduler ............................... Passed 40.09 sec Start 168: CTestTestCostSerial 168/270 Test #168: CTestTestCostSerial .............................. Passed 14.14 sec Start 169: CTestTestStopTime 169/270 Test #169: CTestTestStopTime ................................ Passed 22.68 sec Start 170: CTestTestSubdir 170/270 Test #170: CTestTestSubdir .................................. Passed 9.00 sec Start 171: CTestTestTimeout 171/270 Test #171: CTestTestTimeout ................................. Passed 13.77 sec Start 172: CTestTestZeroTimeout 172/270 Test #172: CTestTestZeroTimeout ............................. Passed 12.57 sec Start 173: CTestTestDepends 173/270 Test #173: CTestTestDepends ................................. Passed 7.72 sec Start 174: CTestTestCycle 174/270 Test #174: CTestTestCycle ................................... Passed 7.64 sec Start 175: CTestTestRunScript 175/270 Test #175: CTestTestRunScript ............................... Passed 0.31 sec Start 176: CTestTestShowOnly 176/270 Test #176: CTestTestShowOnly ................................ Passed 0.46 sec Start 177: CTestBatchTest 177/270 Test #177: CTestBatchTest ................................... Passed 0.42 sec Start 178: CTestTestFailedSubmit-cp 178/270 Test #178: CTestTestFailedSubmit-cp ......................... Passed 4.30 sec Start 179: CTestTestFailedSubmit-ftp 179/270 Test #179: CTestTestFailedSubmit-ftp ........................ Passed 4.49 sec Start 180: CTestTestFailedSubmit-http 180/270 Test #180: CTestTestFailedSubmit-http ....................... Passed 4.66 sec Start 181: CTestTestFailedSubmit-https 181/270 Test #181: CTestTestFailedSubmit-https ...................... Passed 4.58 sec Start 182: CTestTestFailedSubmit-scp 182/270 Test #182: CTestTestFailedSubmit-scp ........................ Passed 4.29 sec Start 183: CTestTestFailedSubmit-xmlrpc 183/270 Test #183: CTestTestFailedSubmit-xmlrpc ..................... Passed 4.30 sec Start 184: Fortran 184/270 Test #184: Fortran ..........................................***Failed 23.03 sec Start 185: FortranC.Flags 185/270 Test #185: FortranC.Flags ...................................***Failed 20.81 sec Start 186: CMakeWizardTest 186/270 Test #186: CMakeWizardTest .................................. Passed 1.34 sec Start 187: CompileCommandOutput 187/270 Test #187: CompileCommandOutput ............................. Passed 6.49 sec Start 188: IncludeDirectories 188/270 Test #188: IncludeDirectories ............................... Passed 16.31 sec Start 189: CMakeLib.testGeneratedFileStream 189/270 Test #189: CMakeLib.testGeneratedFileStream ................. Passed 0.08 sec Start 190: CMakeLib.testSystemTools 190/270 Test #190: CMakeLib.testSystemTools ......................... Passed 0.07 sec Start 191: CMakeLib.testUTF8 191/270 Test #191: CMakeLib.testUTF8 ................................ Passed 0.07 sec Start 192: CMakeLib.testXMLParser 192/270 Test #192: CMakeLib.testXMLParser ........................... Passed 0.07 sec Start 193: CMakeLib.testXMLSafe 193/270 Test #193: CMakeLib.testXMLSafe ............................. Passed 0.07 sec Start 194: CMakeOnly.LinkInterfaceLoop 194/270 Test #194: CMakeOnly.LinkInterfaceLoop ...................... Passed 2.28 sec Start 195: CMakeOnly.CheckSymbolExists 195/270 Test #195: CMakeOnly.CheckSymbolExists ...................... Passed 5.13 sec Start 196: CMakeOnly.CheckCXXSymbolExists 196/270 Test #196: CMakeOnly.CheckCXXSymbolExists ................... Passed 6.40 sec Start 197: CMakeOnly.CheckCXXCompilerFlag 197/270 Test #197: CMakeOnly.CheckCXXCompilerFlag ................... Passed 5.29 sec Start 198: CMakeOnly.CheckLanguage 198/270 Test #198: CMakeOnly.CheckLanguage .......................... Passed 8.22 sec Start 199: CMakeOnly.CompilerIdC 199/270 Test #199: CMakeOnly.CompilerIdC ............................ Passed 2.18 sec Start 200: CMakeOnly.CompilerIdCXX 200/270 Test #200: CMakeOnly.CompilerIdCXX .......................... Passed 2.69 sec Start 201: CMakeOnly.CompilerIdFortran 201/270 Test #201: CMakeOnly.CompilerIdFortran ...................... Passed 3.03 sec Start 202: CMakeOnly.AllFindModules 202/270 Test #202: CMakeOnly.AllFindModules ......................... Passed 75.68 sec Start 203: CMakeOnly.SelectLibraryConfigurations 203/270 Test #203: CMakeOnly.SelectLibraryConfigurations ............ Passed 0.46 sec Start 204: CMakeOnly.TargetScope 204/270 Test #204: CMakeOnly.TargetScope ............................ Passed 0.43 sec Start 205: CMakeOnly.find_library 205/270 Test #205: CMakeOnly.find_library ........................... Passed 0.46 sec Start 206: CMakeOnly.find_path 206/270 Test #206: CMakeOnly.find_path .............................. Passed 0.38 sec Start 207: CMakeOnly.ProjectInclude 207/270 Test #207: CMakeOnly.ProjectInclude ......................... Passed 4.52 sec Start 208: CMakeOnly.MajorVersionSelection-PythonLibs_2 208/270 Test #208: CMakeOnly.MajorVersionSelection-PythonLibs_2 ..... Passed 5.03 sec Start 209: CMakeOnly.MajorVersionSelection-PythonLibs_3 209/270 Test #209: CMakeOnly.MajorVersionSelection-PythonLibs_3 ..... Passed 5.47 sec Start 210: CMakeOnly.MajorVersionSelection-PythonInterp_2 210/270 Test #210: CMakeOnly.MajorVersionSelection-PythonInterp_2 ... Passed 0.54 sec Start 211: CMakeOnly.MajorVersionSelection-PythonInterp_3 211/270 Test #211: CMakeOnly.MajorVersionSelection-PythonInterp_3 ... Passed 0.53 sec Start 212: CMakeOnly.MajorVersionSelection-Qt_3 212/270 Test #212: CMakeOnly.MajorVersionSelection-Qt_3 ............. Passed 6.60 sec Start 213: CMakeOnly.MajorVersionSelection-Qt_4 213/270 Test #213: CMakeOnly.MajorVersionSelection-Qt_4 ............. Passed 4.85 sec Start 214: RunCMake.CMP0019 214/270 Test #214: RunCMake.CMP0019 ................................. Passed 1.05 sec Start 215: RunCMake.CTest 215/270 Test #215: RunCMake.CTest ................................... Passed 0.36 sec Start 216: RunCMake.CompilerChange 216/270 Test #216: RunCMake.CompilerChange .......................... Passed 7.38 sec Start 217: RunCMake.ExternalData 217/270 Test #217: RunCMake.ExternalData ............................ Passed 9.85 sec Start 218: RunCMake.FPHSA 218/270 Test #218: RunCMake.FPHSA ................................... Passed 0.43 sec Start 219: RunCMake.GeneratorExpression 219/270 Test #219: RunCMake.GeneratorExpression ..................... Passed 2.47 sec Start 220: RunCMake.GeneratorToolset 220/270 Test #220: RunCMake.GeneratorToolset ........................ Passed 0.63 sec Start 221: RunCMake.TargetPropertyGeneratorExpressions 221/270 Test #221: RunCMake.TargetPropertyGeneratorExpressions ...... Passed 39.69 sec Start 222: RunCMake.Languages 222/270 Test #222: RunCMake.Languages ............................... Passed 0.41 sec Start 223: RunCMake.ObjectLibrary 223/270 Test #223: RunCMake.ObjectLibrary ........................... Passed 35.94 sec Start 224: RunCMake.PositionIndependentCode 224/270 Test #224: RunCMake.PositionIndependentCode ................. Passed 8.04 sec Start 225: RunCMake.CompatibleInterface 225/270 Test #225: RunCMake.CompatibleInterface ..................... Passed 23.89 sec Start 226: RunCMake.add_dependencies 226/270 Test #226: RunCMake.add_dependencies ........................ Passed 0.37 sec Start 227: RunCMake.build_command 227/270 Test #227: RunCMake.build_command ........................... Passed 0.93 sec Start 228: RunCMake.find_package 228/270 Test #228: RunCMake.find_package ............................ Passed 4.33 sec Start 229: RunCMake.include 229/270 Test #229: RunCMake.include ................................. Passed 0.67 sec Start 230: RunCMake.include_directories 230/270 Test #230: RunCMake.include_directories .....................***Failed 9.66 sec Start 231: RunCMake.list 231/270 Test #231: RunCMake.list .................................... Passed 0.87 sec Start 232: RunCMake.CMP0004 232/270 Test #232: RunCMake.CMP0004 ................................. Passed 1.12 sec Start 233: FindPackageModeMakefileTest 233/270 Test #233: FindPackageModeMakefileTest ...................... Passed 1.06 sec Start 234: CTestTestMemcheckUnknown 234/270 Test #234: CTestTestMemcheckUnknown ......................... Passed 0.24 sec Start 235: CTestTestMemcheckUnknownQuoted 235/270 Test #235: CTestTestMemcheckUnknownQuoted ................... Passed 0.24 sec Start 236: CTestTestMemcheckNotExist 236/270 Test #236: CTestTestMemcheckNotExist ........................ Passed 0.24 sec Start 237: CTestTestMemcheckDummyValgrind 237/270 Test #237: CTestTestMemcheckDummyValgrind ................... Passed 6.71 sec Start 238: CTestTestMemcheckDummyValgrindPrePost 238/270 Test #238: CTestTestMemcheckDummyValgrindPrePost ............ Passed 6.72 sec Start 239: CTestTestMemcheckDummyValgrindFailPre 239/270 Test #239: CTestTestMemcheckDummyValgrindFailPre ............ Passed 6.24 sec Start 240: CTestTestMemcheckDummyValgrindFailPost 240/270 Test #240: CTestTestMemcheckDummyValgrindFailPost ........... Passed 6.72 sec Start 241: CTestTestMemcheckDummyPurify 241/270 Test #241: CTestTestMemcheckDummyPurify ..................... Passed 6.71 sec Start 242: CTestTestMemcheckDummyBC 242/270 Test #242: CTestTestMemcheckDummyBC ......................... Passed 6.68 sec Start 243: CTestTestMemcheckDummyValgrindIgnoreMemcheck 243/270 Test #243: CTestTestMemcheckDummyValgrindIgnoreMemcheck ..... Passed 6.86 sec Start 244: CMake.List 244/270 Test #244: CMake.List ....................................... Passed 3.65 sec Start 245: CMake.VariableWatch 245/270 Test #245: CMake.VariableWatch .............................. Passed 0.12 sec Start 246: CMake.Include 246/270 Test #246: CMake.Include .................................... Passed 0.13 sec Start 247: CMake.FindBase 247/270 Test #247: CMake.FindBase ................................... Passed 0.14 sec Start 248: CMake.Toolchain 248/270 Test #248: CMake.Toolchain .................................. Passed 0.36 sec Start 249: CMake.GetFilenameComponentRealpath 249/270 Test #249: CMake.GetFilenameComponentRealpath ............... Passed 0.15 sec Start 250: CMake.Version 250/270 Test #250: CMake.Version .................................... Passed 0.12 sec Start 251: CMake.Message 251/270 Test #251: CMake.Message .................................... Passed 0.22 sec Start 252: CMake.File 252/270 Test #252: CMake.File ....................................... Passed 10.72 sec Start 253: CMake.ConfigureFile 253/270 Test #253: CMake.ConfigureFile .............................. Passed 1.05 sec Start 254: CMake.SeparateArguments 254/270 Test #254: CMake.SeparateArguments .......................... Passed 0.12 sec Start 255: CMake.ImplicitLinkInfo 255/270 Test #255: CMake.ImplicitLinkInfo ........................... Passed 15.62 sec Start 256: CMake.ModuleNotices 256/270 Test #256: CMake.ModuleNotices .............................. Passed 1.83 sec Start 257: CMake.GetProperty 257/270 Test #257: CMake.GetProperty ................................ Passed 1.62 sec Start 258: CMake.If 258/270 Test #258: CMake.If ......................................... Passed 0.41 sec Start 259: CMake.String 259/270 Test #259: CMake.String ..................................... Passed 11.48 sec Start 260: CMake.Math 260/270 Test #260: CMake.Math ....................................... Passed 0.58 sec Start 261: CMake.CMakeMinimumRequired 261/270 Test #261: CMake.CMakeMinimumRequired ....................... Passed 1.05 sec Start 262: CMake.CompilerIdVendor 262/270 Test #262: CMake.CompilerIdVendor ........................... Passed 0.35 sec Start 263: CMake.ProcessorCount 263/270 Test #263: CMake.ProcessorCount ............................. Passed 0.62 sec Start 264: CMake.PushCheckState 264/270 Test #264: CMake.PushCheckState ............................. Passed 0.13 sec Start 265: CMake.While 265/270 Test #265: CMake.While ...................................... Passed 0.72 sec Start 266: CMake.FileDownload 266/270 Test #266: CMake.FileDownload ...............................***Exception: SegFault 4.30 sec Start 267: CMake.FileUpload 267/270 Test #267: CMake.FileUpload ................................. Passed 0.30 sec Start 268: CMake.ELF 268/270 Test #268: CMake.ELF ........................................ Passed 0.20 sec Start 269: CMake.EndStuff 269/270 Test #269: CMake.EndStuff ................................... Passed 1.73 sec Start 270: CMake.GetPrerequisites 270/270 Test #270: CMake.GetPrerequisites ........................... Passed 1.15 sec 98% tests passed, 6 tests failed out of 270 Label Time Summary: Label1 = 0.35 sec Label2 = 0.35 sec Total Test time (real) = 2465.88 sec The following tests FAILED: 24 - FindPackageTest (Failed) 35 - VSGNUFortran (Failed) 184 - Fortran (Failed) 185 - FortranC.Flags (Failed) 230 - RunCMake.include_directories (Failed) 266 - CMake.FileDownload (SEGFAULT) Errors while running CTest gmake: *** [test] Error 8 $ $ ls *core* node_node002-host_sun4v-zone_z_001-time_1368993213-pid_13378-uid_16411-gid_1-fid_cmsysTestProcess.core node_node002-host_sun4v-zone_z_001-time_1368993213-pid_13381-uid_16411-gid_1-fid_cmsysTestProcess.core node_node002-host_sun4v-zone_z_001-time_1368994977-pid_10255-uid_16411-gid_1-fid_Crash.core node_node002-host_sun4v-zone_z_001-time_1368995656-pid_18683-uid_16411-gid_1-fid_cmake.core $ find . -type f -name cmsysTestProcess ./Source/kwsys/cmsysTestProcess $ dbx ./Source/kwsys/cmsysTestProcess node_node002-host_sun4v-zone_z_001-time_1368993213-pid_13378-uid_16411-gid_1-fid_cmsysTestProcess.core Reading cmsysTestProcess dbx: warning: core object name "cmsysTestProces" matches object name "cmsysTestProcess" within the limit of 14. assuming they match core file header read successfully Reading ld.so.1 Reading libc.so.1 Reading libc_psr.so.1 program terminated by signal SEGV (no mapping at the fault address) Current function is test4 106 *invalidAddress = 0; (dbx) where =&gt;[1] test4(argc = 3, argv = 0xffffffff7ffff2f8), line 106 in "testProcess.c" [2] main(argc = 3, argv = 0xffffffff7ffff2f8), line 429 in "testProcess.c" (dbx) quit $ dbx ./Source/kwsys/cmsysTestProcess node_node002-host_sun4v-zone_z_001-time_1368993213-pid_13381-uid_16411-gid_1-fid_cmsysTestProcess.core Reading cmsysTestProcess dbx: warning: core object name "cmsysTestProces" matches object name "cmsysTestProcess" within the limit of 14. assuming they match core file header read successfully Reading ld.so.1 Reading libc.so.1 Reading libc_psr.so.1 program terminated by signal SEGV (no mapping at the fault address) Current function is test4 106 *invalidAddress = 0; (dbx) quit $ find . -type f -name Crash ./Tests/CTestTestCrash/Crash $ dbx ./Tests/CTestTestCrash/Crash node_node002-host_sun4v-zone_z_001-time_1368994977-pid_10255-uid_16411-gid_1-fid_Crash.core Reading Crash core file header read successfully Reading ld.so.1 Reading libCstd.so.1 Reading libCrun.so.1 Reading libm.so.2 Reading libc.so.1 Reading libc_psr.so.1 program terminated by signal SEGV (no mapping at the fault address) Current function is main 5 *ptr = 1; (dbx) where =&gt;[1] main(), line 5 in "crash.cxx" (dbx) quit $ find . -type f -name cmake ./Bootstrap.cmk/cmake ./Docs/bash-completion/cmake ./bin/cmake $ $ dbx ./bin/cmake node_node002-host_sun4v-zone_z_001-time_1368995656-pid_18683-uid_16411-gid_1-fid_cmake.core Reading cmake core file header read successfully Reading ld.so.1 Reading libdl.so.1 Reading libexpat.so.1.6.0 Reading libz.so.1.2.7 Reading libmd.so.1 Reading libcurl.so.4.3.0 Reading libCstd.so.1 Reading libCrun.so.1 Reading libm.so.2 Reading libc.so.1 Reading libidn.so.11.6.9 Reading libssh2.so.1.0.1 Reading libssl.so.1.0.0 Reading libcrypto.so.1.0.0 Reading libldap.so.5 Reading librt.so.1 Reading libsocket.so.1 Reading libnsl.so.1 Reading libintl.so.8.1.1 Reading libiconv.so.2.5.1 Reading libaio.so.1 Reading libc_psr.so.1 Reading libnspr4.so Reading libpthread.so.1 Reading libsasl.so.1 Reading libmd_psr.so.1 Reading libplc4.so Reading libnss3.so Reading libnssutil3.so Reading libplds4.so Reading libssl3.so Reading libthread.so.1 Reading libmp.so.2 Reading libscf.so.1 Reading libdoor.so.1 Reading libuutil.so.1 Reading libgen.so.1 t&lt; at &gt;1 (l&lt; at &gt;1) program terminated by signal BUS (invalid address alignment) Current function is cmSHA512_Internal_Transform 1340 T1 = h + Sigma1_512(e) + Ch(e, f, g) + K512[j] + (W512[j] = *data++); (dbx) where current thread: t&lt; at &gt;1 =&gt;[1] cmSHA512_Internal_Transform(context = 0x100bedee0, data = 0xffffffff7fffb70c), line 1340 in "cm_sha2.c" [2] cmSHA512_Update(context = 0x100bedee0, data = 0xffffffff7fffb70c "\x89PNG^M\n^Z\n", len = 358U), line 1428 in "cm_sha2.c" [3] cmSHA384_Update(context = 0x100bedee0, data = 0xffffffff7fffb70c "\x89PNG^M\n^Z\n", len = 358U), line 1552 in "cm_sha2.c" [4] cmCryptoHashSHA384::Append(this = 0x100b2fe20, buf = 0xffffffff7fffb70c "\x89PNG^M\n^Z\n", sz = 358), line 129 in "cmCryptoHash.cxx" [5] cmCryptoHash::HashFile(this = 0x100b2fe20, file = 0x100bede70 "/usr/local/build/cmake-2.8.11_SunOS5.10_sparcv9.001/Tests/CMakeTests/downloads/file3.png"), line 71 in "cmCryptoHash.cxx" [6] cmFileCommand::HandleDownloadCommand(this = 0x100bdde50, args = CLASS), line 2807 in "cmFileCommand.cxx" [7] cmFileCommand::InitialPass(this = 0x100bdde50, args = CLASS, _ARG3 = CLASS), line 83 in "cmFileCommand.cxx" [8] cmCommand::InvokeInitialPass(this = 0x100bdde50, args = CLASS, status = CLASS), line 68 in "cmCommand.h" [9] cmMakefile::ExecuteCommand(this = 0x100bca9f0, lff = STRUCT, status = CLASS), line 414 in "cmMakefile.cxx" [10] cmMakefile::ReadListFile(this = 0x100bca9f0, filename_in = (nil), external_in = 0x100b59090 "/usr/local/build/cmake-2.8.11_SunOS5.10_sparcv9.001/Tests/CMakeTests/FileDownloadTest.cmake", fullPath = (nil), noPolicyScope = true), line 695 in "cmMakefile.cxx" [11] cmake::ReadListFile(this = 0xffffffff7fffeb78, args = CLASS, path = 0x100b59090 "/usr/local/build/cmake-2.8.11_SunOS5.10_sparcv9.001/Tests/CMakeTests/FileDownloadTest.cmake"), line 539 in "cmake.cxx" [12] cmake::SetCacheArgs(this = 0xffffffff7fffeb78, args = CLASS), line 488 in "cmake.cxx" [13] cmake::Run(this = 0xffffffff7fffeb78, args = CLASS, noconfigure = false), line 2503 in "cmake.cxx" [14] do_cmake(ac = 3, av = 0xffffffff7ffff208), line 527 in "cmakemain.cxx" [15] main(ac = 3, av = 0xffffffff7ffff208), line 338 in "cmakemain.cxx" (dbx) quit $ That is a pretty ugly result. -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake</pre> Paul Lanken 2013-05-20T00:34:28 http://comments.gmane.org/gmane.comp.programming.tools.cmake.user/46702 <pre>Hi Bill: I am addressing this mostly to you because I believe you have a strong historical interest in the Cygwin platform. Just to remind you, my use case is I build and test a fair number of different cross-platform software packages (FreeEOS, te_gen, ephcom, and PLplot and all their dependencies) with CMake-based build systems on both Linux and the Wine version of Windows. For the latter case, I have had perfect success (no issues at all compared with the Linux builds and tests) with CMake-2.8.10.2, nearly the latest MinGW (4.7.0, but I haven't tried the latest 4.7.2 yet), and MSYS on Wine-1.5.19. Encouraged by that Wine build and test success I would like to install Cygwin on Wine-1.5.19 and try to build and test all the packages I am interested in on the Cygwin/Wine platform. GUI installers that I have tried so far all seem to work well on Wine so I don't anticipate any difficulties with the Cygwin GUI installer. But I am a complete Cygwin newbie so I have some questions about how to access and use the latest CMake on that platform. 1. The CMake version at http://cygwin.com/packages/cmake/ appears to be somewhat outdated. The latest available package there is cmake-2.8.9. My impression is in the past the Cygwin package for cmake was your work. Is that still the case, do you plan to update that package to CMake-2.8.10.2 (or 2.8.11) anytime soon? 2. If you are no longer involved with that package, can I just download the Windows binary version of CMake-2.8.10.2 or later for use on Cygwin? 3, Even if a binary version of CMake-2.8.10.2 or later is available for Cygwin, I may build it anyway on that platform just for the practice. Are there any special build instructions for that platform? 4. Which of the command-line generators should I be using on Cygwin? I assume it is one of the "* Makefiles" ones, but which one? Alan __________________________ Alan W. Irwin Astronomical research affiliation with Department of Physics and Astronomy, University of Victoria (astrowww.phys.uvic.ca). Programming affiliations with the FreeEOS equation-of-state implementation for stellar interiors (freeeos.sf.net); the Time Ephemerides project (timeephem.sf.net); PLplot scientific plotting software package (plplot.sf.net); the libLASi project (unifont.org/lasi); the Loads of Linux Links project (loll.sf.net); and the Linux Brochure Project (lbproject.sf.net). __________________________ Linux-powered Science __________________________ -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake </pre> Alan W. Irwin 2013-05-19T20:17:39 http://comments.gmane.org/gmane.comp.programming.tools.cmake.user/46700 <pre>Hello all...I've used cmake a lot in the past, and it's done very well for me...but I'm afraid I've run into a brick wall. Admittedly, I'm trying to do something complex, though the part that's failing seems really simple. I know that cmake doesn't handle multiple toolchains very well.  The problem is that I'm trying to build a MinGW version of the phonon package from Fedora Core 18, i.e. cross-compile.  Most of the find_* commands need to look at the cross-compile cmake environment, and they are, but there's at least one exception -- it needs to run the host's automoc tool (to preprocess Qt/KDE files). If you want to follow along in the phonon source code, I'm in phonon-4.6.0/cmake/FindAutomoc4.cmake; I've modified the line find_package(Automoc4 QUIET NO_MODULE) to say find_package(Automoc4 QUIET NO_MODULE PATHS "${HOST_PREFIX_PATH}") and I've passed the value of HOST_PREFIX_PATH on the cmake command line as "/usr/lib/automoc4". My machine has a /usr/lib/automoc4/Automoc4Config.cmake file. But find_package() consistently fails!  Is there any explanation why? I added the line message (STATUS "Got here /usr/lib/automoc4/Automoc4Config.cmake") to /usr/lib/automoc4/Automoc4Config.cmake, so that I could make sure whether it is/isn't getting called.  It's not. Out of desperation, I even ran "restorecon -Rv /usr", since SELinux contexts tend to lead to mysterious errors like this, but it found nothing relevant. Any ideas? Steven Boswell -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake</pre> Steven Boswell II 2013-05-19T00:28:07 http://comments.gmane.org/gmane.comp.programming.tools.cmake.user/46697 <pre>Hi, I'm pretty new to CMake/CTest, and I was wondering what the best way to switch between compilers is when testing and building the same project with multiple compilers. It seems deleting the CMake cache from cmake-gui doesn't always work to switch compilers (which I am specifying with `export CC=icc; export CXX=icpc; export FC=ifort` in my environment). It would be great if I could have multiple build directories, one for each compiler. Is there a good way to do this, possibly in CMakeLists.txt? Thanks, Izaak Beekman =================================== (301)244-9367 Princeton University Doctoral Candidate Mechanical and Aerospace Engineering ibeekman-uX/v2g6dJhCyum0STUha2w&lt; at &gt;public.gmane.org UMD-CP Visiting Graduate Student Aerospace Engineering ibeekman-+0HnD9Kv66LFajBVf7NWsQ&lt; at &gt;public.gmane.org ibeekman-e45ueOrobK4&lt; at &gt;public.gmane.org -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake</pre> Zaak Beekman 2013-05-17T15:51:50 http://comments.gmane.org/gmane.comp.programming.tools.cmake.user/46695 <pre>On behalf of myself, Ken, Bill, Brad, David, Alex, Eike, Steve, Eric, Zach, Ben and the rest of the CMake team from all around the world, we are pleased to announce that CMake 2.8.11 is now available for download at: http://www.cmake.org/files/v2.8/?C=M;O=D It is also available from the usual download links found on the CMake web site: http://www.cmake.org/cmake/resources/software.html Some of the notable changes in this release are: - Introduced Target Usage Requirements - Targets can specify usage requirements for their consumers such as include directories and preprocessor definitions; previously only link dependencies were supported - target_link_libraries(myexe yourlib) can now build myexe sources with requirements specified by yourlib - Added target_include_directories and target_compile_definitions commands with PUBLIC/PRIVATE/INTERFACE options - See design and development discussion at http://community.kde.org/Frameworks/Epics/CMake_target_usage_requirements - Introduced a Generator Toolset selection for VS &gt;= 10 and Xcode &gt;= 3 - Tell the IDEs which compiler toolchain to use - ex. Use VS 9 tools under VS 10: -G “Visual Studio 10” -T “v90” - Introduced ExternalData Module - Keep source trees lightweight by storing data separately - Reference data unambiguously from source tree by content hash - Fetch on-demand during build from local or remote resources - CMake: Sublime Text Generator added that supports both Make and Ninja - CMake: Added support for Texas Instruments C6 and up compilers - CMake: Improve OpenBSD support - CMake: Support for Windows CE with VS 8 and 9 generators - CPack: Added Support for 64bit NSIS - CPack: Added WiX Package Generator - ExternalProject: Will run git fetch less often - FindBoost: Major overhaul of searching and result caching - FindCUDA: Now has support for separable compilation - FindQt4: Overall improvements to finding Qt and importing targets - FindSquish: Added support for squish 4 - GetPrerequisites: Port to MinGW with objdump The bug tracker change log page for this version is at: http://public.kitware.com/Bug/changelog_page.php?version_id=103 Please upgrade to this latest and greatest version of CMake for building your projects. For a complete list of changes in this release, please read the related blog posts http://www.kitware.com/blog/home/post/492 -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake </pre> Robert Maynard 2013-05-17T15:09:11 http://comments.gmane.org/gmane.comp.programming.tools.cmake.user/46691 <pre>I'm new to cmake, a few weeks ago I decided to convert a complex and decrepit old build system to cmake. It has gone very well, I'm quite impressed. So, now I want to add testing support, but I haven't been able to figure out a few things. 1. What to do with testing input files? I wrote a script to handle the common details of running. So I just need to pass it paths to the executable and input files. What's the best way to do this? Right now I just have them point to the source directory, is that the best way to handle this? add_test (Bungee ${PROJECT_SOURCE_DIR}/Examples/psuade_2test.sh ${PROJECT_BINARY_DIR}/psuade ${PROJECT_SOURCE_DIR}/Examples/Bungee/psuade.in ${PROJECT_SOURCE_DIR}/Examples/Bungee/psScript.in ${PROJECT_SOURCE_DIR}/Examples/Bungee/psScript.out) Maybe it would be better to copy the input files to the build directory? 2. Also, with autoconf you can run installcheck. However, I'm sure what I did here wouldn't work with an installcheck. However, I can't find any evidence that cmake supports installcheck explicitly. Does it? And if so, what's the right way to do it? 3. Finally, my testing script uses "diff" to compare the output from the test to the canonical output. This works fine on various unix flavors, but I will also need to build this on Windows (probably with mingw). Windows doesn't have diff, but does have FC. I could probably write a windows script to do testing. How are these problems usually handled? CMAKE_SYSTEM_NAME? Thanks, Jim -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake</pre> Leek, Jim 2013-05-16T00:35:31 http://comments.gmane.org/gmane.comp.programming.tools.cmake.user/46688 <pre>I have a fortran code that I'm compiling twice to generate two libraries. There is a USE statement inside a preprocessor conditional. It looks like cmake is not picking up the dependency because of it. The code in question is SUBROUTINE calc_fbal(bsubu, bsubv) ... USE realspace, ONLY: wint, phip #ifdef _ANIMEC 1 ,pperp, ppar, onembc, sigma_an, 2 pp1, pp2, pp3 USE vforces, gsqrt =&gt; azmn_o #endif When I try to compile this, I get an error [ 39%] Building Fortran object VMEC2000/CMakeFiles/animec.dir/Sources/General/fbal.f.o /trunk/VMEC2000/Sources/General/fbal.f:22.72: USE vforces, gsqrt =&gt; azmn_o 1 Fatal Error: Can't open module file 'vforces.mod' for reading at (1): No such file or directory I'm defining _ANIMEC using the line set_target_properties (animec PROPERTIES COMPILE_FLAGS "${BUILD_FLAGS} -D_ANIMEC") because I only what it defined for this specific target only. Is there a better way define _ANIMEC so that it correctly finds the dependency? Mark -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake</pre> Mark Cianciosa 2013-05-15T20:10:13 http://comments.gmane.org/gmane.comp.programming.tools.cmake.user/46675 <pre>hello, I'm working on a C++ package for ROS (robot operating system) that uses a C library libccv.a. ROS uses CMake which is why I am asking here. Asking at ROS answers did not help and I am totally stuck. here is the relevant part of my CMakeLists.txt: set(SOURCES src/${PROJECT_NAME}.cpp src/RosDispatcher.cpp src/Text2D.cpp src/TDetector.cpp src/TRecognizer.cpp) set(CMAKE_MODULE_PATH ${CMAKE_MODULE_PATH} "${CMAKE_SOURCE_DIR}/cmake/Modules/") find_package(CCV REQUIRED) include_directories(${CCV_INCLUDE_DIR}) set(LIBS ${LIBS} ${CCV_LIBRARY}) find_package(JPEG REQUIRED) include_directories(${JPEG_INCLUDE_DIR}) set(LIBS ${LIBS} ${JPEG_LIBRARY}) find_package(PNG REQUIRED) include_directories(${PNG_INCLUDE_DIR}) set(LIBS ${LIBS} ${PNG_LIBRARY}) message(STATUS "linked libs: ${LIBS}") rosbuild_add_executable(${PROJECT_NAME} ${SOURCES}) target_link_libraries(${PROJECT_NAME} ${LIBS}) I am getting this error: undefined reference to `ccv_read_impl(...)' and more undefined references to the stuff from the library libccv.a comes with a header file ccv.h and it depends on libjpeg and libpng. I wrote my own FindCCV.cmake to find the library and put it into ${CMAKE_SOURCE_DIR}/cmake/Modules/, together with finders for jpeg and png. As far as I know, all three are found successfully (the REQUIRED keyword doesn't stop compilation and there are correct address entries in CMakeCache). The libraries are in correct order ccv, jpeg, png (ccv depends on them). here &lt;http://pastebin.com/iye7iuqX&gt; [pastebin] is output of the compilation here &lt;http://pastebin.com/f6WK1A1x&gt; is my FindCCV.cmake Please, what am I doing wrong? Any help is very greatly appreciated, thanks! -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake</pre> Vojtěch Novák 2013-05-14T23:05:13 http://comments.gmane.org/gmane.comp.programming.tools.cmake.user/46674 <pre>I'm pleased to announce the first release candidate of CMake Tools for Visual Studio, an extension adding support for syntax highlighting and IntelliSense in CMake code using Microsoft Visual Studio. The extension is open source (distributed under Ms-RL), freely available, and compatible with VS 2010 and VS 2012. You can download it from the project from its web site on CodePlex at http://cmaketools.codeplex.com. I hope that the extension will prove useful to the CMake community. Please don't hesitate to contact me if you've found any bugs that you'd like to report of it you're interested in contributing to the project. Enjoy! David Golub -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake</pre> David Golub 2013-05-14T23:04:12 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.programming.tools.cmake.user