Changes

Line 65: Line 65:  
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-local</nowiki>
+
  <nowiki>sudo port mdmg octave-devel @3.6.4+atlas+fltk+gcc47-x11+no_x11-metis+llvm32+ssl+qt</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>sudo port mdmg octave-local @<version>+variant1+variant2</nowiki>
      
In the event errors such as the one below are encountered, the ports implicated ({{Codeline|<nowiki>t1lib</nowiki>}} in this case) must be clean prior to creating the dmg.
 
In the event errors such as the one below are encountered, the ports implicated ({{Codeline|<nowiki>t1lib</nowiki>}} in this case) must be clean prior to creating the dmg.
364

edits