View source for Hugin Compiling OSX

== Compiling Hugin.app on OSX ==

OSX Users: Do you wish you could test those snazzy new Hugin features, provide feedback on its development, or contribute patches to make it a better tool?  Here are the steps necessary to compile your very own Hugin.app direct from the latest sources:

# Get and install the build system CMake, version 2.4.7 or later, from [http://www.cmake.org/HTML/Download.html CMake].
# If you don't have it already, install MacPorts, which provides the <tt>port</tt> command, from [http://macports.org MacPorts], giving you compilable package access to thousands of pieces of open source software.  If you already have macports (formerly darwinports) installed, update it:  <blockquote>% sudo port selfupdate</blockquote>Make sure you have synced the latest port files:<blockquote>% sudo port -d sync</blockquote>
# Don't forget to add <tt>/opt/local/bin</tt> to your path (e.g. <tt>export PATH=/opt/local/bin:$PATH</tt>).
# Use port to install the necessary libraries and commands for Hugin:<blockquote>% sudo port install boost tiff jpeg libpng wxWidgets26 subversion openexr</blockquote>Wait as all of these things are downloaded and compiled, and placed into /opt/local.  Go get a frappe, walk the dog, and total the first 1000 prime numbers in binary.  Rinse, lather, repeat as necessary.  
# Download and build libpano13 from [http://sourceforge.net/project/showfiles.php?group_id=96188&package_id=237430 SourceForge]. Alternatively, use SVN to checkout a fresh copy of libpano13 ([http://sourceforge.net/svn/?group_id=96188 Instructions]).  Build and install it (configure might need to be used with "$ ./configure --with-jpeg=/opt/local/ --with-tiff=/opt/local/", by default it will go into <tt>/usr/local/lib</tt>).
# Check out the hugin sources from SVN, like:<blockquote>% svn co https://hugin.svn.sourceforge.net/svnroot/hugin/hugin/trunk hugin</blockquote>
# Create another directory alongside the newly created <tt>hugin/</tt> for the build files (a cool feature of CMake: it doesn't need to pollute your source directory with build files!):<blockquote>% mkdir hugin_build; cd hugin_build</blockquote>
# Configure hugin using cmake from inside the build directory:<blockquote>% cmake ../hugin</blockquote>
# Fix up a (hopefully temporary) issue with Macport's threaded Boost library not providing generic link names for <tt>libboost_thread</tt>:<blockquote>% cd /opt/local/lib<br>% sudo ln -s libboost_thread-mt.a libboost_thread.a <br>% sudo ln -s libboost_thread-mt.dylib libboost_thread.dylib<br>% cd -</blockquote>
# Compile hugin and friends:<blockquote>% make</blockquote>Watch the pretty colors go by.  Give the dog another quick spin around the block; you're finished.  Look for the new bundle <tt>src/hugin/Hugin.app</tt>.  Copy it to <tt>/Applications</tt>, or your preferred location, and commence testing.

'''Note: This is a new build configuration and you may encounter problems.  Report them on [http://groups.google.com/group/hugin-ptx the Hugin mailing list].'''

== Important Note on the produced Bundle ==

Since the produced Hugin.app bundle links dynamically to libraries outside of the bundle, it is not yet portable, i.e. cannot be copied or shared unless the other machine has the same collection of libraries available in the same places.  This is to facilitate development and testing (re-compile external libraries and test without re-building).  Building a fully portable universal binary version at the command line is planned.

== Notes on wxWidgets ==

wxWidgets, the GUI toolkit currently employed by Hugin, is currently at version 2.8.4.  You can try either this version or the older version 2.6.4.  Switching to the latest version is easy:<blockquote>% sudo port deactivate wxWidgets26; sudo port install wxWidgets</blockquote> and recompile by typing <tt>cmake ../hugin; make</tt> in your build directory.  Switching back is as easy as:<blockquote>% sudo port deactivate wxWidgets; sudo port activate wxWidgets26</blockquote>

[[User:Jdsmith|Jdsmith]] 23:47, 4 August 2007 (CEST)

== Building Enblend ==

Some functionalities of the latest hugin require the latest enblend. Daniel M. German posted compiling instructions for OSX 10.4. Please report successes or errors when building enblend to the hugin-ptx mailing list.

It is rather straightforward. It assumes that you use fink unstable
under 10.4 (it problably works also under 10.5):

1. install lcms

<blockquote><pre>% fink install lcms</pre></blockquote>

2. modify /sw/include/lcms.h

Change:

<blockquote><pre>#if !defined(__INTEGRITY)
#include <memory.h>
#endif</pre></blockquote>

To:

<blockquote><pre>#if !defined(__INTEGRITY)
#include </usr/include/memory.h>
#endif</pre></blockquote>

3. Using fink build enblend

<blockquote><pre>% fink build enblend</pre></blockquote>

This will build enblend 3.0. It will also make sure you satisfy all the dependencies for the latest version of enblend. Don't worry, it won't install it.

4. Install

<blockquote><pre>% fink install openexr openexr-devel</pre></blockquote>

5. Download enblend from cvs,

<blockquote><pre>% cvs -d:pserver:anonymous@enblend.cvs.sourceforge.net:/cvsroot/enblend login
% cvs -z3 -d:pserver:anonymous@enblend.cvs.sourceforge.net:/cvsroot/enblend co -P enblend
% cd enblend</pre></blockquote>

6. Build and install enblend

<blockquote><pre>% make -f Makefile.cvs
% ./configure --prefix=/usr/local
% make
% make install 
</pre></blockquote>


[[Category:Software:Hugin]] [[Category:Software:Platform:Mac OS X]]