Re: Announcing Octave-FANN

[Søren Hauberg]

Hi

David Bateman wrote:
[snip]
> Why not migrate the whole package to octave-forge, probably under the 
> extras directory due to the narrow scope of the package... Then you can 
> use the existing configuration/make structure of octave-forge to deal 
> with it. You'll need a configure.add and Makeconf.add file to indentify 
> if fann is installed, and if you have any m-files then you might need to 
> deal with the issues of why to do with the installation of these in the 
> case that fann is not present. There are several ways of dealing with 
> that, either replace the dot-m files with *.m.in filenames and 
> conditionally copy them to *.m if fann is installed (there are examples 
> of this main/general/Makefile), or you can alter the m-files so that 
> they check the installation and exit with an error if fann is not 
> installed...
This might be a good solution. The FANN library have a lot of bindings 
at their webpage, so I figured this would be a better place to keep the 
library, but perhaps octave-forge is better (assuming it would get 
accepted into octave-forge). I'll have a quick look and then I'll send a 
mail to the octave-forge mailing-list.

> Cheers
> David
Thanks for the advice,
Søren




-------------------------------------------------------------
Octave is freely available under the terms of the GNU GPL.

Octave's home on the web:  http://www.octave.org
How to fund new projects:  http://www.octave.org/funding.html
Subscription information:  http://www.octave.org/archive.html
-------------------------------------------------------------