Re: [CMake] [ANNOUNCE] CMake 3.14.0 available for download

[Sean McBride]

On Thu, 14 Mar 2019 11:58:16 -0400, Robert Maynard via CMake said:

>I am happy to announce that CMake 3.14.0 is now available for download at:
>  https://cmake.org/download/

Pi version on Pi Day.  Nicely done!  :)  Couldn't you have waited until 3:14 to 
release it?  :)

Sean


-- 

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:
https://cmake.org/mailman/listinfo/cmake

Re: [CMake] Odd Behavior in macOS Mojave

[Sean McBride]

On Wed, 14 Nov 2018 10:43:28 -0600, Steven Stallion said:

>We first noticed that some sources would fail to find certain system
>headers (stddef.h in this case) when using Xcode 10 (also seen on
>Xcode 10.1). It looks like Apple decided to relocate system include
>paths under /Library /Developer and did away with /usr/include. After
>some spelunking, it looks like this was tucked away in the release
>notes for Xcode:
>https://developer.apple.com/documentation/xcode_release_notes/
>xcode_10_release_notes

I see.  Well, I just checked my macOS 10.14.1 / Xcode 10.1 bot 
"RogueResearch12" and indeed it does not have a /usr/include folder.  It is 
however able to build CMake, VTK, and ITK nightly without any compiler errors.

Perhaps it's not so much a CMake bug as a bug in the project you're trying to 
build?

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:
https://cmake.org/mailman/listinfo/cmake

Re: [CMake] Odd Behavior in macOS Mojave

[Sean McBride]

On Tue, 13 Nov 2018 18:42:43 -0600, Steven Stallion said:

>It appears there have been some changes to how macOS handles the
>system include path starting with macOS Mojave. It looks like Apple
>has provided a workaround package you can install to re-instate the
>/usr/include hierarchy, however I was wondering if this is something
>that could be handled by AppleClang support?

Could you elaborate?  What odd behaviour are you seeing?  Any error message to 
share?  What 'workaround package' are you speaking of?  What version of Xcode?

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:
https://cmake.org/mailman/listinfo/cmake

Re: [CMake] Recommandation for macOS framework install rules

[Sean McBride]

On macOS, the most usual thing is for your code to be self-contained in your 
.app bundle.  Perhaps if you described more what kind of thing you are building 
and why you don't want to do the usual thing, people will have more advice...


On Fri, 19 Jan 2018 19:44:03 +0100, Lucas Soltic said:

>Hello,
>Should I conclude that there are no recommendations?
>
>Best regards,
>Lucas
>
>> Le 17 janv. 2018 à 23:49, Lucas Soltic  a écrit :
>> 
>> Hello,
>> 
>> By default library install() command uses CMAKE_INSTALL_PREFIX (/usr/
>local by default) as a base for relative install paths. But when you
>define install rules for macOS frameworks, it doesn't make much sense to
>install them there. I'd rather expect something like /Library/Frameworks.
>> 
>> On the other side, if you have more things to install like a "readme"
>or documentation that should go into /usr/local/share, it doesn't make
>sense to have them installed in /Library/Frameworks. So you can't just
>change CMAKE_INSTALL_PREFIX to be /Library/Frameworks.
>> 
>> What do you recommend to keep installation rules simple (ie. remain
>relative) and yet support installation of both frameworks and other things?


-- 

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:
https://cmake.org/mailman/listinfo/cmake

Re: [CMake] SecTrustEvaluateAsync != NULL

[Sean McBride]

On Thu, 18 Aug 2016 09:27:43 -0600, Laura Fowler said:

>
>/Users/LauraLaptop/InstalledSoftwares/sourcecode/cmake-3.6.1/Utilities/
>cmcurl/lib/vtls/darwinssl.c:1999:6:
>error: ‘SecTrustEvaluateAsync’ undeclared (first use in this function)
>
>   if(SecTrustEvaluateAsync != NULL) {
>
>  ^

If you look in SecTrust.h (where the SecTrustEvaluateAsync() API is declared), 
you'll see it's wrapped in

#ifdef __BLOCKS__

Likely your complier (gcc 5.3) does not support blocks.  Is there a reason you 
want to use gcc instead of the system complier (clang)?

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

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

[Sean McBride]

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?

[Sean McBride]

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] [cmake-developers] Drop support for older Xcode versions?

[Sean McBride]

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

Re: [cmake-developers] Drop support for older Xcode versions?

[Sean McBride]

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?

[Sean McBride]

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] [cmake-developers] Drop support for older Xcode versions?

[Sean McBride]

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

Re: [CMake] CMake 3.3 and 3.2 bootstrap fails on OS X Yosemite

[Sean McBride]

On Thu, 1 Oct 2015 16:51:55 -0700, Damian Rouson said:

>/usr/include/dispatch/object.h:143:15: error: expected unqualified-id
>before '^' token
> typedef void (^dispatch_block_t)(void);
>   ^
>/usr/include/dispatch/object.h:143:15: error: expected ')' before '^' token
>/usr/include/dispatch/object.h:362:3: error: 'dispatch_block_t' has not
>been declared
>   dispatch_block_t notification_block);

Your compiler doesn't support "blocks":

<https://en.wikipedia.org/wiki/Blocks_(C_language_extension)>

and the latest OS X SDKs require such support.  You could try building CMake 
against an older SDK, or just use clang, the default compiler on OS X.

I think Apple added blocks support to their fork of gcc (long ago), but I don't 
think it ever went into mainline gcc.

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

Re: [cmake-developers] malware?

[Sean McBride]

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

[Sean McBride]

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

[Sean McBride]

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

[Sean McBride]

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] How to install the command line tools on OSX with 3.0.2

[Sean McBride]

On Tue, 30 Sep 2014 10:28:43 +1300, Glenn Ramsey said:

With CMake 3.0.2 on OSX when I try to install the command line tools I get the
following message:

Failed create symlink installation may be incomplete: /usr/bin/toolname

With the 2.8.* versions I was able to workaround this by manually deleting the
symlinks in /usr/bin as recommended here:

http://public.kitware.com/Bug/print_bug_page.php?bug_id=10056

However that doesn't seem to work now, even if I run CMake.app as root.

Aside from manually creating the symlinks is there a workaround for this?

Now that CMake 3 finally excludes its version from its filename, I suggest you 
just add /Applications/CMake.app/Contents/bin to you $PATH.

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

Re: [cmake-developers] scan-build of CMake

[Sean McBride]

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] Using CPack with OSX 10.9

[Sean McBride]

On Tue, 29 Jul 2014 01:06:26 +, lachlan.hether...@csiro.au said:

I’m currently looking into the OSX Bundle generator, however, our
application ships with multiple executables and a number of dependent
libraries and frameworks, so I’m not quite sure whether this is the
right way to go. From what I’ve read, OSX application bundles are
supposed to have a single executable only – how would I go about
deploying an application that has multiple component applications? If we
use the bundle generator, our application is going to look like this (I
think), which seems strange:

OurApplication.app/
Contents/
Info.plist
MacOS/
executable1
Frameworks/
QtCore.framework
QtGui.framework
…
Resources/
bin/
executable1
executable2
…
lib/
non-framework dependencies

What's strange about it?  It's generally strongly preferred for an OS X 
application to be self-contained in a .app.  There are times when it's not 
possible, which is maybe your case?  What do you need to install where?

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

Re: [CMake] Regarding CMAKE and OSX Mavericks

[Sean McBride]

On Sat, 15 Mar 2014 00:57:16 +1100, Theodore St. Shenouda said:

CMAKE Version : 3.0.0 rc 1

My current system version.
OS:OSX 10.9.2
XCODE: 5.0.2


The C compiler identification is unknown
CMake Error at CMakeLists.txt:1 (project):
No CMAKE_C_COMPILER could be found.


Configuring incomplete, errors occurred!
See also /Users/theodorestshenouda/Desktop/glfw-3.0.4/Build/CMakeFiles/
CMakeOutput.log.
See also /Users/theodorestshenouda/Desktop/glfw-3.0.4/Build/CMakeFiles/
CMakeError.log.

gcc version: 

Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr
--with-gxx-include-dir=/usr/include/c++/4.2.1
Apple LLVM version 5.0 (clang-500.2.79) (based on LLVM 3.3svn)
Target: x86_64-apple-darwin13.1.0
Thread model: posix

Are you the one passing --prefix= and --with-gxx-include-dir?  If so, why?

What do the following output:

xcrun --find cc

xcode-select --print-path

BTW: OS 10.9  Xcode 5 do not provide *any* version of gcc, only clang.  
There's a gcc symlink for compatibility (as surely many tools/scripts assume 
its existence), but it's not really gcc at all.

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Xcode cannot open generated project

[Sean McBride]

On Thu, 27 Feb 2014 09:35:09 -0500, David Cole said:

Anybody else out there using Xcode 5.0.2 with CMake yet?

This dashboard of mine is using Xcode 5.0.2 under OS X 10.9:

http://open.cdash.org/buildSummary.php?buildid=3234853

It's basically green.

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://www.cmake.org/mailman/listinfo/cmake

Re: [cmake-developers] Objective-C support

[Sean McBride]

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

[Sean McBride]

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

[Sean McBride]

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 ?

[Sean McBride]

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] problems when upgrading to Xcode v5

[Sean McBride]

On Wed, 2 Oct 2013 18:42:16 +, Jeff Schenck said:

I recently upgraded to Xcode v5 on Mac OSX and started getting build
failures.  Below is a simplified project that produces the same problem,
followed by the error message generated by Xcode.  The problem occurs
with version v5 but not v4.6.x of Xcode.  I'm running CMake 2.8.10.2.

The first thing I would try is updating to 2.8.12rc4.  There have been fixes 
for new Xcode/OS X since 2.8.10.2.

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://www.cmake.org/mailman/listinfo/cmake

Re: [cmake-developers] CMake*.app/Contents/Info.plist version information

[Sean McBride]

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

[Sean McBride]

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

[Sean McBride]

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] Warning in CMake Git HEAD

[Sean McBride]

On Thu, 19 Sep 2013 17:08:21 +, Williams, Norman K said:

It is a typo.  This is a warning generated by a very recent development
head version of CLang I built.

My Rogue7 dashboard uses clang trunk, but I just noticed I never switched to a 
-Weverything + subtractive warning policy like I did for my VTK dashboards.  
Will fix that too.

It looks like it was added to CMake by Andy Cedilnik in revision 9314bb;
It looks like an upstream typo that just happened never to cause a
real-world problem.

I've created a patch, which I'll share on the cmake-dev list...

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Warning in CMake Git HEAD

[Sean McBride]

On Thu, 19 Sep 2013 15:12:54 +, Williams, Norman K said:

This looks like a simple typo.  I could fix it and submit a gerrit topic,
but I'm busy with other stuff for the moment.

Or is this a typo imported from CURL?

In file included from /scratch/kent/cmake/cmake/Utilities/cmcurl/http.c:99:
/scratch/kent/cmake/cmake/Utilities/cmcurl/parsedate.h:1:9: warning:
'__PARSEDATE_H' is used as a header guard here, followed
  by #define of a different macro [-Wheader-guard]
#ifndef __PARSEDATE_H
^
/scratch/kent/cmake/cmake/Utilities/cmcurl/parsedate.h:2:9: note:
'__PARSEDATEL_H' is defined here; did you mean
  '__PARSEDATE_H'?
#define __PARSEDATEL_H
^~
__PARSEDATE_H

Strange that my dashboard is not showing this, I'll check on that.  It does 
look like a typo.  That's 3rd party code, right?  Maybe it is fixed upstream?  
(Also, it's illegal to start an identifier with two underscores.)

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://www.cmake.org/mailman/listinfo/cmake

Re: [cmake-developers] CTestTestMemcheckDummy* failures during dynamic analysis

[Sean McBride]

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] Xcode generator : is it commonly used ?

[Sean McBride]

On Tue, 3 Sep 2013 07:26:44 +1000, Nicholas Yue said:

 I am currently on OS X 10.7 and am wondering if there are other 
developer on the same OS version and XCode 4.4.1 and have success with 
that tool chain and hope to learn the correct work flow since the 
changes at Apple with the move from  /Developer to /Application for XCode

Are you using the newest CMake?  It was updated quite some time ago to deal 
with the move from /Developer to /Applications.

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://www.cmake.org/mailman/listinfo/cmake

Re: [cmake-developers] How submit CMake dashboard to a different CDash server?

[Sean McBride]

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?

[Sean McBride]

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

[Sean McBride]

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] Objective-C support

[Sean McBride]

On Tue, 6 Aug 2013 12:05:35 +0200, Emmanuel Blot said:

What is the recommended way to specify compiler flags for Objective-C
source files?

Objective-C is not defined as a specific language in the default CMake
modules (vs. C and C++ for exemple), so CMake does not seem to handle
OBJC flags at all.

How to define OBJCFLAGS for a whole project, in such a way that those
flags are only applied to .m source files, not the other source files
(.c, .cxx, etc.)?

There might be some useful info for you here:
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

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://www.cmake.org/mailman/listinfo/cmake

Re: [cmake-developers] Suspicious Clang versions

[Sean McBride]

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

[Sean McBride]

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

[Sean McBride]

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

[Sean McBride]

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

[Sean McBride]

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

[Sean McBride]

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

[Sean McBride]

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

Re: [CMake] SEGV and signal BUS with cmake-2.8.11 on Solaris 10

[Sean McBride]

On Wed, 22 May 2013 16:43:21 -0400, Bill Hoffman said:

Anybody have suggestions for a fix?   This code was taken from here:
http://www.aarongifford.com/computers/sha.html

Is there a way to get a struct like that to align correctly?  Maybe make 
it a union with something that is the same number of bytes in 64 bit types?

memcpy().  (And compilers these days often optimize well-known functions like 
memcpy().)

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] SEGV and signal BUS with cmake-2.8.11 on Solaris 10

[Sean McBride]

On Wed, 22 May 2013 17:07:42 -0400, Bill Hoffman said:

How does that change the alignment of the buffer?

Maybe I've looked too quickly at the code... I'm suggesting this pattern change:

short* buffer_from_somewhere = ...
double foo = *((double*)buffer_from_somewhere);

to

short* buffer_from_somewhere = ...
double foo;
memcpy (foo, buffer_from_somewhere, sizeof(foo));

But maybe that's not the pattern at hand, I've admittedly looked hastily...

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Problem installing symbolic links on Mac OS X

[Sean McBride]

On Fri, 10 May 2013 12:34:06 -0400, Cory Quammen said:

I am running Mac OS X 10.7.5 . When I installed CMake 2.8.10.2 just
now, it failed to create symbolic links to the cmake executables in
the default location because I had symbolic links with the same names
already installed by a previous version of CMake.

This is a known bug:
http://public.kitware.com/Bug/view.php?id=10056

IMNSHO, the best thing to do is fix:
http://public.kitware.com/Bug/view.php?id=11693

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Date issue on www.cmake.org

[Sean McBride]

On Wed, 24 Apr 2013 15:53:28 +, David Cole said:

Sure, but this is in web page text only meant to be read by human
beings, not in some parse-able data that’s actually important for anything.

But human beings are confused by ambiguous dates, not just computers.  ISO 
dates are the way to go!

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] 2.8.11rc1 - OSX Lion and Xcode 4.4.1

[Sean McBride]

On Thu, 21 Mar 2013 22:27:41 +1100, Nicholas Yue said:

 I am trying out CMake 2.8.11rc1 on OS X Lion with XCode 4.4.1

My dashboard here:
http://open.cdash.org/buildSummary.php?buildid=2851443

Is running OS X 10.7.5, CMake 2.8.11rc1, and Xcode 4.4.1.  It's able to build 
(nightly) CMake itself, are you?

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Building Mac OSX .apps for Sys 10.6 and 10.8 with Cmake using 10.7.5 on the command line

[Sean McBride]

On Fri, 8 Feb 2013 09:22:12 -0800, Ed said:

Here is what I tried:
cmake -DCMAKE_OSX_64=ON -DCMAKE_OSX_DEPLOYMENT_TARGET=10.6 -
DCMAKE_C_COMPILER=/usr/bin/gcc -DCMAKE_CXX_COMPILER=/usr/bin/g++ ..

I've never heard of CMAKE_OSX_64 and google has only 7 results...

It built fine and runs on 10.7.5 but does not run on 10.6.  10.6 barfs
with usual message saying this app was not built for this architecture.

If the error message speaks of architecture, then you've probably built as 64 
bit-only or 32 bit-only.  Are you trying to run on a machine with 32 bit CPU?  
In any case, try setting CMAKE_OSX_ARCHITECTURES to i386;X86_64 to generate a 
'universal binary'.

Do you suppose it could not find what it needs to build the 10.6 64 bit
binaries?  Would it give some kind of error message if it could not find
the 10.6 SDK?
Do I have to tell it were to find the 10.6 SDK?

Generally, you don't need to use the 10.6 SDK to deploy to 10.6.  That's what 
the deployment target is for.  This has been discussed many times on may lists. 
 ex:
http://www.clarkcox.com/blog/2009/06/23/sdks-and-deployment-targets/

So many questions, and no answers on the cmake Website.

Well, these are perhaps more OS X questions... you'd have many of the same 
issues using Xcode directly.

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Building Mac OSX .apps for Sys 10.6 and 10.8 with Cmake using 10.7.5 on the command line

[Sean McBride]

On Fri, 8 Feb 2013 10:53:16 -0800, Ed said:

 I've never heard of CMAKE_OSX_64 and google has only 7 results…

CMAKE_OSX_64 is just a variable in the cmakelists.txt file which is
converted to ARCH=X86_64.
Does this variable need to be set to CMAKE_OSX_ARCHITECTURES=X86_64
instead of ARCH=X86_64?

If you want to build as x86_64 you should set CMAKE_OSX_ARCHITECTURES to x86_64.

Check with the developer to make sure OpenCPN works with this version
of Mac OS X.  You may need to reinstall the application.  Be sure to
install any available updates for the application and Mac OS X.
I cannot build the i386 version because wxWidgets 2.9.4 only supports
X86_64 and the 2.8.12 (which only supports i386) version of wxWidgets is
very buggy for the more Modern OS X operating systems.

Are you sure all the various libraries you're linking with were also built with 
the correct deployment target?

You should also try 'lipo -info /path/to/file' to make sure your app/libraries 
are built for the architecture you expect.

 http://www.clarkcox.com/blog/2009/06/23/sdks-and-deployment-targets/

I read the whole page at the Web link you mentioned but it does not
apply to this problem as it does not use Cmake and the article is over 3
years old which makes it obsolete.

It is not obsolete.  It explains the OS X concepts of deployment and SDK 
correctly (you appeared to be unfamiliar with them); these concepts have been 
around for many years.

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Building Mac OSX .apps for Sys 10.6 and 10.8 with Cmake using 10.7.5 on the command line

[Sean McBride]

On Thu, 7 Feb 2013 17:05:55 -0800, Ed said:

I am trying to build an app to be compatible with Mac OSX systems 10.6,
10.7, and 10.8 using the command line with cmake.  I have successfully
built it for 10.7.5, now I would like to expand this app to be
compatible with 10.6 and 10.8 is this possible?
This is the command I am issuing to cmake:
cmake -DCMAKE_OSX_64=ON -DCMAKE_C_COMPILER=/usr/bin/gcc -
DCMAKE_CXX_COMPILER=/usr/bin/g++ ..

Could anyone help me to build this app to be compatible with the other
two system?

The most important thing is to set the deployment target to 10.6.  See 
CMAKE_OSX_DEPLOYMENT_TARGET.  If you want to support both 32 and 64 bit CPUs, 
you should also set the architectures, see CMAKE_OSX_ARCHITECTURES.

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Building CMake 2.8.10.2 -- package created named cmake-2.8.10.2-Darwin-i386.dmg?

[Sean McBride]

On Tue, 5 Feb 2013 09:22:35 -0600, Kent Williams said:

And the reason it says i386 is that CPACK_SYSTEM_NAME defaults to the
output of uname -p which on OS X 10.7.5 is 'i386'

So CMake is behaving as documented, and OS X is wrong ;-) Quelle Surprise!

OS X returns 'i386' for 'uname -p' deliberately.  I don't have a link handy, 
but when doing the 64 bit transition years ago, Apple tried to change it to 
x86_64 but way too many things broke, expecting the broad family type (ex: ppc, 
arm, intel).  Perhaps 'uname -m' is more to your liking...

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] CMake 2.8.8 Upgrade problem with Xcode on OS X 10.8

[Sean McBride]

Just following up after a little while...


On Sat, 8 Sep 2012 10:48:11 -0400, David Cole said:

Does this happen regardless of which Xcode you select, or only with
the -DP4 one?

Happens with any of them.

Does this still happen for you if you use CMake from the 'next' branch?

Seems fixed in 2.8.10rc2 BTW.

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] CMake passes compiler flags to linker

[Sean McBride]

On Tue, 2 Oct 2012 22:35:31 +0530, Arindam Mukherjee said:

I have used CMAKE_CXX_FLAGS and CMAKE_EXE_LINKER_FLAGS variables to
pass custom options to the C++ compiler and linker. However, cmake
seems to be passing the flags meant only for the compiler to the
linker too.

That's a pet peeve of mine too.  You might want to add your scenario here:

http://public.kitware.com/Bug/view.php?id=12652

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] problem building CMake with clang's -fcatch-undefined-behavior

[Sean McBride]

On Tue, 25 Sep 2012 08:34:57 -0400, David Cole said:

If there really is a problem here, it looks like it comes from the
structure returned by a call to the readdir function which is implemented
by the system libraries. So if there's a problem here, I don't think it's
CMake's fault.

You were quite right.  It wasn't a false positive from 
-fcatch-undefined-behavior, but it was an OS X 10.7 bug (fixed in 10.8), not a 
CMake bug.

Sorry for the noise.

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] GCOV Coverage Testing. Mac OS X with Clang. Getting gcno files, but no gcna files after execution.

[Sean McBride]

On Sun, 23 Sep 2012 01:33:04 -0700, Aaron Smith said:

I'm working on a C project and using CMake. I've been trying to get
coverage testing working and am just about there.

This is what I have figured out so far:

-use clang for c compiler. gcc on the latest Xcode does nothing with
-fprofile-arcs and -ftest-coverage

The latest Xcode doesn't even include gcc, that's just a symlink for 
compatibility.

-add -fprofile-arcs and -ftest-coverage to c debug flags
-set cmake build type to debug
-run cmake to build makefile
-double check that gcno files are created for each source file compiled
(they are).

This is where i'm stuck now. I run one of my unit tests and I don't get any
.gcna files created.

You may be seeing these:
http://llvm.org/bugs/show_bug.cgi?id=11760
http://llvm.org/bugs/show_bug.cgi?id=11457
http://llvm.org/bugs/show_bug.cgi?id=11809

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://www.cmake.org/mailman/listinfo/cmake

[CMake] problem building CMake with clang's -fcatch-undefined-behavior

[Sean McBride]

Hi all,

My dashboards used to build CMake with clang's -fcatch-undefined-behavior, but 
now they've given it more smarts (to catch more bugs) and now one can't build 
CMake with this flag.

Here's the build failure:

http://open.cdash.org/viewBuildError.php?buildid=2562276

It seems, near the end of the build, that the just-built cpack is run to do 
something or other.  This process dies:

$ gdb --args ../bin/cpack --help-full 
/Users/builder/external/CMake-clang-dbg-x86_64/Docs/cpack.txt --help-full 
/Users/builder/external/CMake-clang-dbg-x86_64/Docs/cpack.html --help-full 
/Users/builder/external/CMake-clang-dbg-x86_64/Docs/cpack.1 --help-full 
/Users/builder/external/CMake-clang-dbg-x86_64/Docs/cpack.docbook

(gdb) r
Starting program: /Users/builder/external/CMake-clang-dbg-x86_64/bin/cpack 
--help-full /Users/builder/external/CMake-clang-dbg-x86_64/Docs/cpack.txt 
--help-full /Users/builder/external/CMake-clang-dbg-x86_64/Docs/cpack.html 
--help-full /Users/builder/external/CMake-clang-dbg-x86_64/Docs/cpack.1 
--help-full /Users/builder/external/CMake-clang-dbg-x86_64/Docs/cpack.docbook
Reading symbols for shared libraries 
++ done

Program received signal EXC_BAD_INSTRUCTION, Illegal instruction/operand.
0x000100fac2e9 in cmsys::Directory::Load (this=0x7fff5fbfba90, 
name=0x101f51c28 /Users/builder/external/CMake/Modules/) at 
/Users/builder/external/CMake/Source/kwsys/Directory.cxx:223
223 this-Internal-Files.push_back(d-d_name);

(gdb) bt
#0  0x000100fac2e9 in cmsys::Directory::Load (this=0x7fff5fbfba90, 
name=0x101f51c28 /Users/builder/external/CMake/Modules/) at 
/Users/builder/external/CMake/Source/kwsys/Directory.cxx:223
#1  0x000100fb158e in cmsys::Glob::ProcessDirectory (this=0x7fff5fbfc170, 
start=0, dir=@0x7fff5fbfbbf0) at 
/Users/builder/external/CMake/Source/kwsys/Glob.cxx:302
#2  0x000100fb451a in cmsys::Glob::FindFiles (this=0x7fff5fbfc170, 
inexpr=@0x7fff5fbfc168) at 
/Users/builder/external/CMake/Source/kwsys/Glob.cxx:464
#3  0x000100653545 in cmDocumentation::getDocumentedModulesListInDir 
(this=0x7fff5fbfe8f8, path=@0x7fff5fbfcab8, globExpr=@0x7fff5fbfcab0, 
docedModuleList=@0x7fff5fbfcae8) at 
/Users/builder/external/CMake/Source/cmDocumentation.cxx:771
#4  0x0001fc9e in main (argc=9, argv=0x7fff5fbff920) at 
/Users/builder/external/CMake/Source/CPack/cpack.cxx:554

(gdb) p name
$1 = 0x101f51c28 /Users/builder/external/CMake/Modules/

(gdb) p *this
$2 = {
  Internal = 0x101f51a80
}

(gdb) p d
$3 = (struct dirent *) 0x102010664

(gdb) p *d
$4 = {
  d_ino = 387485515, 
  d_seekoff = 1769662337112866820, 
  d_reclen = 48, 
  d_namlen = 20, 
  d_type = 8 '\b', 
  d_name = 
AutomocInfo.cmake.in\000\000\000\000\000\000\000?\032?\030\000\000\000\000\005\000\000\000?\032?\030D\000+\000\bBasicConfigVersion-AnyNewerVersion.cmake.in\000\000\000\000?\032?\030\000\000\000\000\006\000\000\000?\032?\030D\000(\000\bBasicConfigVersion-ExactVersion.cmake.in\000\000\000\000\000\000\000?\032?\030\000\000\000\000\a\000\000\000???\032H\000,\000\bBasicConfigVersi...
}

It might be a false positive, though I have yet to see any from this tool.

I'm hoping someone that knows the code can see the problem.

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Errors in Info.plist of Mac GUI app for CMake 2.8.9

[Sean McBride]

On Thu, 20 Sep 2012 11:36:53 -0700, James Walker said:

The Info.plist for CMake 2.8-9.app has an empty string for CFBundleName, 
making it show up without a name in utilities such as Activity Monitor. 
  It's also bad that there is an empty string for CFBundleIdentifier, 
CFBundleVersion, CFBundleShortVersionString, CFBundleGetInfoString, and 
NSHumanReadableCopyright.

See:
http://public.kitware.com/Bug/view.php?id=11694

and sorta related:
http://public.kitware.com/Bug/view.php?id=11693

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] CMake and OS X compiler tools without SDK

[Sean McBride]

On Thu, 20 Sep 2012 14:26:54 -0600, David Gobbi said:

Hi All,

Just yesterday, Apple released new Command Line Tools for XCode 4.5.
 Unlike their previous command-line compiler tools, these new tools no
longer require XCode.  They are stand-alone.

You sure?  I'm pretty sure the 4.4 command line tools didn't need Xcode.app 
either.

However, there is a caveat.  CMake is looking for (and not finding) an
XCode SDK.

When I configure VTK, for example, cmake sets this:

CMAKE_OSX_SYSROOT:PATH=/Developer/SDKs/MacOSX10.7.sdk

Odd.  For several Xcode releases now, /Developer is gone, and CMake was updated 
fro this change already.  Which CMake are you using?  You might try with ToT.

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Errors in Info.plist of Mac GUI app for CMake 2.8.9

[Sean McBride]

On Thu, 20 Sep 2012 16:40:20 -0400, Michael Jackson said:

I use the following macro in my own projects:

Perhaps you are in a position to make a patch to fix CMake.app itself? :)

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] CMake and OS X compiler tools without SDK

[Sean McBride]

On Thu, 20 Sep 2012 16:16:19 -0600, David Gobbi said:

 You sure?  I'm pretty sure the 4.4 command line tools didn't need
Xcode.app either.

Could be.  I'm still using XCode 3.2 on my own box.  It's the people
working under me who are using newer versions.

A! :)  I think it's been this way since even before 4.4 actually.

This is with cmake 2.8.9, so the latest version.  What do you mean by ToT?

Top of Tree.  As in: newest from source control.

It could very well be that the person that I was helping with
this problem set some variables when I was elsewhere...

Could be, but there was some Xcode related issue I had just recently that's 
still in 2.8.9 but fixed in ToT/2.8.10.

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[Sean McBride]

kitware-provided CMake installer/executables should be codesigned with 
'Developer ID' for GateKeeper on OS X
http://public.kitware.com/Bug/view.php?id=13532


--

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

Re: [CMake] CMake 2.8.8 Upgrade problem with Xcode on OS X 10.8

[Sean McBride]

Hi all,

I believe I am seeing this too.  I have 3 versions of Xcode installed:

/Applications/Xcode4.3.3.app
/Applications/Xcode4.4.1.app
/Applications/Xcode4.5-DP4.app

I am careful to have no spaces or weird characters in those names.  I am 
careful to use 'sudo xcode-select -switch' to point to the one I want.  I 
always start with an empty bin directory.

But CMake 2.8.9 always fails like this:

-
-- Check for working C compiler using: Xcode
-- Check for working C compiler using: Xcode -- broken
CMake Error at 
/Applications/CMake.app/Contents/share/cmake-2.8/Modules/CMakeTestCCompiler.cmake:52
 (MESSAGE):
  The C compiler /usr/bin/gcc is not able to compile a simple test program.

  It fails with the following output:

   Change Dir: 
/Volumes/Leopard/Users/sean/kitware/VTK-analyze-bin/CMakeFiles/CMakeTmp

  

  Run Build Command:/Applications/CMake.app/Contents/bin/cmakexbuild -project
  CMAKE_TRY_COMPILE.xcode build -target cmTryCompileExec2711236228
  -buildstyle Development

  xcodebuild: error: option '-buildstyle' is no longer supported
-

If I rename one of my Xcodes to just Xcode.app and 'sudo xcode-select 
-switch' to it, things work fine.

Can anyone repro that?

Thanks,

Sean





On Thu, 9 Aug 2012 19:52:49 +, Michael Toy said:

I have seen this problem as we upgraded from older XCodes.  In all the
places where cmake looks at your version of Xcode except one, it looks
at xcode-select -print–path.  In that one place, it looks in /
Developer/Applications/XCode.app.  I think this bug is fixed in 2.8.9,
and until then you can work around it by placing a symlink from /
Developer/Applications/XCode.app to your actual Xcode installation.

From: Etuka Onono et...@tesco.netmailto:et...@tesco.net
Date: Wednesday, August 8, 2012 5:34 PM
To: cmake@cmake.orgmailto:cmake@cmake.org
cmake@cmake.orgmailto:cmake@cmake.org
Subject: [CMake] CMake 2.8.8 Upgrade problem with Xcode on OS X 10.8

After I upgraded to OS X 10.8, I recently upgraded my CMake version to 2.8.8.

I can build CMake projects if I use Unix Makefiles as a generator, but
if I use the Xcode generator, I get the following error:

The C compiler identification is GNU 4.2.1
The CXX compiler identification is GNU 4.2.1
Checking whether C compiler has -isysroot
Checking whether C compiler has -isysroot - yes
Checking whether C compiler supports OSX deployment target flag
Checking whether C compiler supports OSX deployment target flag - yes
Check for working C compiler using: Xcode
Check for working C compiler using: Xcode -- broken

CMake Error at /Developer/CMake 2.8-8.app/Contents/share/cmake-2.8/
Modules/CMakeTestCCompiler.cmake:52 (MESSAGE):
The C compiler /usr/bin/gcc is not able to compile a simple test program.

It fails with the following output:

Change Dir: /Users/etuka/projects/baml/onethousand/build/CMakeFiles/CMakeTmp


Run Build Command:/Developer/CMake\ 2.8-8.app/Contents/bin/cmakexbuild
-project CMAKE_TRY_COMPILE.xcode build -target cmTryCompileExec3395723889
-buildstyle Development

xcodebuild: error: option '-buildstyle' is no longer supported

I understand that this error is associated with earlier versions of
Cmake that are incompatible with Xcode 4.4.  I have tried removing all
traces of CMake 2.8.8 that I can from my system and re-installing, but I
cannot get rid of this error.  I would be grateful for suggestions of
what to try next.
--

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

Re: [CMake] CMake 2.8.8 : Reproducible Crash in Mac OS X 10.8

[Sean McBride]

On Mon, 13 Aug 2012 16:40:05 -0400, Bill Hoffman said:

On 8/12/2012 1:25 PM, Michael Jackson wrote:
 I think you can actually download the Command line tools and install
 them_without_  installing Xcode. Have not tried but this is what I am
 led to believe.
I don't think that is true. Xcode does install them, it just does not 
put them in the PATH...

Those are both true.

If you install only Xcode.app, the command line tools are there, but not in 
your path, making them seem missing.

You can also decide not to download the 4 GB Xcode.app and instead download 
only the smaller 'command line tools' installer.

-- 

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Xcode without 'command line tools' xcrun CMake

[Sean McBride]

On Fri, 13 Jul 2012 11:03:02 -0400, Bill Hoffman said:

I am guessing some of the tools will not run without proper environments 
set.  So, running the command line compilers will not work by doing lots 
of calls to xcrun -find  Think, ld, ar, gcc, g++, cfront, and all 
the other stuff you need to run a compiler and cmake on the mac.   I 
think we will have to take the stance that we do on windows, you have to 
run cmake from a shell that is setup to run the compiler.

Perhaps, I'm not enough of a shell nor cmake expert to say...

Is there an xcvars?

Not that I know of.  That would be analogous to...?  What would it do?  

For now, I've created this bug:

CMake should support default installation of Xcode.app only, without 'command 
line tools' extras
http://public.kitware.com/Bug/view.php?id=13408

Relatedly, on my new-from-the-store Mac Mini, I'm getting two test failures:
http://open.cdash.org/viewTest.php?onlyfailedbuildid=2445802

both because the tests can't find PackageMaker.  Indeed, PackageMaker is no 
longer part of the default Xcode.app, nor is it installed as part of the 
'command line tools' but rather part of the separate 'auxiliary tools' (there 
are about 7 stupid installers for all these separate things now).

Perhaps these tests should only be run conditional on the presence of 
PackageMaker instead of allowed to fail hard?

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Xcode without 'command line tools' xcrun CMake

[Sean McBride]

On Tue, 17 Jul 2012 14:22:20 -0400, Bill Hoffman said:

 Not that I know of.  That would be analogous to...?  What would it do?

In VS it setups the environment to run CC from the command line.


 For now, I've created this bug:

 CMake should support default installation of Xcode.app only, without
'command line tools' extras
 http://public.kitware.com/Bug/view.php?id=13408

I am not sure I agree with the statement.  CMake has always required 
that the command line tools that it uses be in the environment.  I 
really don't see how CMake could technically use xcrun to configure an 
environment correctly so that things would work.  On all platforms CMake 
requires the environment to work from the command line.

Well, I don't know enough about how cmake works internally, but I was under the 
impression that it looks for things in certain well-known places in hopes of 
finding them.  I just greped the code for 'usr/local/bin' and here's an example 
of what I mean:

  set(gp_cmd_paths ${gp_cmd_paths}
C:/Program Files/Microsoft Visual Studio 9.0/VC/bin
C:/Program Files (x86)/Microsoft Visual Studio 9.0/VC/bin
C:/Program Files/Microsoft Visual Studio 8/VC/BIN
C:/Program Files (x86)/Microsoft Visual Studio 8/VC/BIN
C:/Program Files/Microsoft Visual Studio .NET 2003/VC7/BIN
C:/Program Files (x86)/Microsoft Visual Studio .NET 2003/VC7/BIN
/usr/local/bin
/usr/bin
)

Is this not a trial-and-error way of finding which folder holds the sought 
item?  Wouldn't it be a matter of extending this facility?  (Not that I'm 
saying it would be trivial to do so...)

 Perhaps these tests should only be run conditional on the presence
 of
PackageMaker instead of allowed to fail hard?

This we might be able to fix.

Cool.  Shall I create a bug for that?

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Xcode without 'command line tools' xcrun CMake

[Sean McBride]

On Fri, 13 Jul 2012 10:18:38 -0400, Bill Hoffman said:

 xcrun make --version

That is so totally stupid

What were they thinking at Apple...

I'm not privy to their thinking but... one advantage to this approach is the 
ability to have multiple versions of Xcode installed.  I have the current 4.3.3 
and the latest betas of 4.4 and 4.5.  I can invoke 'xcode-select -switch' to 
redirect 'xcrun' to any Xcode.app.  Then 'xcrun clang' will use the clang 
embedded in the chosen Xcode.app.  It's pretty useful really.

CMake wouldn't *need* to invoke 'xcrun make' to invoke make, though that's one 
way.  The other way is to ask xcrun to give you the path to make, ex:

$ xcrun -find make
/Applications/Xcode.app/Contents/Developer/usr/bin/make

Most of this is just a rant

Much of Apple's recent behaviour is very rant worthy, IMNSHO.

-- 

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://www.cmake.org/mailman/listinfo/cmake

[CMake] Xcode without 'command line tools' xcrun CMake

[Sean McBride]

Hi all,

Nowadays, Xcode is distributed as a standalone .app instead of an installer 
that copies files all over the place.  As a consequence of this, nothing gets 
installed at /usr/bin/make, /usr/bin/cc, etc.

Optionally, one can install a separate 'command line tools' package that places 
things at those venerable locations.  Without installing that, one can still 
find and use 'make' and other tools using 'xcrun' (see 'man xcrun').  ex:

$ xcrun make --version
GNU Make 3.81

$ xcrun -find make
/Applications/Xcode.app/Contents/Developer/usr/bin/make

Without the 'command line tools' installed, CMake seems unable to get far:

Error(s) when configuring the project
CMake Error: CMake was unable to find a build program corresponding to Unix 
Makefiles.  CMAKE_MAKE_PROGRAM is not set.  You probably need to select a 
different build tool.

It would be nice if CMake would invoke 'xcrun -find' to find the paths to the 
tools it needs.  Or can it already, and I'm missing something?

Thanks,

-- 

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Latest Xcode install (4.3.x) and CMake error

[Sean McBride]

On Thu, 28 Jun 2012 09:16:31 -0400, Michael Jackson said:

 Error: No developer directory found at /Developer.  Run
 /usr/bin/xcode-select to update the developer directory path.

Hey Mike!

Maybe your xcode-select is still pointing to /Developer?  Try rerunning 
xcode-select to point it to /Applications/Xcode.app (or where ever).  It has a 
pretty good man page too BTW.

-- 

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] CMake 2.8-8 rc1 and Xcode 4.3

[Sean McBride]

On Tue, 27 Mar 2012 16:59:07 +0200, Daniel Dekkers said:

I've upgraded to Xcode 4.3 and CMake to 2.8-8 rc1 on a Snow Leopard system.

Xcode 4.3 requires Mac OS X 10.7 Lion.  On 10.6, the last version you can use 
is 4.2.  See:
http://en.wikipedia.org/wiki/Xcode

-- 

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Problems with coverage on OS X Server

[Sean McBride]

On Sat, 24 Mar 2012 08:53:04 -0400, David Cole said:

The answer to that stackoverflow question recommends using
clang/clang++ instead. (I have not tried this yet myself, but would
not be entirely surprised to find out it's correct. I have observed
the zero coverage phenomenon on my own Mac laptop, but have sufficient
coverage capabilities elsewhere... so I didn't care enough to follow
up on it previously.)

The state of code coverage with Mac OS tools is not great.  The gcc and 
llvm-gcc that Apple ship don't support coverage.  clang didn't support it for a 
long time, but now does, but there are still a number of bugs, notably this one:

http://llvm.org/bugs/show_bug.cgi?id=11457

-- 

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Problems with coverage on OS X Server

[Sean McBride]

On Sat, 24 Mar 2012 17:34:22 +, NoRulez said:

But i?t seems that there is something missing, because I also get the
message that no coverage files were found for some projects:

-- Coverage Continuous  --
Cannot find any coverage files. Ignoring Coverage request.

Here are my version informations:
$ clang --version
Apple clang version 3.0 (tags/Apple/clang-211.10.1) (based on LLVM 3.0svn)

What version of Xcode is that from?  IIRC, that version of clang is too old to 
support coverage.  Update to Xcode 4.3.2.

-- 

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[Sean McBride]

Support for Xcode 4.3 (sic)
http://public.kitware.com/Bug/view.php?id=12621


--

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

Re: [CMake] CHECK_C_COMPILER_FLAG (very) broken with icc!

[Sean McBride]

On Fri, 13 Jan 2012 17:54:23 +0100, Szilárd Páll said:

Additionally, IMHO it's quite unfortunate that such a widely used
compiler as the Intel Compiler has such flaky support in CMake.

Searching today's dashboard for icc, I see only 1 entry:
http://www.cdash.org/CDash/index.php?project=CMake

I'm sure the community would benefit from additional submissions.  icc costs 
money, making it harder...

-- 

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[Sean McBride]

Might be nice to decide about this one:
http://public.kitware.com/Bug/view.php?id=4756

Sean


--

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

Re: [CMake] Bug fix requests for the *next* release of CMake...

[Sean McBride]

http://public.kitware.com/Bug/view.php?id=12652


--

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

Re: [CMake] CMAKE_LANG_FLAGS also used for linking?

[Sean McBride]

From the lack of reply, I guess there is indeed no way to specify flags only 
for compiling and not for linking.

Is there a bug in the Mantis for this already?

Sean



On Tue, 20 Dec 2011 11:12:17 -0500, Sean McBride said:

Hi all,

Searching the archives, I see that CMake deliberately passes the
CMAKE_LANG_FLAGS for linking too:

http://www.cmake.org/pipermail/cmake/2010-July/038090.html

If I add -std=c++0x to CMAKE_CXX_FLAGS, then compilation is fine, but
clang will warn when linking:

clang-3: warning: argument unused during compilation: '-std=c++0x'

How does one specify flags only for compilation, not linking?


--

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

Re: [CMake] CMAKE_LANG_FLAGS also used for linking?

[Sean McBride]

On Fri, 23 Dec 2011 14:06:30 -0500, David Cole said:

 From the lack of reply, I guess there is indeed no way to specify
flags only for compiling and not for linking.

 Is there a bug in the Mantis for this already?

I don't think so, but is it really a bug in CMake?

Obviously that's up for discussion. :)

My goal was to add the -std=c++0x flag to my dashboards, to ensure that their 
codebases are C++ compatible.  But that flag therefore gets passed in the link 
phase, and spews:

clang-3: warning: argument unused during compilation: '-std=c++0x'

So I guess my question is: how can I use -std=c++0x without getting warnings?

-- 

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] CMAKE_LANG_FLAGS also used for linking?

[Sean McBride]

On Fri, 23 Dec 2011 20:12:07 +0100, Rolf Eike Beer said:

Try SET_SOURCE_FILES_PROPERTIES(${MYCPPS} PROPERTIES COMPILE_FLAGS --
std=c++0x)

Thanks, but I'm looking to do this on my CMake/ITK/VTK dashboards, I can't 
change their CMake files

-- 

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://www.cmake.org/mailman/listinfo/cmake

[CMake] CMAKE_LANG_FLAGS also used for linking?

[Sean McBride]

Hi all,

Searching the archives, I see that CMake deliberately passes the 
CMAKE_LANG_FLAGS for linking too:

http://www.cmake.org/pipermail/cmake/2010-July/038090.html

If I add -std=c++0x to CMAKE_CXX_FLAGS, then compilation is fine, but clang 
will warn when linking:

clang-3: warning: argument unused during compilation: '-std=c++0x'

How does one specify flags only for compilation, not linking?

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://www.cmake.org/mailman/listinfo/cmake

[CMake] Enabling code coverage on clang dashboard

[Sean McBride]

Hi all,

Now that clang supports code coverage, I thought I'd enable it on my CMake 
dashboards, but I'm a little confused as to how.

I've read this, but it's only partly helpful:
http://www.cmake.org/Wiki/CTest:Coverage

Building cmake itself, if I use only cmake (not ctest nor cdash) then things 
compile and link if I use these settings:

CMAKE_CXX_FLAGS -fprofile-arcs -ftest-coverage
CMAKE_C_FLAGS -fprofile-arcs -ftest-coverage
CMAKE_EXE_LINKER_FLAGS -I/Developer/usr/lib -lprofile_rt

 
CMAKE_MODULE_LINKER_FLAGS -I/Developer/usr/lib -lprofile_rt 


CMAKE_SHARED_LINKER_FLAGS -I/Developer/usr/lib -lprofile_rt 



Is this right?  I'm especially uncertain about the linker flags.

Also, this seems to leave gunk in the git repo:

# Untracked files:
#   (use git add file... to include in what will be committed)
#
#   Tests/CommandLineTest/CMakeFiles/
#   Tests/CustomCommandWorkingDirectory/CMakeFiles/
#   Tests/Java/CMakeFiles/

Is that a bug?  Does it happen with gcc?

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] CMake and Sandboxed Mac OS X app

[Sean McBride]

On Tue, 22 Nov 2011 11:45:29 -0500, David Cole said:

What are the requirements for a Sandboxed app? Is there a
documentation page from Apple that describes what needs to be in the
Info.plist to support Sandboxing?

The main doc is here:
http://developer.apple.com/library/mac/#documentation/Security/Conceptual/AppSandboxDesignGuide/AboutAppSandbox/AboutAppSandbox.html

It's more than just adding keys in Info.plist, the app also needs to be 
codesigned, which is typically done by invoking the 'codesign' tool (see man 
codesign).

-- 

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] CMake and Sandboxed Mac OS X app

[Sean McBride]

On Tue, 22 Nov 2011 18:35:42 +0100, NoRulez said:

did you know if I also need special compiler and/or linker flags?

That's more of an Xcode question than a CMake question... IIRC, no you don't.  
You just need to add your entitlements file and codesign.  But it's been a few 
months since I played with App Sandbox.  It's still half-baked and I gave up on 
it.

-- 

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://www.cmake.org/mailman/listinfo/cmake

[CMake] CMake 2.4.6 and Xcode 4.2 on Mac OS X 10.7

[Sean McBride]

Hi all,

I've updated one of my dashboard machines to 10.7 and Xcode 4.2 and am having 
trouble with the Xcode generator.  It fails with:

-
The C compiler /usr/bin/llvm-gcc is not able to compile a simple test
  program.

  It fails with the following output:

   Change Dir: 
/Users/builder/external/CMake-xcode-dbg-x86_64/CMakeFiles/CMakeTmp

  

  Run Build Command:/Applications/CMake.app/Contents/bin/cmakexbuild -project
  CMAKE_TRY_COMPILE.xcodeproj build -target cmTryCompileExec -configuration
  Debug
-

The Xcode project file at:

/Users/builder/external/CMake-xcode-dbg-x86_64/CMakeFiles/CMakeTmp/CMAKE_TRY_COMPILE.xcodeproj

is but an empty folder, and Xcode crashes trying to open it.

If I use /usr/bin/clang things work.

Anyone tried a similar setup?  How to debug this further?

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] CMake 2.4.6 and Xcode 4.2 on Mac OS X 10.7

[Sean McBride]

On Tue, 8 Nov 2011 11:06:46 -0500, David Cole said:

More info, please...

I assume you mean CMake 2.8.6 and not 2.4.6, as in the subject line... :-)

Doh!

Are you setting CC and CXX before calling cmake -G Xcode ../CMake?

Yes, see:
http://www.cdash.org/CDash/viewNotes.php?buildid=1705589

That's not a valid way of setting the compiler to a different compiler
with the Xcode generator.

Ah.

Are you trying to build CMake or some other project?

CMake.

In reality, the Xcode generator only works 100% reliably well when you
do not try to specify the compiler, and let Xcode use the one it wants
to use by default.

OK, I'll just stop specifying it.

Thanks!

-- 

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Symlinks not created on OS X

[Sean McBride]

On Mon, 31 Oct 2011 17:27:38 -0700, Jerry said:

The OS X .dmg installer, cmake-2.8.6-Darwin64-universal.dmg, at http://
www.cmake.org/cmake/resources/software.html, failed to install symlinks
in /usr/bin as promised. I received six messages, I think from the Cmake
app, of this nature:

Failed create symlink installation may be incomplete: x

where x was ccmake, cmake, cmake-gui, cmakexbuild, cpack, and ctest. I
made the symlinks manually and things seem to work OK.

Perhaps you're seeing this:
http://public.kitware.com/Bug/view.php?id=10056

see also:
http://public.kitware.com/Bug/view.php?id=11693

-- 

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] *.so on Mac

[Sean McBride]

On Mon, 5 Sep 2011 06:49:45 +0200, Michael Wild said:

 Shouldn't dynamic libraries on Mac have dylib as their extension? 

 Why does MyLib have an extension so when I use add_library(MyLib MODULE)?

 Thanks

 Yifei

Because a MODULE is normally a plugin library, and these 
traditionally have the extension .so on Mac.

Do they?

I just searched all of /System and the only .so I find are in Python.framework. 
 I've been using Macs since the early 90s, I don't recall any tradition of 
using .so for anything, but could be wrong...

-- 

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[Sean McBride]

David,

http://public.kitware.com/Bug/view.php?id=12381

Cheers,

Sean


___
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

Re: [CMake] Bug fix requests for the *next* release of CMake...

[Sean McBride]

bugs:
http://public.kitware.com/Bug/view.php?id=11746
http://public.kitware.com/Bug/view.php?id=8563
http://public.kitware.com/Bug/view.php?id=6215
http://public.kitware.com/Bug/view.php?id=7867
http://public.kitware.com/Bug/view.php?id=10895

features:
http://public.kitware.com/Bug/view.php?id=12300

not a bug, but a distribution consideration:
http://public.kitware.com/Bug/view.php?id=9839

Cheers!

Sean


___
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

Re: [CMake] Enabling C99 in CMake

[Sean McBride]

On Thu, 23 Jun 2011 18:20:46 +0200, Jed Brown said:

 You need to use a C99 compiler for your project


This is already a problem. C99 introduces new keywords (e.g. restrict) and
removes implicit int. It is entirely possible for part of a project to
include C89-conforming legacy code that is not valid C99. The use of C99 or
C89 should be a file- and directory-level property.

It's also horrible to encumber the poor user just trying to build your
project with needing to know whether it is written in C99 or whatever else,
nor with how to make their compiler deliver that dialect.

CMake does not ask the user to provide the full command to link a shared
library, it should not require the user to specify dialect C99/C89.

I agree.  And of course this problem is not limited to C, there are several 
not-fully-compatible versions of C++ too.  gcc accepts flags like -std=c++98 
and -std=c++0x to choose between them.  Different compilers presumably need 
different flags.

-- 

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Enabling C99 in CMake

[Sean McBride]

On Wed, 22 Jun 2011 12:32:55 -0700, Todd Gamblin said:

Is there a good cross-platform way to enable C99 in a CMake project
right now?  You can obviously do this:

   set(CMAKE_C_FLAGS -std=c99)

However, that's the GNU way to enable C99, and other compilers do it
differently.  It would be nice if there were some flags for this set for
you in whatever platform file you're using, e.g.:

   set(CMAKE_C_FLAGS ${CMAKE_ENABLE_C99})

Or something to that effect.  Then you'd pick up -qlanglvl=c99 for xlc, -
std=c99 for gcc, etc.

Is there anything similar already in there?  I don't see anything
grepping around in the modules or platform files.

I don't think there is.  But it would be a good idea, and I suggest you file a 
bug.  The VTK dashboard has warnings for exactly this reason:

http://www.vtk.org/Bug/view.php?id=11952

-- 

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Cmake 2.8.4 and gcc 4.6 on OSX

[Sean McBride]

On Fri, 6 May 2011 10:51:57 -0400, Michael Allen said:

I've installed a newer version of gcc because the version supplied by
Apple is so far out of date, but I don't know how to configure cmake
such that it uses the normal gcc flags instead of the
Apple specific flags. Is there a way to configure cmake to use the
appropriate flags even though I'm not using the normal compiler?

IMHO, a Mac compiler that does not recognise -arch is pretty broken. 
Where did you get it?  I think if you use macports or fink you can get a
newer gcc that recognises the normal/typical flags.  Another option is
to use clang, which comes with recent versions of Xcode.

-- 

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Enabling C++0x support

[Sean McBride]

On Wed, 4 May 2011 23:58:56 +0200, Guido Winkelmann said:

Is there a way to specify, in a cross-platform compatible manner, that a
given 
C++ source file (or a target or an entire project) requires support for C
++ 0x, 
so that whatever compiler flags would be necessary for that for the current 
platform and compiler will be set?

For example, when using GCC, you need to pass -std=c++0x as an argument to 
the compiler in order to get C++0x support. I could just set(CMAKE_CXX_FLAGS 
-std=c++0x), but that's not really portable... the current platform might 
use a different compiler that needs a different option to enable C++ 0x and 
won't understand -std=c++0x, or, at some point in the future, it might
use a 
GCC release which makes 0x the default and does not even need a special flag.

It would indeed be nice to have such a thing.  VTK currently has a
similar problem where it passes -std=c99, a gcc flag unrecognised by clang:
http://vtk.org/Bug/view.php?id=11952

-- 

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Which MacOS installer to use and how?

[Sean McBride]

On Wed, 27 Apr 2011 15:34:45 +0200, Eric Noulard said:

I'd like to provide my software as a nice Mac OS installer,
and I am back into the Mac OS jungle:

  Bundle  = Mac OSX bundle
  DragNDrop   = Mac OSX Drag And Drop
  OSXX11  = Mac OSX X11 bundle
  PackageMaker= Mac OSX Package Maker installer

Which one should I go with?
My current projects currently contains only command lines tools
which I expect to install in standard place (may be /usr?) on the Mac.

The first thing to figure out is what you need to install where.  If
it's a bunch of command line tools, then maybe /usr/local/bin would be
the right place; don't install in /usr/bin !  Probably a .pkg is your
best bet.

-- 

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Which MacOS installer to use and how?

[Sean McBride]

On Wed, 27 Apr 2011 16:55:58 +0200, Eric Noulard said:

2011/4/27 Sean McBride s...@rogue-research.com:
 On Wed, 27 Apr 2011 15:34:45 +0200, Eric Noulard said:

I'd like to provide my software as a nice Mac OS installer,
and I am back into the Mac OS jungle:

  Bundle                      = Mac OSX bundle
  DragNDrop                   = Mac OSX Drag And Drop
  OSXX11                      = Mac OSX X11 bundle
  PackageMaker                = Mac OSX Package Maker installer

Which one should I go with?
My current projects currently contains only command lines tools
which I expect to install in standard place (may be /usr?) on the Mac.

 The first thing to figure out is what you need to install where.  If
 it's a bunch of command line tools, then maybe /usr/local/bin would be
 the right place; don't install in /usr/bin !   Probably a .pkg is your
 best bet.

Ok I'll go for /usr/local.

.pkg meaning ? which CPack generator?

Probably PackageMaker, though I've never used CPack.

I tried PackageMaker and even if I manage to build  execute the installer
it fails in the end.

Does it generate a .pkg file?  That's the format that the Mac OS X
installer (Installer.app) expects.

-- 

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[Sean McBride]

On Tue, 29 Mar 2011 13:56:03 -0400, David Cole said:

Now that we have released CMake 2.8.4, *now* would be a great time to
prioritize bug fixes for the next release of CMake.

http://public.kitware.com/Bug/view.php?id=11746

-- 

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] File remove_recurse doesn't on OSX

[Sean McBride]

On Wed, 16 Mar 2011 13:46:56 -0400, David Cole said:

Is the Mac file system in question case-sensitive, or
case-insensitive? (By default, most Macs are case-insensitive... and
we've had other reports of file weirdnesses on
case-sensitive-file-system-based Macs -- we do not have one of these
presently here at Kitware, so it's hard for us to repro any such bugs
to figure out if there is a good fix or not. Suggestions welcome.)

Using Disk Utility, you can create a disk image and use a case-sensitive
filesystem.  This is a handy way to do testing, without any formatting
of real disks.

-- 

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Fail to Compile cmake on OSX 10.4

[Sean McBride]

On Wed, 9 Mar 2011 18:38:52 +0100, Olivier Cessenat said:

I downloaded cmake-2.8.4 and also cmake-2.8.3 Unix sources and tried
to compile it for Mac OS-X 10.4.

What version of Xcode?  Which compiler?

-- 

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Installing cmake-2.8.4-Darwin-universal.dmg

[Sean McBride]

On Sun, 20 Feb 2011 09:43:10 +1100, Andrew Maclean said:

I am attempting to install this on Snow Leopard. The installation seems to
work Ok but fails at the Install Command Line Tools stage, with the message:
Failed create symlink installation may be incomplete: /usr/bin/ccmake
... and so forth for all the command line tools.

Clearly this is a permissions issue. The installer actually does ask for my
password and the gui seems to be successfully installed in the Apps folder,
so I suspect sudo rights are not being propagated to the symlink creation
stage.

This has failed for as long as I can remember.  It might be this:
http://public.kitware.com/Bug/view.php?id=10938

So how do I get the Command Lines stuff installed? (Aside from manually
creating them.)

What I do is add /Applications/CMake.app/Contents/bin to my PATH.  If
you do this, you'll also need to remember to rename the installed CMake
every time (to remove the version number):
http://public.kitware.com/Bug/view.php?id=11693

-- 

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://www.cmake.org/mailman/listinfo/cmake