use of mkoctfile with autoconf/automake

[John W. Eaton]

On  1-Mar-2007, Eric Chassande-Mottin wrote:

| I'd like to compile a set of DLD codes with automake/autoconf.
| i am trying to understand what octave-forge does.  from
| configure.base, i see that the idea is to "recompose" the compilation
| instructions of mkoctfile. am i right?
| the compiler, options and libs are retrieved from a call "mkoctfile
| -p" for instance :
| 
|   163 CC=`$MKOCTFILE -p CC`
|   [...]
|   169 AC_SUBST(CC)
|   [...]

I'm not sure why Octave Forge works this way.

Why not just use mkoctfile as a compiler?  It can compile only (use -c
to create only object files) and link objects into a shared/dynamic
library (.oct file).

| second question: I am not able to find the Makefile.ams (there are only
| Makefile.in). why is that?

Because the project uses autoconf but not automake?

jwe