Re: [OctDev] Re: delaunay

[Paul K. <pki...@us...>]

On Apr 28, 2005, at 5:15 AM, Rafael Laboissiere wrote:

> * Dmitri A. Sergatskov <das...@gm...> [2005-04-27 07:49]:
>
>> I noticed that "make install" in octave-forge would install delaunay.m
>> (and related) even though qhull is not present and delaunayn.oct has
>> not being built. Perhaps this is a bug in the octave-forge configure
>> script?
>
> Yes, it seems to be a bug.  Unfortunately, I am not very used to the
> octave-forge configure/Makefile scheme and I would prefer that someone
> else review this issue.

Install is mostly handled by main/Makefile, which walks through every
subdirectory without a NOINSTALL file and runs octinst.sh on it.  This
installs every oct-file and m-file.

The quick hack is to figure out how to make ./configure touch or remove
main/geometry/NOINSTALL depending on whether qhull is present.  You
can't do it from main/geometry/Makefile since this will not be used
if main/geometry/NOINSTALL is present.  This isn't a very good solution.

Perhaps it is time to rethink the idea of automatically installing every
m-file and oct-file in a directory, and instead go back to explicitly
listing the files which need to be installed.

In the meantime, I'm inclined to live with a non-working delaunay.m
installed when qhull is not present.

- Paul