Create a MacOS X App Bundle Using MacPorts: Difference between revisions

→‎TODO List: Add notes on enabling mkoctfile
(→‎TODO List: Add notes on enabling mkoctfile)
Line 255: Line 255:
*** Made sure -pthreads is included in CPPFLAGS, CXXFLAGS, CFLAGS, FFLAGS, and LDFLAGS, and the error remains.
*** Made sure -pthreads is included in CPPFLAGS, CXXFLAGS, CFLAGS, FFLAGS, and LDFLAGS, and the error remains.
* Test the ability to compile mex-files and oct-files.
* Test the ability to compile mex-files and oct-files.
** Necessary changes
*** Use the environment variable OCTAVE_HOME in mkoctfile to point to the bundled developer tools and libraries.
*** 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.
*** 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 {{Codeline|mkoctfile helloworld.cc}} fails with the error below.  I can't find the source of {{Codeline|-lgcc}} in in either {{Codeline|mkoctfile}}, {{Codeline|octave_configure_info}}, or {{Codeline|octave-config-3.7.0+}}.
<nowiki>ld: library not found for -lgcc
collect2: ld returned 1 exit status</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?
364

edits