[Gneuralnetwork] [PATCH] Compile gneuralnetwork as library

[Aljosha Papsch]

Hello gneuralnetworkers,

my motivation in joining gneuralnetwork is bringing Guile[0] support to 
it. I'm not involved in neural network programming, so don't expect 
changes which improve gneuralnetwork's network capabilities. However, I 
believe bringing Guile to gneuralnetwork can be a huge benefit for 
gneuralnetwork. It makes gneuralnetwork hackable, because one doesn't 
need to know C or learn the intricate configuration format. Scheme is 
flexible and a complete programming language compared to the .script 
files. You don't even have to fear the parentheses; wisp[1] makes Guile 
Scheme look as readable as Python.

I could write more arguments in favor of Guile but I'd rather come to 
the practical side of things:
How can Guile be integrated in gneuralnetwork?

A first step to this is building the major part of gneuralnetwork as a 
library, which can be used by Guiles foreign function interface[2] (FFI) 
for interfacing gneuralnetwork's C functions in Scheme. Attached is a 
series of patches which does this. This is the foundation for next broad 
steps:

* Write Guile bindings using FFI
* Write Scheme programs equivalent to the .script files

While doing this, it should be possible to keep parser.c, so .script 
files can still be used. They could even be used when Guile support is 
proper. What is your stance on this?

Best regards
Aljosha

[0] https://gnu.org/software/guile/
[1] http://www.draketo.de/english/wisp/
[2] 
https://gnu.org/software/guile/manual/html_node/Foreign-Function-Interface.html

0001-Ignore-autoconf-build-files-and-GNOME-Builder-projec.patch
Description: Text Data

0002-Ignore-autoconf-build-files.patch
Description: Text Data

0003-Compile-sources-as-libtool-library-and-link-main-pro.patch
Description: Text Data

0004-Install-header-files-along-with-library.patch
Description: Text Data