Editing Create a MacOS X App Bundle Using MacPorts
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 1: | Line 1: | ||
==Install MacPorts== | ==Install MacPorts== | ||
Line 19: | Line 9: | ||
* MacPorts has good support for Octave. A list of what MacPorts has available for Octave is [http://www.macports.org/ports.php?by=name&substr=octave here]. To install the most recent version of Octave, type {{Codeline|<nowiki>sudo port install octave-devel</nowiki>}} at the Terminal's command line. Octave has many dependencies which will be downloaded and installed prior to Octave. The entire installation process can take a few hours. | * MacPorts has good support for Octave. A list of what MacPorts has available for Octave is [http://www.macports.org/ports.php?by=name&substr=octave here]. To install the most recent version of Octave, type {{Codeline|<nowiki>sudo port install octave-devel</nowiki>}} at the Terminal's command line. Octave has many dependencies which will be downloaded and installed prior to Octave. The entire installation process can take a few hours. | ||
MacPorts has historically been rather good a maintaining their Octave portfiles. However, there are times when the | MacPorts has historically been rather good a maintaining their Octave portfiles. However, there are times when the maintainer fall behind. If the current version of the [http://www.macports.org/ports.php?by=name&substr=octave-devel octave-devel] port isn't current, it will be necessary to produce a local portfile. For the remainder of this page, it is assume a local portfile is being used and that the port name is {{Codeline|<nowiki>octave-local</nowiki>}}. | ||
===Install an Octave Port=== | ===Install an Octave Port=== | ||
MacPorts | For the purpose of creating an App bundle using MacPorts, an Octave port must be installed. A standard MacPorts port or a local port may be used. For a local portfile it is first required that a [http://guide.macports.org/chunked/development.local-repositories.html local portfile repository be created] and the local portfile placed there. | ||
A [[Prototype MacPorts PortFile|prototype portfile]] | MacPorts' Octave port includes the non-GPL [http://glaros.dtc.umn.edu/gkhome/views/metis METIS]. To avoid license violations do not bundle Metis with Octave and then distribute to others. A second motivation to use a local portfile is that the portfiles for the 3.4.x and 3.6.x series did not include all dependencies for the {{Codeline|<nowiki>print</nowiki>}} feature. The missing dependencies are [http://www.macports.org/ports.php?by=name&substr=epstool epstool], [http://www.macports.org/ports.php?by=name&substr=pstoedit pstoedit], and [http://www.macports.org/ports.php?by=name&substr=transfig transfig]. A [[Prototype MacPorts PortFile|prototype portfile]] which does not depend upon METIS and does depend upon epstool, pstoedit, and transfig has been prepared. | ||
After [http://guide.macports.org/chunked/development.local-repositories.html creating a local portfile repository] an Octave portfile may be added to the local repository using the commands below. | |||
<nowiki>mkdir -p ~/ports/math/octave-local | <nowiki>mkdir -p ~/ports/math/octave-local | ||
cp ~/Desktop/portfile ~/ports/math/octave-local</nowiki> | cp ~/Desktop/portfile ~/ports/math/octave-local</nowiki> | ||
This assumes the Octave portfile had been placed on the | This assumes the Octave portfile had been placed on the users Desktop, and that the local portfile repository is located in the users home folder and named {{Codeline|<nowiki>ports</nowiki>}}. After adding the portfile, the local repository must be indexed for MacPorts to recognize it. | ||
<nowiki>cd ~/ports | <nowiki>cd ~/ports | ||
portindex -f</nowiki> | portindex -f</nowiki> | ||
Once indexed the local Octave port may be installed. | Once indexed the local Octave port may be installed. | ||
<nowiki>sudo port install octave-local | <nowiki>sudo port install octave-local +atlas+gcc45</nowiki> | ||
The use of the | The use of the {{Codeline|+atlas}} variant is encouraged as bugs exist for Apple's {{Codeline|accelerate}} framework in both MacOS 10.6 and 10.7. Octave's developers have included a fix for MacOS 10.6, but the fix does not work for MacOS 10.7. There is some commentary on this in various developers discussion forums. For example, see [https://github.com/mxcl/homebrew/issues/6649 this Homebrew thread (Octave 3.4 fails on lion)], [https://stat.ethz.ch/pipermail/r-sig-mac/2011-September/008564.html this R-Sig-Mac thread (R 2.13.1-patched, vecLib problem on Lion)], and [http://list.coin-or.org/pipermail/ipopt/2011-October/002610.html the COIN-OR thread (Ipopt - problems on OS X 10.7 Lion)]. Use of Apple's {{Codeline|accelerate}} framework should also be avoided for {{Codeline|arpack}} and {{Codeline|qrupdate}}. To install the recommended variants, use the {{Codeline|port}} commands below. | ||
<nowiki>port install arpack +atlas+ | <nowiki>port install arpack +atlas+gcc45 | ||
port install qrupdate +atlas+ | port install qrupdate +atlas+gcc45</nowiki> | ||
As a precaution against unexpected problems and a bloated App bundle, using consistent variants for Octave and its dependents is suggested. For example, when using | As a precaution against unexpected problems and a bloated App bundle, using consistent variants for Octave and its dependents is suggested. For example, when using {{Codeline|+atlas}} make sure none of the dependents are using {{Codeline|+accelarate}}. Also, make sure no dependents are using the {{Codeline|+universal}} variant. Using the {{Codeline|+gcc45}} variant is also recommended as all of Octave's dependents have a {{Codeline|+gcc45}} variant. At the very least, following these suggestions will reduce the size of the bundle. The name of Octave's dependent ports may be determined by the command below. | ||
<nowiki>port | <nowiki>port deps octave-local</nowiki> | ||
The installed variants for each port may be determined by the command below. Be sure to replace "<portname>" with the name of the port. | The installed variants for each port may be determined by the command below. Be sure to replace "<portname>" with the name of the port. | ||
Line 47: | Line 39: | ||
<nowiki>port installed <portname></nowiki> | <nowiki>port installed <portname></nowiki> | ||
Once an Octave port is installed the command below may be used to determine / verify the version and variants of < | Once an Octave port is installed the command below may be used to determine / verify the version and variants of {{Codeline|<nowiki>octave-local</nowiki>}} which are installed. | ||
<nowiki>port installed octave-local</nowiki> | <nowiki>port installed octave-local</nowiki> | ||
==Create the MacOS X App Bundle== | ==Create the MacOS X App Bundle== | ||
Line 67: | Line 51: | ||
MacPorts provides a feature for [http://guide.macports.org/index.html#using.binaries.binary-packages producing binary packages] with standalone binary installers that are precompiled; they do not require MacPorts on the target system. Binary files created with MacPorts may be either .pkg (Mac OS X Installer Packages), or RPM (RPM Package Manager) format. MacPorts may also process a .pkg package into a Mac OS X .dmg disk image file. The port command shown below will create a DMG type binary installer for the Octave port and all its dependencies. | MacPorts provides a feature for [http://guide.macports.org/index.html#using.binaries.binary-packages producing binary packages] with standalone binary installers that are precompiled; they do not require MacPorts on the target system. Binary files created with MacPorts may be either .pkg (Mac OS X Installer Packages), or RPM (RPM Package Manager) format. MacPorts may also process a .pkg package into a Mac OS X .dmg disk image file. The port command shown below will create a DMG type binary installer for the Octave port and all its dependencies. | ||
<nowiki>sudo port mdmg octave- | <nowiki>sudo port mdmg octave-local</nowiki> | ||
If more than one version of Octave is installed, or if more than one variant of Octave has been installed, the version and variant should be included. | |||
<nowiki> | <nowiki>sudo port mdmg octave-local @<version>+variant1+variant2</nowiki> | ||
The DMG will be placed in the port's {{Codeline|<nowiki>work</nowiki>}} directory. If a local portfile is used, a symbolic link to the {{Codeline|<nowiki>work</nowiki>}} directory will be placed in the directory containing the portfile. In this instance the DMG can be found in {{Codeline|<nowiki>~/ports/math/octave-local/work</nowiki>}}. | |||
The DMG produced using the [http://www.octave.org/wiki/index.php?title=Prototype_MacPorts_PortFile prototype portfile's] does not include everything needed for Octave. Both {{Codeline|macros.texi}}, {{Codeline|octave.info}}, and the {{Codeline|octave.info-#}} files are missing. Until the cause for these missing files is identified and resolved, they will have to be copied manually to the App bundle. | |||
The DMG produced using the [http://www.octave.org/wiki/index.php?title=Prototype_MacPorts_PortFile prototype portfile's] does not include everything needed for Octave. Both | |||
===Create an Application Template for Octave=== | ===Create an Application Template for Octave=== | ||
Line 137: | Line 110: | ||
The Octave App bundle for MacOS X is now ready to run. | The Octave App bundle for MacOS X is now ready to run. | ||
==Running Octave from the Terminal's Command Line== | ==Running Octave from the Terminal's Command Line== | ||
Line 296: | Line 256: | ||
List of what can be done to improve the MacOS X App bundle. | List of what can be done to improve the MacOS X App bundle. | ||
* The {{Codeline|macros.texi}} file doesn't install properly. It should be in {{Codeline|share/octave/3.7.0+/etc}}, but doesn't show up. | * The {{Codeline|macros.texi}} file doesn't install properly. It should be in {{Codeline|share/octave/3.7.0+/etc}}, but doesn't show up. | ||
* Test the ability to compile mex-files and oct-files. | * Test the ability to compile mex-files and oct-files. | ||
** Necessary changes | ** Necessary changes | ||
Line 302: | Line 261: | ||
*** Same for octave_confgure-3.7.0+ | *** Same for octave_confgure-3.7.0+ | ||
*** Over-ride the built-in octave_configure_info and use an m-file version that replaces the original MacPorts prefix with the OCTAVE_HOME environment variable set by the bundle. | *** Over-ride the built-in octave_configure_info and use an m-file version that replaces the original MacPorts prefix with the OCTAVE_HOME environment variable set by the bundle. | ||
*** The bundled mkoctfile references the gcc4.4 libraries instead of the gcc4. | *** The bundled mkoctfile references the gcc4.4 libraries instead of the gcc4.5 libraries that are actually bundled. This needs to be corrected. | ||
** With the above changes [http://www.gnu.org/software/octave/doc/interpreter/Getting-Started-with-Oct_002dFiles.html {{Codeline|mkoctfile helloworld.cc}}] fails with the error below. This is likely due to the {{Codeline|Octave-3.7.0+.app/Contents/Resources/bin/octave}} script over-riding the build environment variables normally set by {{Codeline|mkoctfile}}. | ** With the above changes [http://www.gnu.org/software/octave/doc/interpreter/Getting-Started-with-Oct_002dFiles.html {{Codeline|mkoctfile helloworld.cc}}] fails with the error below. This is likely due to the {{Codeline|Octave-3.7.0+.app/Contents/Resources/bin/octave}} script over-riding the build environment variables normally set by {{Codeline|mkoctfile}}. | ||
*** Rely on {{Codeline|mkoctfile}} to setup the oct-file build environment (i.e. don't set any of it up in the {{Codeline|.../Octave-3.7.0+.app/Contents/Resources/bin/octave}} script. | *** Rely on {{Codeline|mkoctfile}} to setup the oct-file build environment (i.e. don't set any of it up in the {{Codeline|.../Octave-3.7.0+.app/Contents/Resources/bin/octave}} script. | ||
Line 311: | Line 270: | ||
collect2: ld returned 1 exit status | collect2: ld returned 1 exit status | ||
"/Applications/Octave-3.7.0+.app/Contents/Resources/bin/g++-mp-4. | "/Applications/Octave-3.7.0+.app/Contents/Resources/bin/g++-mp-4.5" \ | ||
-c -I"/Applications/Octave-3.7.0+.app/Contents/Resources/include/curl" \ | -c -I"/Applications/Octave-3.7.0+.app/Contents/Resources/include/curl" \ | ||
-I"/Applications/Octave-3.7.0+.app/Contents/Resources/include/readline" -fPIC \ | -I"/Applications/Octave-3.7.0+.app/Contents/Resources/include/readline" -fPIC \ | ||
Line 321: | Line 280: | ||
helloworld.cc -o helloworld.o | helloworld.cc -o helloworld.o | ||
"/Applications/Octave-3.7.0+.app/Contents/Resources/bin/g++-mp-4. | "/Applications/Octave-3.7.0+.app/Contents/Resources/bin/g++-mp-4.5" -bundle -bundle_loader \ | ||
"/Applications/Octave-3.7.0+.app/Contents/Resources/bin/octave-3.7.0+" -o helloworld.oct helloworld.o \ | "/Applications/Octave-3.7.0+.app/Contents/Resources/bin/octave-3.7.0+" -o helloworld.oct helloworld.o \ | ||
-L"/Applications/Octave-3.7.0+.app/Contents/Resources/lib/octave/3.7.0+" \ | -L"/Applications/Octave-3.7.0+.app/Contents/Resources/lib/octave/3.7.0+" \ | ||
-L"/Applications/Octave-3.7.0+.app/Contents/Resources/lib" -loctinterp -loctave -lcruft \ | -L"/Applications/Octave-3.7.0+.app/Contents/Resources/lib" -loctinterp -loctave -lcruft \ | ||
"/Applications/Octave-3.7.0+.app/Contents/Resources/lib/ | "/Applications/Octave-3.7.0+.app/Contents/Resources/lib/gcc45/libstdc++.6.dylib"</nowiki> | ||
* Should the contents of the la-files, in {{Codeline|Octave-3.7.0+.app/Resources/lib}}, be changed to reflect to use the {{Codeline|@executable_path}} token. | * Should the contents of the la-files, in {{Codeline|Octave-3.7.0+.app/Resources/lib}}, be changed to reflect to use the {{Codeline|@executable_path}} token. | ||
** These files are from libtool. For limited development, such as building oct-files and mex-files, are they needed at all? | ** These files are from libtool. For limited development, such as building oct-files and mex-files, are they needed at all? | ||
Line 331: | Line 290: | ||
** This will allow for a fully automatic build of an App bundle from a shell script. | ** This will allow for a fully automatic build of an App bundle from a shell script. | ||
* Also use an AppleScript to record the creation of a MacOS X Octave icon. | * Also use an AppleScript to record the creation of a MacOS X Octave icon. | ||
[[Category:Mac]] | |||
[[Category: |