Re: [cmake-developers] CMake 3.5.2 conflates OSX SDK version with target deployment
On Sat, 21 May 2016 22:50:41 -0700, James Burgess said: >If your set CMAKE_OSX_DEPLOYMENT_TARGET in order to get find modules to >work on Xcode6 or above you get this message: > >$ 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" > > Instead using SDK: > > "/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/ >Developer/SDKs/MacOSX10.10.sdk". >Call Stack (most recent call first): > /Applications/CMake.app/Contents/share/cmake-3.5/Modules/ >CMakeSystemSpecificInitialize.cmake:18 (include) > CMakeLists.txt:25 (project) It seems to me that if you're going to specify a deployment target explicitly that you should specify an SDK explicitly too. That aside, if you don't, CMake should probably default to the newest SDK (which is what Xcode does). I don't see a reason to default to an SDK "matching" the deployment target, in fact it's problematic these days since they no longer provider older SDKs. Of course, finding the "newest" SDK will be a bit fragile, since they get moved/renamed all the time, but I guess that's something CMake always has to deal with anyway. Cheers, -- Sean McBride, B. Eng s...@rogue-research.com Rogue Researchwww.rogue-research.com Mac Software Developer Montréal, Québec, Canada -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
Re: [cmake-developers] Drop support for older Xcode versions?
On Wed, 10 Feb 2016 15:25:31 -0800, Eric Wing said: >On 2/9/16, Davy Durham <ddur...@davyandbeth.com> wrote: >> I'll say that in my line of work, we still have to support OS X 10.6 >> (just dropped 10.5 support) .. And we're doing this at Apple's own >> request/demand! It's not fun. I've had to hack tools around to get >> somewhat newer tool chains to continue to work, but it's been /great/ >> that cmake hasn't been an obstacle in this endeavour. > >Supporting 10.6...this is what I'm referring to. In Apple's world, >this means you are on 10.11 using Xcode 7.3 and setting the Deployment >target to 10.6. > >I know for hard cases, it is never that simple, but do you really need >to be on 10.6 to develop for 10.6? As you say, you can develop on newest and set old deployment target. But when you run into a bug that only reproduces on 10.6, what then? The nicest is to build & debug on 10.6 so you can debug it. This means being able to use the (newest) Xcode that supports that OS. Again, I don't care about 10.6 per se, but substitute 10.x for whatever the oldest you care about is, and the above still applies. Cheers, -- ________ Sean McBride, B. Eng s...@rogue-research.com Rogue Researchwww.rogue-research.com Mac Software Developer Montréal, Québec, Canada -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
Re: [cmake-developers] Drop support for older Xcode versions?
On Mon, 8 Feb 2016 10:31:17 -0500, Brad King said: >Sean, it looks like you are still running nightly tests on OS X >10.6 with Xcode 4.2: > > https://open.cdash.org/viewNotes.php?buildid=4226138 > >and OS X 10.5 with Xcode 3.1: > > https://open.cdash.org/viewNotes.php?buildid=4226202 Yeah, mostly because those machines haven't died either. :) If/when it's decided to drop those Xcodes, I'll switch those builds to makefile generator. >Given Apple's encouragement of developers to always update... They certainly do, as Eric described. However, just like everyone else, Apple often ships regressions in Xcode and it's sometimes vital to be able to use older versions. Similarly, if you want to deploy an app to an older OS, it's very useful to be able to build-run-debug on that OS, and since the newest Xcodes only run on the newest OSes, one needs an older Xcode to test/debug on older OSes. Cheers, -- ________ Sean McBride, B. Eng s...@rogue-research.com Rogue Researchwww.rogue-research.com Mac Software Developer Montréal, Québec, Canada -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
Re: [cmake-developers] Drop support for older Xcode versions?
On Sat, 6 Feb 2016 11:49:07 +0100, Gregor Jasny via cmake-developers said: >I'd like to get your feedback on deprecating or dropping support for >older Xcode versions. During changes on the Xcode generator it gets >harder and harder to test against old and very old Xcode versions like 3 >and 4. > >Are there still users around for these versions of Xcode? Wikipedia has a nice table of Xcode & OS X: <https://en.wikipedia.org/wiki/Xcode#Version_comparison_table> The problem with supporting only current - 1 as Eric suggests is that also excludes older versions of OS X, see the 'min OS X to run' column. What's the oldest version of Xcode that CMake currently supports? Personally, I think supporting Xcode 5.0+ would be reasonable at this point. It was released about 2.5 years ago and can run on OS X 10.8. Cheers, -- ________ Sean McBride, B. Eng s...@rogue-research.com Rogue Researchwww.rogue-research.com Mac Software Developer Montréal, Québec, Canada -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
Re: [cmake-developers] malware?
On Fri, 24 Jul 2015 11:40:09 -0400, Chuck Atkins said: I just checked the cmake.org download and was able to verify the following: cmake-3.2.3-Darwin-x86_64.dmg - 27949121 Bytes - MD5 97c26048e9b3e242951bb5b1ff88da9e cmake-3.3.0-Darwin-x86_64.dmg - 22628082 Bytes - MD5 232ae38586f3e6b665f9b7ac281167a0 I checked from both inside and outside Kitware's network as to verify internal and external were the same. Are these the same for the files you downloaded from cmake.org? Can you try to download from a different machine to verify it's not a local problem? If you're trying to detect imposter binaries, don't use md5. In fact, don't use md5 ever for anything: https://en.wikipedia.org/wiki/MD5#Security I get the following for my cmake download: $ shasum -a 256 /Users/sean/Downloads/cmake-3.3.0-Darwin-x86_64.dmg 0282d6f139f5292c2bb9b3d600df6b7db242d8f53c4ab8d1e6ddff76402e0eab /Users/sean/Downloads/cmake-3.3.0-Darwin-x86_64.dmg Cheers, -- Sean McBride, B. Eng s...@rogue-research.com Rogue Researchwww.rogue-research.com Mac Software Developer Montréal, Québec, Canada -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
[cmake-developers] Fragile OS X version checks failing against 10.10
Hi all, Dunno why I didn't notice until now, but CMake seems to be doing some fragile checks for OS X version numbers. Specifically in cmCPackPackageMakerGenerator, at least 2 things: 1) a 'double' variable: this-PackageCompatibilityVersion = 10.4; 10.10 will compare like 10.1 there. 2) a regex: if(OSX_VERSION MATCHES ^10\\.[0123] OR OSX_VERSION MATCHES ProductVersion:\t10\\.[0123]) message(STATUS Forcing CTEST_TEST_CPACK=OFF on OSX 10.4) Cheers, -- Sean McBride, B. Eng s...@rogue-research.com Rogue Researchwww.rogue-research.com Mac Software Developer Montréal, Québec, Canada -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
Re: [cmake-developers] [TEST REQUEST] CPack IFW generator on OSX
On Thu, 23 Oct 2014 16:45:36 +0400, Konstantin Podsvirov said: Can anybody test IFW generator on Mac? Probably... What is it? :) How would I test it? If you can give me clear instructions, I can update one or more of my dashboards to test it. Cheers, -- Sean McBride, B. Eng s...@rogue-research.com Rogue Researchwww.rogue-research.com Mac Software Developer Montréal, Québec, Canada -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
Re: [cmake-developers] fix-OSX-bundle-rpaths-and-Qt5 topic
On Wed, 22 Oct 2014 19:29:00 +0200, Adam Strzelecki said: The nightly binary works again. The first working version after this gap is now: Great! Now, do you plan code signing the CMake.app? Do you guys have Mac Developer ID? The bug for that is here BTW, created over 2 years ago now... http://public.kitware.com/Bug/view.php?id=13532 Cheers, -- Sean McBride, B. Eng s...@rogue-research.com Rogue Researchwww.rogue-research.com Mac Software Developer Montréal, Québec, Canada -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
Re: [cmake-developers] scan-build of CMake
On Wed, 30 Jul 2014 18:10:36 -0400, Bill Hoffman said: I am working on scan-build integration with ctest/CDash and did a build of CMake. The results show up in the warning section of the build: http://open.cdash.org/viewBuildError.php?type=1buildid=3429991 Sweet! Looking forward to turning that on some of our dashboards. For those that don't know, when Bill refers to 'scan-build' he's talking about the clang static analyzer: http://clang-analyzer.llvm.org Cheers, -- Sean McBride, B. Eng s...@rogue-research.com Rogue Researchwww.rogue-research.com Mac Software Developer Montréal, Québec, Canada -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
Re: [cmake-developers] Objective-C support
On Thu, 13 Feb 2014 17:35:42 -0700, Steve Wilson said: I just pushed a small topic branch to stage the introduces support for Objective-C as a ‘supported’ language with a separate identity from C/ CXX. The topic name is ‘objective-c-support.’ Does that solve this by any chance: http://public.kitware.com/Bug/view.php?id=4756 Cheers, -- Sean McBride, B. Eng s...@rogue-research.com Rogue Researchwww.rogue-research.com Mac Software Developer Montréal, Québec, Canada -- 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://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] Objective-C support
On Fri, 14 Feb 2014 15:14:23 -0700, Steve Wilson said: On Mavericks (OS X 10.9) there are two STL implementations: libstdc++ and libc++. That was also the case in 10.7 and 10.8. In 10.9 the default changed from libstdc++ to libc++ though. I’m adding support for Objective-C++ and on Mavericks it matters which C++ library is used for linking. Same in 10.7 and 10.8, and any OS really, since C++ ABIs are not super stable. Is there a standard mechanism already in place for handling the difference in CMake. I checked for the -stdlib command line flag in the sources, but didn’t find it anywhere.Or put it another way, do we require users to decide themselves with STL implementation to use? To me, it's something the user (of CMake) chooses, very much like choosing to build as C89 or C99 or C++03 or C++11. Cheers, -- Sean McBride, B. Eng s...@rogue-research.com Rogue Researchwww.rogue-research.com Mac Software Developer Montréal, Québec, Canada -- 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://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] Objective-C support
On Fri, 14 Feb 2014 17:47:00 -0500, Ben Boeckel said: Same in 10.7 and 10.8, and any OS really, since C++ ABIs are not super stable. Hmm? The only one I know of recently is 4.7.0 and 4.7.1 breaking std::string ABI with C++11 support enabled (4.7.2 fixed it to be compatible with 4.7.0 and I'd, personally, blacklist those two versions if you use C++11). What I mean is that with C++, and STL especially, it's hard to build a library with a given compiler/standard library combination and link that library into an executable built with a different compiler/standard library combination. (Harder than with say C.) That's the case on any platform. I was only trying to point out that 10.9 Mavericks is not special in this regard. Cheers, -- Sean McBride, B. Eng s...@rogue-research.com Rogue Researchwww.rogue-research.com Mac Software Developer Montréal, Québec, Canada -- 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://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] Change default standard library implementation before used by compiler ?
On Tue, 14 Jan 2014 16:14:44 -0500, Jean-Christophe Fillion-Robin said: For both Slicer and SimpleITK, there is currently no support for the clang c++ standard library new implementation [1] that is now used by default on Maverick. It means that we currently expect our users to build the project by passing the flag: -DCMAKE_CXX_FLAGS_INIT:STRING=-stdlib=libstdc++ That seems like a backwards approach. Do Slicer and SimpleITK not build against libc++? If not, what's the reason you want to force libstdc++? Getting VTK and ITK to build against libc++ was not too much work, I imagine it would not be hard to get Slicer and SimpleITK compiling if they are not already. Cheers, -- Sean McBride, B. Eng s...@rogue-research.com Rogue Researchwww.rogue-research.com Mac Software Developer Montréal, Québec, Canada -- 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://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] CMake*.app/Contents/Info.plist version information
On Thu, 26 Sep 2013 13:11:21 -0700, quest4insi...@earthlink.net said: For the Mac OS X build of CMake, can the version number be added to CMake*.app/Contents/Info.plist ? The Info.plist version entries are currently empty ... keyCFBundleShortVersionString/key string/string keyCFBundleVersion/key string/string FYI I have filed a bug about that a couple of years ago: http://public.kitware.com/Bug/view.php?id=11694 Cheers, -- Sean McBride, B. Eng s...@rogue-research.com Rogue Researchwww.rogue-research.com Mac Software Developer Montréal, Québec, Canada -- 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://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
[cmake-developers] Patches for some clang warnings
Hi all, After Kent's message on the other list, I realized I didn't have my CMake + clang trunk dashboard configured the way I thought I did, namely some warnings I thought were enabled were not. Attached are some patches to fix some warnings. There are a couple of others that will appear on the Rogue7 dashboard that are easy to fix by someone that knows the code better. Specifically: CMake/Source/cmCreateTestSourceList.h:18:10: warning: empty paragraph passed to '\brief' command [-Wdocumentation] * \brief ~~^ CMake/Source/CPack/cmCPackGenerator.h:163:38: warning: empty paragraph passed to '@param' command [-Wdocumentation] * @param[in] initialPackageFileName ^ CMake/Source/CPack/cmCPackGenerator.h:164:36: warning: empty paragraph passed to '@param' command [-Wdocumentation] * @param[in] groupOrComponentName ~~^ CMake/Source/CPack/cmCPackGenerator.h:165:27: warning: empty paragraph passed to '@param' command [-Wdocumentation] * @param[in] isGroupName ~^ CMake/Source/CPack/cmCPackGenerator.h:175:10: warning: empty paragraph passed to '@pre' command [-Wdocumentation] * @pre @ref toplevel has been filled-in ^ Cheers, -- Sean McBride, B. Eng s...@rogue-research.com Rogue Researchwww.rogue-research.com Mac Software Developer Montréal, Québec, Canada 0001-Fixed-typo-in-header-include-guard.patch Description: Binary data 0002-Removed-useless-semi-colon.patch Description: Binary data 0003-Add-extra-space-in-comment-to-suppress-warning.patch Description: Binary data 0004-Fixed-warning-about-brief-usage.patch Description: Binary data 0005-Properly-escape-char-in-doxygen-comments.patch Description: Binary data 0006-Populated-empty-doxygen-param-comment.patch Description: Binary data 0007-Fixed-a-few-doxygen-comment-errors.patch Description: Binary data -- 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://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] Patches for some clang warnings
On Thu, 19 Sep 2013 13:53:54 -0400, Brad King said: On 09/19/2013 01:22 PM, Sean McBride wrote: Attached are some patches to fix some warnings. Applied, thanks. Here is the merge to 'next': http://cmake.org/gitweb?p=cmake.git;a=commit;h=3964de62 Thanks. Here are two more patches. Once they are all in, there will be about 10 new warnings on Rogue7 for someone to fix... Cheers, -- Sean McBride, B. Eng s...@rogue-research.com Rogue Researchwww.rogue-research.com Mac Software Developer Montréal, Québec, Canada 0008-Populated-empty-doxygen-param-comment.patch Description: Binary data 0009-Suppressed-warnings-by-setting-initial-value.patch Description: Binary data -- 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://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] CTestTestMemcheckDummy* failures during dynamic analysis
On Fri, 13 Sep 2013 14:51:21 -0400, Brad King said: There is still something fishy: http://open.cdash.org/testDetails.php?test=208331329build=3027132 http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=54a3e2a9 Not that it matters horribly, but those aren't from Guard Malloc (none of my dashboards use Guard Malloc). Guard Malloc is a specific thing, documented in: man libgmalloc https://developer.apple.com/library/mac/documentation/Darwin/Reference/ManPages/man3/libgmalloc.3.html The environment variables in question (ex: MallocScribble) are documented in: man malloc https://developer.apple.com/library/mac/documentation/Darwin/Reference/ManPages/man3/malloc.3.html under the section ENVIRONMENT. I'm not sure they have a collective name, I usually call them 'malloc debug environment variables'. Cheers, -- Sean McBride, B. Eng s...@rogue-research.com Rogue Researchwww.rogue-research.com Mac Software Developer Montréal, Québec, Canada -- 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://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] How submit CMake dashboard to a different CDash server?
On Fri, 16 Aug 2013 11:42:36 -0400, David Cole said: Try writing a dashboard_hook_build function, and setting the CTEST_DROP_* variables in there. The CTestConfig settings in the CMake source tree win unless you set those variables in the ctest script *after* the configure step. (I think... if I'm remembering correctly.) That mostly worked, thanks. My CMake build now gets submitted to my own dashboard. But cmake_common also automatically builds KWSys too, and that's still showing up on the public dashboard... any idea why? Cheers, -- Sean McBride, B. Eng s...@rogue-research.com Rogue Researchwww.rogue-research.com Mac Software Developer Montréal, Québec, Canada -- 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://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
[cmake-developers] How submit CMake dashboard to a different CDash server?
Hi all, I contribute a few CMake dashboards to the public cdash.org server. I've now set up a buildbot running a beta of OS X 10.9, but since 10.9 is in beta and under NDA, I want to submit the results to my own cdash server. How can I redirect my submission? The cmake_common.cmake file does not seem to have such a facility, the closest thing I've found is 'dashboard_no_submit' which is not quite what I want. :) I've tried setting the following: set(CTEST_DROP_METHOD http) set(CTEST_DROP_SITE cdash.rogue-research.com) set(CTEST_DROP_LOCATION /submit.php?project=FooBar) but it still showed up here: http://open.cdash.org/viewNotes.php?buildid=3000889 Any suggestions? Cheers, -- Sean McBride, B. Eng s...@rogue-research.com Rogue Researchwww.rogue-research.com Mac Software Developer Montréal, Québec, Canada -- 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://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] Suspicious Clang versions
On Thu, 15 Aug 2013 10:15:11 +0200, Rolf Eike Beer said: http://open.cdash.org/testDetails.php?test=203678570build=2998892 Looks like the headers are not those that belong to that version of Clang, but older ones. To which headers do you refer? On that version of the OS and Xcode, I believe the default C++ library is libstdc++, not libc++; and it's a gcc 4.2 era libstd++, with limited C++11 support. Cheers, -- Sean McBride, B. Eng s...@rogue-research.com Rogue Researchwww.rogue-research.com Mac Software Developer Montréal, Québec, Canada -- 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://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] Suspicious Clang versions
On Mon, 5 Aug 2013 08:08:20 +0200, Rolf Eike Beer said: So any version checking like I do in the CXXFeatures test (I have compiler version X, the supported features should be ...) is entirely mood for Clang. Great. Well, I don't know what we're really talking about here... but it sounds like you're trying to determine a compiler's features based on its version number. That's inherently pretty fragile, don't you agree? I do know that the clang folks discourage trying to determine clang's abilities from its version number. Instead, they have a mechanism called 'Feature Checking Macros' described here: http://clang.llvm.org/docs/LanguageExtensions.html#feature-checking-macros Cheers, -- Sean McBride, B. Eng s...@rogue-research.com Rogue Researchwww.rogue-research.com Mac Software Developer Montréal, Québec, Canada -- 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://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] Suspicious Clang versions
On Mon, 5 Aug 2013 09:44:00 -0400, Brad King said: and local testing we can use __APPLE_CC__ to detect Apple compiler builds. In my own build of open source clang from svn trunk, it seems that __APPLE_CC__ is defined: $ clang -dM -E - /dev/null #define __APPLE_CC__ 5621 So I don't think that will help. We could consider treating this as a separate compiler and using a new compiler id like ClangApple or AppleClang or something. That's probably a good idea... Embarcadero's compiler is also based on clang, how do you deal with it? I guess if the output of 'clang --version' includes the string 'Apple', it's AppleClang and not clang. But I think it may be a good idea to ask on cfe-dev or xcode-users mailing lists too... Cheers, -- Sean McBride, B. Eng s...@rogue-research.com Rogue Researchwww.rogue-research.com Mac Software Developer Montréal, Québec, Canada -- 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://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
[cmake-developers] clang now warns: 'register' storage class specifier is deprecated
Hi all, Recently in clang trunk, they added a new warning which we now see on Rogue7 since I updated my clang: http://open.cdash.org/viewBuildError.php?type=1buildid=2949429 CMake/Source/kwsys/RegularExpression.cxx:347:5: warning: 'register' storage class specifier is deprecated [-Wdeprecated-register] register const char* scan; ^ I can make a patch to remove the 'register' keyword, if you will accept it. Anyone have a philosophical objection? If so, I will suppress the warning. Cheers, -- Sean McBride, B. Eng s...@rogue-research.com Rogue Researchwww.rogue-research.com Mac Software Developer Montréal, Québec, Canada -- 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://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] Test fails with Xcode
On Wed, 26 Jun 2013 09:14:51 -0400, Brad King said: though it may be sporadic. I cannot reproduce it on my OS X 10.8 machine. In the above-linked output one can see that Xcode does not build the excludedFromAll target prior to the failure. In my local build it does. Something is tricking your Xcode into not building the target. So I opened the .xcodeproj with Xcode.app and I don't see any excludedFromAll item in the 'scheme' popup. Do you? I do see an 'ALL_BUILD' item and it builds successfully. I feel I'm missing something here :) Cheers, -- Sean McBride, B. Eng s...@rogue-research.com Rogue Researchwww.rogue-research.com Mac Software Developer Montréal, Québec, Canada -- 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://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] Test fails with Xcode
On Wed, 26 Jun 2013 09:14:51 -0400, Brad King said: RogueResearch7 Mac10.8-xcode-dbg-x86_64 http://open.cdash.org/testDetails.php?test=196407273build=2947399 clang: error: no such file or directory: '/Users/builder/external/CMake- xcode-dbg-x86_64/Tests/ExportImport/Import/A/excludedFromAll/Debug/ libexcludedFromAll.dylib' /Users/builder/external/CMake-xcode-dbg-x86_64/Tests/ExportImport/Import/A/excludedFromAll/ exits, but there is no 'Debug' folder within. though it may be sporadic. I cannot reproduce it on my OS X 10.8 machine. In the above-linked output one can see that Xcode does not build the excludedFromAll target prior to the failure. In my local build it does. Something is tricking your Xcode into not building the target. Please take a look to see if you can identify the problem in your local build tree. I'm short of time this week, but today I just updated from Xcode 4.6.2 to 4.6.3 and deleted the CMake binary folders for a cleaner build tomorrow. Let's see if that changes something... Cheers, -- Sean McBride, B. Eng s...@rogue-research.com Rogue Researchwww.rogue-research.com Mac Software Developer Montréal, Québec, Canada -- 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://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] Rogue7 dashboards and clang undefined behaviour
On Tue, 4 Jun 2013 13:45:34 -0400, Brad King said:
'CTestTestFdSetSize' is superficially happening in an OS header's macro:
static __inline int
__darwin_fd_isset(int _n, const struct fd_set *_p)
{
return (_p-fds_bits[_n/__DARWIN_NFDBITS] (1(_n %
__DARWIN_NFDBITS)));
}
where right right-hand side of the is apparently 31.
__DARWIN_NFDBITS is 32.
Alas, gdb refuses to give me a backtrace. But there are only 9
FD_ISSET() in
CMake, anyone familiar with this test/code?
The test covers CTest's ability to drive many child processes at once
so the file descriptor set is getting filled up. The FD_ISSET calls
in Source/kwsys/ProcessUNIX.c will be the ones triggering this. It
looks to me like the bug is in the OS header macro because the 1
should be 1u.
Agreed. I'll suppress both these tests and unsuppress them when the libarchive
and Apple people fix their respective bugs.
Cheers,
--
Sean McBride, B. Eng s...@rogue-research.com
Rogue Researchwww.rogue-research.com
Mac Software Developer Montréal, Québec, Canada
--
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://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
[cmake-developers] Rogue7 dashboards and clang undefined behaviour
Hi all,
I recently tweaked my Rogue7 dashboard's undefined behaviour checks and now
there are two test failures:
http://open.cdash.org/viewTest.php?onlyfailedbuildid=2926604
'ExternalProject' is a libarchive bug which I filed here:
http://code.google.com/p/libarchive/issues/detail?id=320
'CTestTestFdSetSize' is superficially happening in an OS header's macro:
static __inline int
__darwin_fd_isset(int _n, const struct fd_set *_p)
{
return (_p-fds_bits[_n/__DARWIN_NFDBITS] (1(_n %
__DARWIN_NFDBITS)));
}
where right right-hand side of the is apparently 31. __DARWIN_NFDBITS is 32.
Alas, gdb refuses to give me a backtrace. But there are only 9 FD_ISSET() in
CMake, anyone familiar with this test/code?
Cheers,
--
Sean McBride, B. Eng s...@rogue-research.com
Rogue Researchwww.rogue-research.com
Mac Software Developer Montréal, Québec, Canada
--
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://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
