OS X Compilation (again!)

[Olly Betts]

On Wed, Jan 15, 2014 at 04:03:53PM -0500, David A. Riggs wrote:
> I'm attempting to build Survex 1.2.10 on Mac OS X 10.9.1 (Mavericks)
> using the `buildmacosx.sh` script. I allowed the script to download
> its own tarball of wxWidgets (though I had to switch it to use HTTP
> rather than FTP for the download). I do not have Apple's full XCode
> suite installed, but I do have the XCode command line tools installed.

I think the command line tools should be enough.

> Unfortunately I'm not familiar with C development on this platform, or
> with wx at all, so I'm not very skilled at debugging compilation
> failures. Here's where the build dies:
> 
> In file included from ../src/common/dynlib.cpp:48:
> In file included from ../include/wx/mac/private.h:4:
> ../include/wx/mac/carbon/private.h:1459:9: error: unknown type name
> 'Cursor'; did you mean 'NSCursor'?
> typedef Cursor ClassicCursor;
>         ^~~~~~
>         NSCursor

I've no idea what's going on here I'm afraid.  I know this wx version
built OK not very long ago, but probably not on 10.9 - something must
have changed in OS X or the XCode SDK.

> I would love to get compilation working, preferably with wx 2.9 or
> 3.0

I'd suggest focussing on wx 3.0 at this point, as that's where the
wx development focus is.  We'll need to get it working with wx 3.0
sooner or later, and if wx 2.8 won't build out of the box, now seems a
good time.

If you either update the script to use 3.0 or build against 3.0 from
homebrew, how do things go?

> Any suggestions on the compilation failure? Has anyone successfully
> compiled a recent Survex on OS X Mavericks? Is it perhaps a
> Carbon/Cocoa issue? Build log attached.

I think the list might have stripped it - it's set to remove some
attachments to try to avoid relaying viruses and trojans.  The
interactions between some of the settings in mailman are somewhat
confusing, so I tend to avoid tinkering, but it looks like it should
allow attachments which are text/plain (or a few other "safe" types) and
don't have a "bad" extension (like "exe").  Or perhaps you just forgot
to attach it?

Cheers,
    Olly