2Prerequisites
3Preparations for building the 'External Programs'
- 3.2Installing Necessary Tools
- 3.4Location of the 'External Programs' development tree
- 3.5Creation of the 'External Programs' development tree
4Building the 'External Programs'
5Xcode compiling Hugin
- 5.4Compile and build our Hugin.app
6Notes

Introduction

The latest version of Hugin Lite is 7.5 on Mac Informer. It is a perfect match for IDE in the Developer Tools category. The app is developed by HUGIN EXPERT A/S. Hugin is a third party application that provides additional functionality to OS X system and enjoys a popularity among Mac users. However, instead of installing it by dragging its icon to the Application folder, uninstalling Hugin may need you to do more than a simple drag-and-drop to the Trash. The cmake compilation of Hugin is currently broken due to the fact that the boost library on OS X is currently at version 1.50 and boost versions = 1.48 conflict with a number of Mac OS X macros (from AssertMacros.h). This can not be disabled as WxWindows for Mac (a.k.a. WxMac) needs these macros. RHugin Install Instructions for Mac OS X. Last updated by Kjell Konis on 2017-02-02. The RHugin package provides an R API for the HUGIN Decision Engine (HDE): both the HDE and R must be installed on the computer in order for the RHugin package to function.

The 'normal' way of compiling Hugin is via Cmake. With the current versions of MacPorts, Fink and Cmake it is very difficult to make a universal bundle due to the way endianness is dealt with in MacPorts and Fink. This HowTo explains how to make a universal bundle with Xcode.

The creation of a bundle is actually a two step process:

Hugin For Mac Os High Sierra

Build all libraries and binaries which Hugin depends on. This is done outside Xcode. From here on we will call these libraries and binaries 'External Programs'. To compile and build all 'External Programs' as universal, we will follow a different process compared to the normal 'straight-forward' process of building libraries with MacPorts or Finks as described in Hugin Compiling OSX. We do not need nor use MacPorts and/or Fink. Some may even prefer to put them 'out of the way' in order to make sure we will not link with the libraries they provide. However, they provide convenient ways to install a few of the tools that we require in the later process and they should not be moved out of the way if they are where cmake is installed on your system. Some of the external package build scripts rely on cmake.
Build Hugin and it's 'internal' tools in Xcode and create the bundle. As the title suggests: This is done in Xcode.

Note: This Howto does not explain how to build a Hugin the 'cmake way'. Follow the Howto Hugin Compiling OSX.

Prerequisites

You should have Mac OS X 10.4 or above. Older systems are not recommended and how to build on those systems will not be included in this document.

Download and install XCode

Download and install the latest version of XCode Tools for your Mac OS X: Xcode 2.5.x for Mac OS X 10.4 (Tiger), Xcode 3.1.x for 10.5 (Leopard) and XCode 3.2.x for 10.6 (Snow Leopard). We do not support 10.3.9 any longer. You need to register as a developer to be able to download XCode, but it is free and you will not be bugged by all kind of mails (unless you choose to receive them).

Subversion (SVN)

Leopard comes with SVN installed. The version is way too old though. This means that you need to install it yourself. The simplest way to get SVN is to use MacPorts or Fink.If you are on Tiger, you need to install it anyway. The simplest way to get SVN is to use MacPorts or Fink.

If you fancy a nice GUI you can download the Open-Source SVNX. You still need svn installed as it is only a graphical shell and I won't explain SVNX here (I only used it once, I still prefer the terminal).

You may also find SCPlugin handy for some quick operations.

Preparations for building the 'External Programs'

Introduction

Building the necessary 'External Programs' (the libraries and binaries Hugin depends on) is completely scripted. This part describes not how to use './configure' or 'make; make install'. It will explain (advise) how and where to create the necessary directory structure, configure the base environment script and, more or less, tell you in which order to run the package build scripts.

Installing Necessary Tools

Before start, we need to install couple of tools used in the process:

Subversion
GNU gettext
cmake

You may use either binary distributions like MacPorts and Fink. You can also download the official version and manually compile and install ('./configure; make; sudo make install'). Note though that in that case you need to take yourself of all dependencies.

MacPorts

You first need to Install Macports (if you did not already do so) as described in Hugin Compiling OSX. Then you need to install:

Fink

If you use Fink:

Note: mercurial is in the Fink 'unstable' Source distribution. Set Fink to look for distributions in the unstable list. As of this writing there are three mercurial listings: mercurial-py24, mercurial-py25 and mercurial-py26. Py25 is presumably for python 2.5. The command python -V reports what python version is currently installed.

Start a fresh Terminal session before proceeding to the next steps. Otherwise the hg command may not be recognized.

Get Hugin from the Mercurial repository

For these instructions you need a folder named 'development' residing at /Users/<your_username>. Create this folder in lowercase with the Finder if you do not already have it. This folder starts the path for what is called the development tree herein.

Tip: In subsequent instructions you will be entering folder path names and file names at the Terminal prompt. Instead of manually typing these in you can have Terminal provide the text for you by dragging the folder or filename item from an open Finder window into the Terminal window. When you do this Terminal deposits the name of the folder or filename you are dragging to the location you drop it in Terminal. For example in the following instructions you are to enter 'cd development'. Type in 'cd ' and then drag the development folder into the Terminal window to finish entering the text. You will find this technique is extremely convenient for the more involved path and file names.

Cd into your development tree and download hugin from the Mercurial hg repository like:

Inside /Users/<your_username>/development, you will now have a directory hugin. The full path to your 'External Programs' development tree will be /Users/<your_username>/development/hugin/mac/ExternalPrograms.

On subsequent retrievals from the Mercurial repository you simply cd into the hugin development directory on your mac and you issue the following two commands:

Location of the 'External Programs' development tree

This part describes where we want to place the development tree for our 'External Programs' that hugin depends on. Although the 'External Programs' directory structure is placed inside the Hugin tree by default, this does not necessarily need to be in the same place as the Hugin source itself. The easiest way to place those files in custom places is to put symbolic link in the default place.

The first question is: where do you want to have your development tree? As you (might) know, the 'normal' location is /usr/local, and MacPorts uses /opt/local by default and Fink, /sw. We do not want to use these locations!

Apart from the fact that it is a bad idea to mix up development trees, another drawback is that these directories are not in 'user space', therefore always requiring a root authorization, e.g. 'sudo make install' as a last step. When keeping the development tree in user space (e.g. /Users/<your_username>/development/ or /Users/Shared/development/), you don't need to 'sudo'. Note that the latter option also creates a development directory but keeps it away from your 'normal' user data.

So, from this moment 'we' have decided to build our development tree in user space.

Note: As mentioned before: If you p