[GRASS-dev] GRASS 7 swig bindings: reorganization of code

GRASS GRASS developer
1

Markus wrote:

in order to facilitate the creation of other bindings, I
suggest to move the
swig/python/*.i
files into
swig/include/

Then the various language wrappers could include from there.

(e.g. java bindings could be popular)

Hamish

2

On Wed, May 6, 2009 at 2:46 AM, Hamish <hamish_b@yahoo.com> wrote:

Markus wrote:

in order to facilitate the creation of other bindings, I
suggest to move the
swig/python/*.i
files into
swig/include/

Then the various language wrappers could include from there.

(e.g. java bindings could be popular)

Exactly - I have tried to generate them and create a prototype
which yet happily fails (I am not familiar with Python but was asked
if GRASS could provide these bindings):

http://www.swig.org/Doc1.3/Java.html

Indeed I have discovered PyObjects in some .i files, so one
more separation will be needed.

Markus

3

Hi Markus,

[...]

(e.g. java bindings could be popular)

Exactly - I have tried to generate them and create a prototype
which yet happily fails (I am not familiar with Python but was asked
if GRASS could provide these bindings):

http://www.swig.org/Doc1.3/Java.html

Indeed I have discovered PyObjects in some .i files, so one
more separation will be needed.

I am not able to help in the generation process because of lack of
time right now, but if you post problems to the list perhaps I may be
able to help somehow?

Regards,
Andrea

Markus
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev