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] [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] [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] 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/"
>
>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] 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] 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] 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] 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] 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] 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] 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] 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] 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 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 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 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] 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] 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 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 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] 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



--

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 mailto:et...@tesco.net>>
>Date: Wednesday, August 8, 2012 5:34 PM
>To: "cmake@cmake.org"
>mailto: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 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 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?onlyfailed&buildid=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 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 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] 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] Bug fix requests for the *next* release of CMake...

[Sean McBride]

Support for Xcode 4.3 (sic)



--

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]

--

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:


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] CMAKE__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

Re: [CMake] CMAKE__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__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__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

[CMake] CMAKE__FLAGS also used for linking?

[Sean McBride]

Hi all,

Searching the archives, I see that CMake deliberately passes the 
CMAKE__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 ..." 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 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

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 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

[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] 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,



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:






features:


not a bug, but a distribution consideration:


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 16:55:58 +0200, Eric Noulard said:

>2011/4/27 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.
>
>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] 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] 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

Re: [CMake] 2.8.4 order of tests

[Sean McBride]

On Thu, 17 Feb 2011 17:21:22 -0500, David Cole said:

>I'm not familiar enough with HDF5 to know if this is correct or not.
>Is this the same order you're seeing?
>
>Or can you tell me your expected order? I'll try to analyze the source
>tree and figure out what's going on, but what you expect will tell me
>something, too.

Perhaps you guys are actually talking about this:???
<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] Help with fixup_bundle for Mac OS - @executable_path, @loader_path, @rpath

[Sean McBride]

On Tue, 1 Feb 2011 08:39:08 -0800, Scott Fowler said:

>I have an application "Foo" which distributes a plugin for a separate
>application "Bar".  My plugin is dependent on libraries distributed with
>application "Foo".  When application "Bar" tries to load the plugin, the
>plugin will not load, as it cannot find the libraries distributed with "Foo".
>
>As far as I can tell this boils down to the @executable_path reference
>which fixup_bundle inserts into my binaries.
>
>>otool -L plugin.dylib
>@executable_path/../MacOS/libsomedependency.dylib
>@executable_path/../MacOS/libsomeotherdependency.dylib
>etc...
>
>When application "Bar" loads my plugin, I'm assuming that
>@executable_path resolves to the location of "Bar", but the plugin's
>dependent libraries are in Foo.app/Contents/MacOS, not in Bar.app/
>Contents/MacOS.
>
>All this leads me to believe that I should be using @loader_path or
>@rpath instead, but I don't see a way to do this using CMake as it
>appears that BundleUtilities.cmake and GetPrerequisites.cmake are
>hardcoded to use @executable_path.

Install names are such a PITA.  Here's a great overview:
<http://www.mikeash.com/pyblog/friday-qa-2009-11-06-linking-and-install-
names.html>

@loader_path was added in 10.4, and assuming you don't need to support
anything older, you should never use @executable_path because
@loader_path is the same or better.  Not sure if it will solve your
problem though.

-- 

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-rc2 ready for testing!

[Sean McBride]

On Tue, 1 Feb 2011 09:56:03 +0100, Johan Björk said:

>What is the intended behavior when upgrading CMake on a OSX Machine?
>It seems that currently, generated projects will keep a reference to
>the resolved symlink, ie
>/Applications/CMake\ VERSION/Contents/bin/..., causing confusing errors
>such as

Johan,

You might want to add your opinion to this bug, which discusses the root
cause of your issue:
<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] Bug fix requests for the *next* release of CMake...

[Sean McBride]

On Wed, 10 Nov 2010 13:30:46 -0500, David Cole said:

>If there are still others to consider for the 2.8.4 release, please
>reply here with just the bug numbers. Please do not hijack this thread
>to talk about specifics. Bug numbers only please. I really appreciate
>the vast majority here who have simply listed the issues of
>interest...

David,

I suggest this one:


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] Status of clang support?

[Sean McBride]

On Sun, 24 Oct 2010 16:33:01 +0100, Mateusz Loskot said:

>I'm trying to find out what's the status of clang support in CMake.
>What version of CMake is recommended to make proper use of clang 2.8+
>for building a C++ software, etc.

Somewhat off-topic, but if you're going to build C++ code with clang,
you should probably build clang yourself from trunk.  Its C++ support is
new and much better in trunk than 2.8.

I have dashboards that use CMake 2.8.3 and a recent build of clang to
build CMake, VTK, ITK, and GDCM nightly.

-- 
________
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] Suspicious CPU speed calculation on Mac

[Sean McBride]

On Mon, 18 Oct 2010 14:36:01 +, Rolf Eike Beer said:

>While hacking on gathering system information on QNX (currently completely
>missing) I found this in SystemInformationImplementation::ParseSysCtl() in
>source/kwsys/SystemInformation.cxx:
>
>  this->CPUSpeedInMHz = static_cast< float >( value )/ 1048576;
>
>From what I can find on the web the output is in Hz so it should be
>divided by 100, no?

I agree, looks like a copy-paste bug.  Indeed, the clock is wrong on our
dashboards, ex:
<http://www.cdash.org/CDash/viewSite.php?
siteid=1987&project=1¤ttime=1287795600>

Will you submit a bug/patch?

-- 
________
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] OS X architecture changes interfere with CheckTypeSize()?

[Sean McBride]

On Wed, 11 Aug 2010 18:08:35 +0200, Erik Lindahl said:

>All the CheckTypeSize() tests then seem to run directly when e.g. ccmake
>is invoked, and they thus set all SIZEOF_XXX defines to the 64-bit
>values (e.g. 8 for "long int").

Why do you need to know the size of 'long'?  Its size is not guaranteed
by the language spec.  If you're writing portable code, you should not
assume any more than the language guarantees.

If you need an integer of a specific size, use types like int32_t or
int64_t.  These are part of C99 and C++0x.  If they don't exist on some
platform you need to support, they are easy to typedef.

That said, if you already have a tonne of code.

-- 
________
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 Mon, 5 Jul 2010 14:31:17 -0400, David Cole said:

>If you have a particular issue that you think should be fixed for inclusion
>in 2.8.3, please bring it up now. Ideally, each issue will be discussed as
>needed on the mailing list to come to any consensus about what should be
>done to fix it, and then an entry in the bug tracker may be used to keep it
>on the radar screen, and to track activity related to it.

My feature wish list, in priority:

CTest cannot test multiple CPU architectures on Mac OS X
<http://public.kitware.com/Bug/view.php?id=6157>

CMake needs an Objective-C equivalent of CMAKE_CXX_FLAGS
<http://public.kitware.com/Bug/view.php?id=4756>

Add support for Clang Static Analyzer (similar to 1st class valgrind support)
<http://public.kitware.com/Bug/view.php?id=10208>


My bug fix wish list:

CTest/CDash OS version & compiler information is lacking on Mac OS X
<http://public.kitware.com/Bug/view.php?id=9663>

-- 
________
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] NCurses issues with OS X 10.6.3 and ccmake

[Sean McBride]

On Tue, 15 Jun 2010 18:05:06 -0400, Michael Jackson said:

>Just FYI that Apple released the OS X 10.6.4 update today that among  
>other things _should_ have fixed the messed up ncurses library that  
>stopped the arrow keys from working with ccmake.
>   As usual use the usual update mechanisms that Apple provides. If  
>anyone _does_ update could you post back to the list to verify that  
>the curses problem is either fixed or still remains broken.

I can confirm it's fixed.

-- 
________
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] No Native 64-Bit CMake Binaries?

[Sean McBride]

On Thu, 6 May 2010 11:45:21 -0500, Richard Wackerbarth said:

>See RogueResearch6 and Chameleon00.NFSNet.
>Both of these machines are reporting errors for some time.

The failing 'Architecture' test on Rogue6 fails on _both_ 32 and 64 bit
though.

-- 
________
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] No Native 64-Bit CMake Binaries?

[Sean McBride]

On Thu, 6 May 2010 08:17:53 -0400, Bill Hoffman said:

>It is not a resource issue.  I just don't see the need?   What good is a 
>64 bit CMake?   On Apple someone wanted to a 64 bit CMake, and I had 
>them do bench marks, and not noticeable difference could be discerned 
>between them.

That was me.  Our discussion is here:
<http://public.kitware.com/Bug/view.php?id=9839>

>So, maybe this is just a marketing thing?

Definitely partly.  Apple touts the 64 bit thing in its marketing:
<http://www.apple.com/macosx/>


On Thu, 6 May 2010 08:13:47 -0500, Richard Wackerbarth said:

>However, it will be a compatibility issue. Things evolve. Remember
>MacOSX 10.0, 10.1? Back then, you could have argued that we didn't need
>a new version of CMake. The binaries from MacOS 9 ran just fine. Now,
>not only can you not run those binaries, but you cannot even run an
>MacOSX 10.5(ppc) program on 10.6. Even though that worked just fine on
>10.5(Intel), it is no longer supported.

I agree with your sentiment, but a correction is in order: 10.6 can
still run PowerPC executables (under Rosetta), but Rosetta is no longer
installed by default.  It's clearly on it's way out.


On Thu, 6 May 2010 09:18:42 -0400, Bill Hoffman said:

>Sure, and the version (of OS X) where that happens, is when I would 
>start shipping 64 bit.   Right now having one binary seems cleaner, 

For Mac OS anyway, you'd still have 'one binary' thanks to the
'universal binary' concept.


On Thu, 6 May 2010 08:36:41 -0500, Richard Wackerbarth said:

>Yes, it works for now. However, the 64-bit version for MacOSX 10.6 is
>currently "broken" (at least to the extent that some of the tests don't
>"work out of the box" without specific configuration).

Oh?  We submit several nightly 64 bit builds, and I see no more problems
than 32 bit.  What problems?

-- 

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] Configure Mac OS X for 32-bit

[Sean McBride]

On Mon, 3 May 2010 10:27:35 -0600, Karl Merkley said:

>The code currently builds and runs in 32 or 64 bit on Linux, Mac and
>Windows.   What I would like to be able to do is to detect the build
>environment that the user starts cmake in and configure correctly for
>that environment.   For example,  if I am building on my 32-bit Linux
>box I want to detect that gcc needs the -m32 flag and have that added
>automatically to my build process without having the user specify the
>architecture.I'm not looking at supporting cross-platform builds on
>one system, I just want to build correctly on the system that the user
>starts the build on

What's 'correctly'?

For example, on Mac OS X 10.6 on 64 bit capable hardware (that is, any
Mac you buy today), the OS can run both 32 and 64 bit applications. 
Which is "correct"?

-- 
____
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] Configure Mac OS X for 32-bit

[Sean McBride]

On Mon, 3 May 2010 09:59:36 -0600, Karl Merkley said:

>I just read through this entire thread and I would like to expand it a
>little.   Regardless of platform, what is the right way to determine the
>right build architecture?  I run on a 32 bit Linux box but I use distcc
>which distributes the build to some 64 bit machines.I always just
>edit the CMakeCache.txt manually and add the -m32 flag.Some of my
>customers don't like that approach and would like to automate the
>decision for Mac, Linux and Windows.So I need to determine is that
>platform that cmake runs on 32 bit or 64 bit and then set the correct
>flags for each platform.

For Mac anyway, the 32/64 'bitness' of the building machine is
irrelevant.  PPC Macs can build Intel code, 32 bit Macs can build 64 bit
code, and vice versa, and etc.

Your code needs to be written such that it 1) supports both endiannesses
2) understands both 32 and 64 bit pointers 3) doesn't make invalid
assumptions about the size of int, long, void*, etc.  Only if your code
is properly written can it be built as either 32 or 64 bit.  Then I
guess the person doing the building also has to decide which kinds of
machines he's building for.

-- 
________
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] Configure Mac OS X for 32-bit

[Sean McBride]

On Sat, 1 May 2010 23:15:03 -0700, Tron Thomas said:

>It looks like:
>set (CMAKE_OSX_ARCHITECTURES "i386 ppc")
>
>will build a universal binary for a debug build on any platform.  How 
>can someone configure things so that Xcode will build a platform 
>specific debug version that is 32-bit?

Forgive me if this is obvious, but: it's ok if your debug build is a
universal binary also.  Yes it increases your build time (which granted
could be long) but it's quite valid to have universal debug versions.

Also, don't use -m32, -arch is the correct way.

What you need is a way to have different values of
CMAKE_OSX_ARCHITECTURES in Debug and Release.  If CMake doesn't support
this, it would make a good feature request.

-- 
________
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 running ccmake on Mac OSX

[Sean McBride]

On Wed, 28 Apr 2010 11:39:26 -0400, Michal Depa said:

>Since I prefer the linux interface to the GUI in the mac version, I got the
>source code for 2.8.1 and compiled it just as I would in linux. That worked
>fine, except that now when I run ccmake, cursor key presses on my keyboard
>don't seem to register and so I can't move around between the different
>options. It's strange because all the other keys work and do what they are
>supposed to do (c, h, t, even enter). I am running Snow Leopard (10.6.3). I
>remember that I did not have this problem before I upgraded from Leopard, so
>this might be a Snow Leopard specific problem. Is this a known issue? Any
>help would be appreciated.

This is a regression introduced in 10.6.3.  File a bug with Apple:
<https://bugreport.apple.com>

-- 
________
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] i386 compiling on OSX Snow Leopard

[Sean McBride]

On Tue, 27 Apr 2010 10:50:11 -0400, Dan Gregory said:

>I have been trying to compile the google gears library on snow leopard
>and have run into some issues.  Based on other emails from this list and
>the bug report http://www.itk.org/Bug/view.php?id=9466 I thought that
>this line should force 32bit compiling, but it doesn't seem to work.
>
>set(CMAKE_OSX_ARCHITECTURES i386 CACHE STRING "do not build for 64-bit"
FORCE)
>set(ARCH i386)
>
>This does not pass "-arch i386" to the gcc options.
>
>$ cmake --version
>cmake version 2.6-patch 4
>
>The bug has been closed for awhile so I assume that I have just done
>something wrong... can anyone push me in the right direction?

Use CMake 2.8.1.

-- 
____
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 after upgrading to OSX 10.6.3!

[Sean McBride]

On Wed, 31 Mar 2010 14:03:53 -0400, Bradley Lowekamp said:

>The down arrow (and other arrow keys) is no longer working after I
>patched to OSX 10.6.3 with ccmake. This is very weird! Other
>applications seems fine.

I've been running betas of both 2.8 and 10.6.3 for months and noticed
this behaviour too.  I'm afraid I reported it neither to Apple nor
Kitware. :(  I just switched to the CMake.app instead.

-- 
________
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] find_library and mac os x SDKs

[Sean McBride]

On Sat, 27 Mar 2010 11:53:46 -0400, Simmons, Aaron said:

>> It is a common misconception that one needs to use the 10.4 SDK to
>> create an executable that is compatible with 10.4.  This is not so.
>
>In most cases, you're right.

Yes, I should have clarified that there are exceptions, and it looks
like you've found one.

You might try asking on Apple's xcode-dev list to see if there is a way
to make your stuff work with newer SDKs.  As you've noticed, the 10.4
SDK is now an optional install, and will very likely be gone by OS X 10.7.


On Sat, 27 Mar 2010 17:54:46 +0100, Michael Wild said:

>(and
>also specify -mmacosx-version-min=10.4 in all CMAKE__FLAGS variables).

Note that CMake 2.8 now has CMAKE_OSX_DEPLOYMENT_TARGET, so you don't
need to do it that way anymore.

-- 
____
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] find_library and mac os x SDKs

[Sean McBride]

On Fri, 26 Mar 2010 14:38:54 -0400, Simmons, Aaron said:

>While it will compile, the resulting binary needs to be compatible with 10.4.

It is a common misconception that one needs to use the 10.4 SDK to
create an executable that is compatible with 10.4.  This is not so.

What you want to do is set CMAKE_OSX_DEPLOYMENT_TARGET to 10.4.  Don't
set CMAKE_OSX_SYSROOT at all.  Also, if you're deploying to 10.4, I
believe you need to use gcc 4.0, not newer.  You'll also want to set
CMAKE_OSX_ARCHITECTURES as desired. 

-- 
________
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] find_library and mac os x SDKs

[Sean McBride]

On Fri, 26 Mar 2010 14:08:04 -0400, Simmons, Aaron said:

>When compiled on Mac OS X, my project links against the 10.4 SDK.  This
>SDK is often not installed by default on newer systems (10.6, for
>example).  I would like to put in a check for whether the SDK is present
>before compiling (otherwise the developer gets all kinds of hard-to-
>understand compile errors).

Is there some reason you must use the 10.4 SDK?  Does your code not
compile against new SDKs?

-- 
________
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 in Darwin CMAKE_SYSTEM_PROCESSOR

[Sean McBride]

On 2/23/10 10:10 AM, Luis Kornblueh said:

>for me it looks like a small bug in determining the processor type
>in Darwin (MacOSX):
>
>uname -m returns always i386 despite of the processor used

No, it can also return ppc or arm, depending.

>uname -p returns on a laptop (Core2duo) running 10.5.x i386
>   (32bit kernel)
>
>uname -p returns on a MacPro (Nehalem)  running 10.6.x x86_64
>   (64bit kernel)
>
>It seems that cmake_system_processor is using for Darwin uname -m 
>instead of uname -p.
>
>I checked as well config.guess, which returns the uname -p results
>(more or less ;-) - i686 instead of i386).
>
>I think, it would be nice, to fix this.

There was a large discussion about uname's output some months ago...
here it is:
<http://lists.apple.com/archives/Darwin-dev/2009/Aug/msg00211.html>

As for changing CMake's current behaviour that would all depend
_why_ CMake wants to know the cpu type.  Another technique could be to
use sysctlbyname().  For example:
<http://github.com/tcurdt/feedbackreporter/blob/master/Sources/Main/
FRSystemProfile.m>

-- 

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] parallel builds (ctest_build() ) for dashboards ?

[Sean McBride]

On 12/2/09 10:10 AM, Bill Hoffman said:

>Well, as Dave mentioned the -j flag only works with gmake.  It does not 
>work with Xcode, as you tried here:  :)
>
>
>http://www.cdash.org/CDash/viewNotes.php?buildid=484307
>
>Which is why nothing built for that build. :)

Doh!  I blindly changed all 30 of my scripts, should not have changed
that one obviously.  So in the Xcode case, how does it build?  Does it
invoke xcodebuild?  If so, that will already use many cores, so that's great.

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] parallel builds (ctest_build() ) for dashboards ?

[Sean McBride]

On 12/1/09 12:30 PM, Bill Hoffman said:

>> Is that better/worse/equivalent to David's suggestion of:
>> 
>> set(CTEST_BUILD_FLAGS -j4)  ?
>> 
>
>Worse most likely. :)
>
>Both should work.

Thanks.  If our dashboards are all red tomorrow, you'll know why. :)

-- 
________
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.8rc2 and "CHECK_TYPE_SIZE found different results" error

[Sean McBride]

Hi all,

I've just tried building VTK with 2.8rc1 and it gives an error:

-- Check size of long
CMake Error at /Applications/CMake 2.8-0.app/Contents/share/cmake-2.8/
Modules/CheckTypeSize.cmake:102 (MESSAGE):
  CHECK_TYPE_SIZE found different results, consider setting
  CMAKE_OSX_ARCHITECTURES or CMAKE_TRY_COMPILE_OSX_ARCHITECTURES to one or no
  architecture !
Call Stack (most recent call first):
  CMake/CMakeBackwardCompatibilityC.cmake:14 (CHECK_TYPE_SIZE)
  CMakeLists.txt:403 (INCLUDE)

I don't recall this happening in earlier versions.

Indeed I have set CMAKE_OSX_ARCHITECTURES to "i386;x86_64" and this
error does go away if I use only one arch.  It is also correct that
'long' has a different size between those 2 architectures. 
Nevertheless, I want/need to build VTK in both architectures.

What is the correct fix here?  I guess it's VTK that needs to change?

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] CMake cvs TOT and Xcode

[Sean McBride]

On 10/2/09 10:40 AM, Bill Hoffman said:

>We did change CMake.  Before we used to hard code the build archs into 
>the file (i386, ppc, etc.).   We now use a variable that Xcode uses, 
>something like $(DEFAULT_ARCH) different name, but you get the idea. If 
>that is not defined for some reason for this version of Xcode we can fix 
>it.  CMake knows what version it is building for.  We did have this same 
>problem with Xcode 1.5 and did a fix.   So, since this is most likely a 
>regression, I would like to fix it.   However, I don't have access to 
>Xcode 3.0 so it is hard to fix... :)

Xcode 3.0 is free to download, though you do need a (free) ADC account:
https://connect.apple.com

You can also have multiple versions of Xcode installed simultaneously,
so you could have 3.0 and 3.1.4 installed.  (I'm not sure how well CMake
itself would deal with this though.)

And the Xcode release notes have a detailed account of what changed when:
<http://developer.apple.com/mac/library/releasenotes/DeveloperTools/RN-
Xcode/index.html>

I bet if you searched it for 'something like $(DEFAULT_ARCH)' you'd find
when that was added (probably 3.1). 

-- 
________
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 cvs TOT and Xcode

[Sean McBride]

On 10/1/09 11:17 PM, James Bigler said:

>Well, it worked just fine with CMake 2.4.6, so wouldn't this be a  
>regression?

I guess.  Or possibly you were lucky it ever worked (as in, relying on
undefined behaviour that changed).  I have no idea. :)

I just found it a little odd that you would be using a days-old CMake
and an Xcode released in October 2007.  Xcode 3.1.4 was released just a
few weeks ago.

>The reason I haven't upgraded Xcode is that the updater never  
>presented it, and I don't really check for updates.

It's never included in the Software Update mechanism (for whatever reason).

-- 
________
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 cvs TOT and Xcode

[Sean McBride]

James,

I'm curious why you're using Xcode 3.0 on 10.5.8.  Why not use Xcode
3.1.4?  Perhaps it's actually Xcode's fault and the bug is already fixed.


On 10/1/09 4:37 PM, James Bigler said:

>So was anyone else able to reproduce this issue?
>
>James
>
>On Tue, Sep 29, 2009 at 10:07 AM, James Bigler  wrote:
>> On Tue, Sep 29, 2009 at 9:40 AM, Bill Hoffman 
>> wrote:
>>>
>>> James Bigler wrote:
>>>>
>>>> Silly me.  That wasn't a very helpful bug report.
>>>>
>>>> I updated CMake from CVS last night at approximately 9 PM MDT.
>>>>
>>>> I have XCode 3.0 installed.
>>>>
>>>> OSX is version 10.5.8.
>>>>
>>>> I also just verified that I have the same problem with CMake 2.8 RC 1.
>>>>
>>>> James
>>>>
>>>> On Tue, Sep 29, 2009 at 5:04 AM, David Cole >>> <mailto:david.c...@kitware.com>> wrote:
>>>>
>>>>    Which TOT is the one you mean?
>>>>    http://acronyms.thefreedictionary.com/TOT
>>>>
>>>>    What day did you update CMake from CVS?
>>>>    What Xcode version?
>>>>    What Mac OSX version?
>>>>
>>> Still don't know what TOT is??
>>>
>>> Also, are you building for more than one architecture?
>>>
>>> Can you do cmake --debug-trycompile and then run make VERBOSE=1 in the
>>> CMakeFiles/CMakeTmp directory that is being used by the ABI check?
>>>
>>> -Bill
>>
>> Sorry, TOT == Top of Tree.
>>
>> I used --debug-trycompile and when I went into CMakeFiles/CMakeTmp there
>> wasn't a makefile (Xcode generator), but there was an
>> CMAKE_TRY_COMPILE.xcodeproj.  I opened that up and hit "Build" and it
seemed
>> to build without errors, but I d on't see the actual executable
>> cmTryCompileExec that was supposedly generated.
>>
>> I'm not trying to build with more than one architecture.  I sent my command
>> line earlier:
>>
>> CMakeLists.txt:
>> cmake_minimum_required(VERSION 2.6)
>> project(my_include_directories)
>>
>> $ /code/cmake-cvs/install/bin/cmake ../ -G Xcode
>> $ /Applications/Code/CMake\ 2.8-0.app/Contents/bin/cmake ../ -G Xcode
>> --debug-trycompile

-- 

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