Build a MacOSX Universal Hugin bundle with Xcode - Revision history

Zarl: /* External Links */ Spam

2010-10-29T05:53:33Z

‎External Links: Spam

Furai: small typo

2010-10-18T08:27:08Z

small typo

MergeMac: /* External Links */

2010-09-29T14:52:21Z

‎External Links

Aks: /* Build the "External Programs" */

2010-06-29T04:00:48Z

‎Build the "External Programs"

Aks: /* Fink */

2010-06-29T02:59:06Z

‎Fink

Aks: /* Fink */

2010-06-29T02:48:53Z

‎Fink

Harryvanderwolf: /* Fink */

2010-05-21T07:20:41Z

‎Fink

Harryvanderwolf: /* MacPorts */

2010-05-21T07:20:27Z

‎MacPorts

Harryvanderwolf: /* Get Hugin from the Mercurial repository */

2010-05-21T07:19:08Z

‎Get Hugin from the Mercurial repository

Harryvanderwolf: /* 32bit versus 64bit */

2010-05-20T17:20:27Z

‎32bit versus 64bit

@@ Line 352: / Line 352: @@
 - What is [http://en.wikipedia.org/wiki/Endianness endianness].<br />
 - MacPorts set endianness [http://guide.macports.org/#reference.variables read-only] for the platform it's installed on.<br />
 - MacOSX online [http://www.hmug.org/man/ Darwin man pages] from the HMUG user group.<br />
 - [http://developer.apple.com/documentation/DeveloperTools/Conceptual/cross_development/index.html Cross-Development Programming Guide] and [http://developer.apple.com/documentation/MacOSX/Conceptual/universal_binary/index.html Universal Binary Programming Guidelines, Second Edition]– more about building fully compatible universal binaries on OS X
 [[Category:Software:Hugin]] [[Category:Software:Platform:Mac OS X]]

@@ Line 343: / Line 343: @@
 # Make a new folder next to <tt>mac/</tt> and name it "<tt>mac-static</tt>".
 # Copy BuildConfig.xcconfig, Version.xcconfig, and Hugin.xcodeproj files to the new folder.
-# Make a new folder in tt>mac-static/</tt> named "<tt>ExternalPrograms</tt>".
+# Make a new folder in <tt>mac-static/</tt> named "<tt>ExternalPrograms</tt>".
 # Either make the static repository here, or place a symbolic link named "repository" to the outside one.
 # Edit BuildConfig.xcconfig and update the REPOSITORY_ABSOLUTE_PATH variable.

@@ Line 352: / Line 352: @@
 - What is [http://en.wikipedia.org/wiki/Endianness endianness].<br />
 - MacPorts set endianness [http://guide.macports.org/#reference.variables read-only] for the platform it's installed on.<br />
 - MacOSX online [http://www.hmug.org/man/ Darwin man pages] from the HMUG user group.<br />
 - [http://developer.apple.com/documentation/DeveloperTools/Conceptual/cross_development/index.html Cross-Development Programming Guide] and [http://developer.apple.com/documentation/MacOSX/Conceptual/universal_binary/index.html Universal Binary Programming Guidelines, Second Edition]– more about building fully compatible universal binaries on OS X
 [[Category:Software:Hugin]] [[Category:Software:Platform:Mac OS X]]

@@ Line 156: / Line 156: @@
 <blockquote><pre>$ bash</pre></blockquote>
 * Download the necessary source packages (Google for them, copy them from your MacPorts and/or Fink base if available). The readme.txt in the ExternalPrograms directory lists the ones you need.
-However, it's also a good idea to look at the corresponding script to verify the version number, as the scripts tend to be updated more often then the documentation. For example: The readme.txt might list Boost (1.39) when in fact the boost.sh script might have a line BOOST_VER="1_40" that causes the script to look for boost related file names with 1_40 instead of 1_39. Therefore you should be downloading boost version 1.40. As a general rule, check the scripts if you see that there is a more recent version available than what is listed in the readme.txt file.
+However, it's also a good idea to look at the corresponding script to verify the version number, as the scripts tend to be updated more often then the documentation. For example: The readme.txt might list Boost (1.39) when in fact the boost.sh script might have a line BOOST_VER="1_40" that causes the script to look for boost related file names with 1_40 instead of 1_39. Therefore you should be downloading boost version 1.40. As a general rule, check the scripts if you see if they indicate a more recent version to use than what is listed in the readme.txt file. The opposite is now true. The readme.txt currently (6/26/10) lists boost version 1.41.
 * untar/unbzip2 the source packages. It's best to do this in the ExternalPrograms directory so that you will have all kind of subdirectories containing the source, like jpeg-6b, tiff-3.8.2, enblend, wxMac-2.8.7 and so on. Perhaps the easiest way to unpack the sources is to double click on the source packages in a Finder window. They can also be unpacked within the Terminal window:
@@ Line 184: / Line 188: @@
 </pre></blockquote>
-* A recent addition to the project is a script named build-all.sh. This script has all the commands needed to build all of the tools. This script is recommended. Edit the script prior to using it to make sure it points to the correct external source folder names that you are using. This script writes a "<<<< building xxxxxxx >>>>>" line prior to starting each package build script.  If you use Terminal, when this script is running or after the script has finished you can search (Edit Find) for the text "< building". This takes you to the beginning of each build process where you can see any errors that have occurred at the end of the prior build script or see any errors at the start of the next build. These are the most likely spots where you can see something has gone wrong. You can keep a second copy of build-all.sh, renamed to build-user.sh, where you comment out all but the one package you may need to rebuild. So if a package does not build for some error like the version number is wrong, and you spot it soon enough, you can start a second Terminal session and run the specific build-user.sh for that package while the other build-all is still running on the other packages.
+* A recent addition to the project is a script named build-all.sh. This script has all the commands needed to build all of the tools. '''This script is highly recommended.''' Edit the script prior to using it to make sure it points to the correct external source folder names that you are using and to make sure it points to the scripts folder. Spiderman would edit the cd line in his version of build-all.sh to be: cd /Users/Spiderman/development/hugin/mac/ExternalPrograms/scripts
 * After building all the tools, you need to download the Perl module Image-ExifTool-7.96 (source version), and extract the archive in the ExternalTools directory. Nothing else needs to be done for this program.

@@ Line 47: / Line 47: @@
 </pre></blockquote>
 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.
 ===Get Hugin from the Mercurial repository===

@@ Line 44: / Line 44: @@
 If you use Fink:
 <blockquote><pre>
-$ sudo apt-get install svn gettext mercurial
+$ sudo apt-get install svn gettext mercurial-py25
 </pre></blockquote>
 ===Get Hugin from the Mercurial repository===

@@ Line 38: / Line 38: @@
 You first need to [[Hugin_Compiling_OSX#Install_Macports | Install Macports]] (if you did not already do so) as described in [[Hugin_Compiling_OSX | Hugin Compiling OSX]]. Then you need to install:
 <blockquote><pre>
-$ sudo port install subversion gettext
+$ sudo port install subversion gettext mercurial
 </pre></blockquote>

@@ Line 56: / Line 56: @@
 $ hg clone http://hugin.hg.sourceforge.net:8000/hgroot/hugin/hugin hugin</pre></blockquote>
 Inside <tt>/Users/<your_username>/development</tt>, you will now have a directory <tt>hugin</tt>. The full path to your "External Programs" development tree will be <tt>/Users/<your_username>/development/hugin/mac/ExternalPrograms</tt>.
 ===Location of the "External Programs" development tree===

@@ Line 295: / Line 295: @@
 ===32bit versus 64bit===
-Tiger (Xcode 2.4) enables you to build universal binaries and libraries for PPC and i386. Leopard and Snow Leopard (XCode 3.x) enable you to build universal binaries for PPC and i386, but also for PPC64 and x86_64. If you want to do this, you should refer to SetEnv-leopard.txt. At this moment this is "''utterly experimental''" as:
+Tiger (Xcode 2.4) enables you to build universal binaries and libraries for PPC and i386. Leopard and Snow Leopard (XCode 3.x) enable you to build universal binaries for PPC and i386, but also for PPC64 and x86_64. If you want to do this, you should refer to SetEnv-leopard.txt. At this moment this is "''experimental''" as:
 :# some "Linux derived" libraries and binaries may not work properly.
 :# they are not well optimized for Core 2 processors.