Jump to navigation Jump to search
* When Octave is running, clicking on Octave's icon in the dock has no effect. This is because the App bundle runs a shell script which launches which runs Octave. To locate the Octave session, click on the
* Only one instance of the App may be run by clicking on the app. Multiple instances may be run from the command line.
* In some instances, the Octave binary attempts to load an library whose version number is older than the one it intended to link to (at build time). This will produce an error like to one below. The developer utility, [ dylibbundler], is useful in pointing to and/or bundling dynamic libraries in an App bundle. This utility automates the use of [ {{Codeline|install_name_tool}}]. These errors may linger as the application of this tool requires some experimentation in this case.
<nowiki>dyld: Library not loaded: /opt/local/libiconv.2.dylib</nowiki>
===Fixing "{{Codeline|dyld: Library not loaded}}" Errors===
If an error such as the one below above is encountered; <nowiki>dyld: Library not loaded: /opt/local/libiconv.2.dylib</nowiki>It , it is likely due to the Bundle looking in the original install path rather than in the App bundle for the library. This can be fixed using the developer utility [ {{Codeline|install_name_tool}}].
To point to the correct location for the library, first determine the library's location in the App bundle. In this instance the library's path is {{Codeline|}}. Next open a Terminal session, {{Codeline|cd}} to the Resources directory and repair Octave's binary.


Navigation menu