On Aug 20, 2011, at 1:30 PM, Ben Abbott wrote:
I've just switched to MacOS 10.7 (Lion) and in the process have switched from Fink to Macports for my package management, and would like to be able build Octave for development purposes.
I'm able to use the developer's sources to create a tarball and using a local port am able to build and install Octave using macports. This isn't a good solution for active development, but it does indicate that Octave can be built using macports for all dependencies.
Unfortunately, I'm unable to build octave in my local mercurial active. Before I begin the process of debugging my build process, I thought I'd check if anyone is already doing this.
Is anyone doing octave development using macports for the dependencies? If so, what options (script?) are used for the configure process?
Ben
I've made some good progress in the last few days.
I'm now able to build from the developers sources. In addition to the dependencies required by the octave-devel port, I recommend including transfig, epstool, and pstoedit. These will allow the print() command to be fully functional.
To build the sources, place the attached script (macports_configure.sh) in directory above the archive, and ...
./autogen.sh
./macports_configure.sh
make
The macports_configure.sh scripts was mostly generated automatically by parsing the output of octave_config_info(). Thus, I expect there is a lot of info there that is not needed.
The resulting binary should include all features for MacOS < 10.7. For MacOS 10.7, the FLTK libs will not be linked to since they rely on the carbon framework which encounters the problem reported for MacOS 10.7 at the link below.
A discussion of the same problem by developers of OpenSceneGraph is at the link below.
My impression is that the sources need to be modified. However, it isn't clear to me if the change needs to be made on the autotools side or on the c++ side. Advice or assistance would be appreciated.
Ben