Hi Ari,
Creating language specific main files would be fine for me. We could also
add the "language specific extensions" at the bottom section (like
gdal_csharp_extend.i) directly into the file.
We should however make sure to update all relevant files if a common change
is done in a language spec
Hi,
I've been trying to find a way to make the common SWIG interface files
less concerned about languages and the whole system more flexible and
understandable (which I see a prerequisite for further developments).
My conclusion seems to be now that it is probably better to make the
main fil
Le lundi 09 mars 2015 14:47:48, Ari Jolma a écrit :
> I'm curious about the setup.
>
> Do you commit to github, which then commits to trac.osgeo.org/gdal or
> how is the system setup?
Regarding Travis, this is vaguely described at
http://trac.osgeo.org/gdal/wiki/Buildbot
Basically I've a cron j
I'm curious about the setup.
Do you commit to github, which then commits to trac.osgeo.org/gdal or
how is the system setup?
Ari
09.03.2015, 15:31, Even Rouault kirjoitti:
Le lundi 09 mars 2015 14:27:05, Ari Jolma a écrit :
09.03.2015, 11:18, Even Rouault kirjoitti:
Or if you prefer Git, yo
Le lundi 09 mars 2015 14:27:05, Ari Jolma a écrit :
> 09.03.2015, 11:18, Even Rouault kirjoitti:
> > Or if you prefer Git, you could fork https://github.com/OSGeo/gdal
>
> I did this fork and made the changes in my copy. Then made a pull
> request and now it says that the Travis CI build passed.
>
09.03.2015, 11:18, Even Rouault kirjoitti:
Or if you prefer Git, you could fork https://github.com/OSGeo/gdal
I did this fork and made the changes in my copy. Then made a pull
request and now it says that the Travis CI build passed.
But I assume Java etc. are not tested by Travis?
Ari
09.03.2015, 11:18, Even Rouault kirjoitti:
Le lundi 09 mars 2015 08:08:34, Ari Jolma a écrit :
08.03.2015, 23:49, Even Rouault kirjoitti:
Le dimanche 08 mars 2015 22:20:50, Ari Jolma a écrit :
Ari,
Your proposal looks reasonable (but I don't pretend mastering SWIG and
anticipating all side ef
Le lundi 09 mars 2015 08:08:34, Ari Jolma a écrit :
> 08.03.2015, 23:49, Even Rouault kirjoitti:
> > Le dimanche 08 mars 2015 22:20:50, Ari Jolma a écrit :
> >
> > Ari,
> >
> > Your proposal looks reasonable (but I don't pretend mastering SWIG and
> > anticipating all side effects) and you can ex
08.03.2015, 23:49, Even Rouault kirjoitti:
Le dimanche 08 mars 2015 22:20:50, Ari Jolma a écrit :
Ari,
Your proposal looks reasonable (but I don't pretend mastering SWIG and
anticipating all side effects) and you can experiment with that if you wish.
Please make sure to test the 4 supported l
Le dimanche 08 mars 2015 22:20:50, Ari Jolma a écrit :
> Even,
>
> It took me quite a while again to understand what goes on with Swig when
> we %apply a typemap etc.
>
> I think we could simplify the things quite a lot if we simply use
> typedefs and then create typemaps for the return values.
>
Even,
It took me quite a while again to understand what goes on with Swig when
we %apply a typemap etc.
I think we could simplify the things quite a lot if we simply use
typedefs and then create typemaps for the return values.
For example CPLErr is never returned to the calling language (I
Howard Butler kirjoitti:
On Jul 22, 2008, at 9:48 AM, Ari Jolma wrote:
The trac.osgeo.org does not answer so I'll put this here.
Hobu, would it be ok to have (int len, int *output) typemap. They can
be used in GetHistogram method like this (note that the API is same
for C# but it must use d
Using the same approach for the csharp bindings seems much more
complicated than the current method. Currently the caller (at the
csharp side) allocates a fixed length int array and the default
marshaler takes care of passing the array to the unmanaged (C) part of
the code. There's no need to do ex
On Jul 22, 2008, at 9:48 AM, Ari Jolma wrote:
The trac.osgeo.org does not answer so I'll put this here.
Hobu, would it be ok to have (int len, int *output) typemap. They
can be used in GetHistogram method like this (note that the API is
same for C# but it must use different typemaps. From
The trac.osgeo.org does not answer so I'll put this here.
Hobu, would it be ok to have (int len, int *output) typemap. They can be
used in GetHistogram method like this (note that the API is same for C#
but it must use different typemaps. From Band.i:
#ifndef SWIGCSHARP
%feature( "kwargs" ) G
15 matches
Mail list logo
