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

GRASS GRASS developer
1

Hi,

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.

?
Markus

2

Markus Neteler 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.

common.i, grass.i, my_typemaps.i and utils.i are language-specific,
but the rest could be moved.

--
Glynn Clements <glynn@gclements.plus.com>

3

Glynn,

On Wed, May 6, 2009 at 12:13 PM, Glynn Clements
<glynn@gclements.plus.com> wrote:

Markus Neteler 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.

common.i, grass.i, my_typemaps.i and utils.i are language-specific,
but the rest could be moved.

I have restructured the includes following the GDAL SWIG bindings
(tarball attached).
But I don't manage to get swig/python/Makefile right...

Would you mind to look into that?

thanks
Markus

(attachments)

swig_includes.tar.gz (2.63 KB)

4

Markus Neteler 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.
>
> common.i, grass.i, my_typemaps.i and utils.i are language-specific,
> but the rest could be moved.

I have restructured the includes following the GDAL SWIG bindings
(tarball attached).
But I don't manage to get swig/python/Makefile right...

Would you mind to look into that?

Done in r37387.

--
Glynn Clements <glynn@gclements.plus.com>