building on a Mac

[Dirk Hohndel]

On Mon, Aug 17, 2015 at 10:35:26AM +0200, Guido Lerch wrote:
> Hi Dirk,
> 
> Thanks for all your efforts.
> I though it might be useful to protocol on how I uninstalled what you listed below.
> 
> What is kind of frustrating is that when removing QT with the maintenance tool, which is what they recommend, certain traces in the /usr/local/ folder remain
> from which a normal user would not know what can be deleted vs. what not.
> 
> For example: /usr/local/lib contains
> /cmake/ : assume can be removed
> libosxfuse_xxx
> tons of libQT5xxxx and QTxxx  stuff
> /pkgconfig/ : can go
> 
> /usr/local/libexec contains QTWebProcess
> 
> /use/local/qml contains lots of QTxxxx stuff
>  
> There is more and I am not 100% sure what to remove and what not, if I keep it there, would that have any negative impact ?

The cmake stuff might get in the way... depending what else you have
installed on that system these should all be leftovers from trying to get
Subsurface to install.

I'd suggest that you run

rm -rf /usr/local/lib/cmake /usr/local/lib/pkgconfig /usr/local/qml /usr/local/lib/*Qt*

> Uninstalling:
> 
> 1. ) ran
> ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/uninstall)"
> to uninstall brew
> 
> 2.) ran maintenance tool to “remove” QT
> 
> 3.) removed the entire ~/src folder and recreated it

Combined with what I wrote above That should be sufficient.

> I’ll wait for feedback till I continue with the installation

Please try the steps below (or in the INSTALL file)

/D

> On 17 Aug 2015, at 04:12, Dirk Hohndel <dirk at hohndel.org> wrote:
> 
> > So I've spent some time today with Guido on the challenges of building Subsurface on a Mac from scratch. And to call the experience for him a disaster would be putting it way too kindly.
> > 
> > I pushed a few changes that I hope will make this better but this will require some more testing. 
> > 
> > If you have a Mac and would like to help, the steps to do this are a bit drastic because we need to make sure we have a somewhat consistent starting point, but based on my attempts in a fresh OS X 10.10 VM I think this should work.
> > 
> > So Guido, here is what I think you (and anyone else who wants to play along) will have to do.
> > 
> > a) remove Qt 5 - regardless where it came from: official installer, built from source, installed via MacPorts or Homebrew or whatever 
> > b) uninstall Homebrew and all packages you have installed via Homebrew
> > c) remove the Subsurface-created folders under ~/src
> > 
> > OK, now you have a pretty clean and reproducible environment.
> > 
> > cd ~/src
> > git clone git://subsurface-divelog.org/subsurface
> > 
> > now read the instructions in subsurface/INSTALL - or simply follow along here:
> > 
> > 
> > 1)  Install Homebrew
> > 
> > $ ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"
> > 
> > 2) Install needed dependencies
> > 
> > $ brew install asciidoc libzip sqlite cmake libusb pkg-config automake libtool
> > 
> > 3) Make the brew version of sqlite the default
> > 
> > $ brew link --force sqlite
> > 
> > 4) Download and install Qt
> > 
> > Download the online installer:
> > 
> > $ curl -L -o ~/Downloads/qt-unified-mac-x64-online.dmg \
> >         http://download.qt.io/official_releases/online_installers/qt-unified-mac-x64-online.dmg
> > $ open ~/Downloads/qt-unified-mac-x64-online.dmg
> > 
> > Double click on the Qt installer shown in the Finder window.
> > In the installer, use the default install folder /home/<your username>/Qt)
> > To save time and disk space you can unselect Android and IOS packages
> > as well as QtWebEngine, Qt3D, Qt Canvas 3D and the Qt Extras.
> > 
> > 5) run the build script
> > 
> > $ cd ~/src
> > $ bash subsurface/scripts/build.sh
> > 
> > After the above is done, Subsurface.app will be available in the
> > subsurface/build directory. You can run Subsurface with the command
> > 
> > $ open subsurface/build/Subsurface.app
> > 
> > 
> > I'm foolishly optimistic that this will work. And I would like people to try this so we can see where it breaks and fix those missing pieces.
> > 
> > Thanks
> > 
> > /D
>