Re: Compiling octave-workshop

[John W. Eaton]

On  1-Mar-2006, Sebastien Loisel wrote:

| 1) Originally, I was using qmake. Qmake adds compile and link options to the
| command line which did not work if I hand-edited the Makefile to use
| mkoctfile for its C++ compiler.
| 2) I don't know how to pass certain options down to g++ at compile time. For
| instance, -fexceptions.
| 
| mkoctfile is good for small projects, but serious projects will sooner or
| later want to get around it.

OK, then I suggest that instead of doing things like parsing the
output of -v (which is fragile, as the output from -v could change in
the future and break your parser), you modify mkoctfile or
octave-config to do what you need and submit the changes.

Doing things like parsing verbose output from a compiler is a bit of a
kluge.  It makes sense if you have no way to change the compiler to
provide the information you need.  But with Octave, you have the
sources and can make them do what you want.

jwe