octave-config -p OCTINCLUDEDIR changed?

[John W. Eaton]

On 18-Jan-2011, Kim Hansen wrote:

| Has the output of "octave-config -p OCTINCLUDEDIR" been changed by
| design or accident?
| 
| address@hidden:~$ /home/kim/octave/install-release-3-0-x/bin/octave-config
| -p OCTINCLUDEDIR
| /home/kim/octave/install-release-3-0-x/include/octave-3.0.5
| address@hidden:~$ /home/kim/octave/install-release-3-2-x/bin/octave-config
| -p OCTINCLUDEDIR
| /home/kim/octave/install-release-3-2-x/include/octave-3.2.4
| address@hidden:~$ /home/kim/octave/install-trunk/bin/octave-config -p 
OCTINCLUDEDIR
| /home/kim/octave/install-trunk/include/octave-3.3.55/octave
| address@hidden:~$
| 
| It now (trunk from today) adds "/octave" at the end meaning that I
| have to rewrite "#include <octave/oct.h>" to "#include <oct.h>" in my
| binary modules in order to recompile them for the trunk version.

I think the idea behind the change was so that OCTINCLUDEDIR could be
used directly as the place where include files should be installed.

The last component of OCTINCLUDEDIR should always be /octave.  If you
use custom Makefile rules, you can continue to use <octave/oct.h> if
you do something similar to what the mkoctfile script does:

  DEFAULT_INCFLAGS="-I$OCTINCLUDEDIR/.. -I$OCTINCLUDEDIR"
  if [ "$INCLUDEDIR" != /usr/include ]; then
    DEFAULT_INCFLAGS="$DEFAULT_INCFLAGS -I$INCLUDEDIR"
  fi

Or you can just use mkoctfile to compile .oct files and not worry
about these details.

jwe