issues with el Captain

Dirk Hohndel dirk at
Sun Nov 15 10:07:43 PST 2015

> On Nov 15, 2015, at 10:02 AM, Tomaz Canabrava <tcanabrava at> wrote:
> (wich is a pretty good name for a OS that runs subsurface, btw. )

Except that that's the name of a mountain...

> I started trying to make subsurface compile for iOS a few weekends ago, but having just a little time per day for subsurface this wasn`t really working.
> Today I had managed to make subsurface run on El Captain, my steps:
> 1 - Nuke the old build directory for every external library that I used (grantlee, marble, libdivecomputer)

That seems to be a good idea whenever things get odd. Even after upgrading the compiler I sometimes need to do that.

> 2 - Installed some new dependencies: libhid, libgcrypt, homebrew/versions/libpqxx3 via brew

I don't think I build libgcrypt or libdbqxx3 for my builds on 10.7...

> 3 - fixed my PATH (for some reason, my qt install wasn`t on my $PATH anymore after my update to El Captain)

Yes, Apple loves messing with user settings. It's because they know better than you what you want in your path. And they care!

> 4 - Copied by hand QtXml.frameworks to the app bundle (for some reason, marble required it but it wasn`t being copied by macdeployqt)

Yeah, look at packaging/maxosx/ -- while that is clearly custom built for my environment to create our actual packages, it does show you some of the things that I needed to do to make it all work, and that includes copying QtXml.framework

> Now, continuing to the iOS stuff...


More information about the subsurface mailing list