2009/5/23 Francesco Paolo Lovergine
>
> If the swig stuff was by default auto-regenerated at building time we could
> have
> some problems from time to time in Debian/Ubuntu, due to recurrent
> problems in moving from one distributed swig version to another. We found
> problems in 1.3.38 and poss
On Tue, May 12, 2009 at 11:43:25PM +0200, Tamas Szekeres wrote:
> 2009/5/12 Frank Warmerdam
>
> >
> > I've also got to the point where FWTools CSharp bindings are no longer
> > being built properly and I don't know why or how to fix it.
> >
>
> Frank,
>
> Do you have more specific information a
2009/5/12 Frank Warmerdam
>
> I've also got to the point where FWTools CSharp bindings are no longer
> being built properly and I don't know why or how to fix it.
>
Frank,
Do you have more specific information about the issue above? I'm not aware
of any problems when building the recent version
Tamas Szekeres wrote:
+1
I don't think we should keep any of the generated stuff just because of
the buildbot. All of the builders should be capable to generate the
bindings as part of the build steps. Only the path to the swig
executable should be detected/specified. The Windows buildslaves
+1
I don't think we should keep any of the generated stuff just because of the
buildbot. All of the builders should be capable to generate the bindings as
part of the build steps. Only the path to the swig executable should be
detected/specified. The Windows buildslaves are OK in this regard.
Bes
Howard,
I have well understood that you suggest to refresh it always as part of the
release process, so the following question only applies during development
time.
If we keep the generated code in SVN for conveniency for buildbot, when are we
supposed to refresh that generated code in SVN ?
-
Howard Butler wrote:
Dear SWIG bindings devs,
I would like to propose the following motions for the upcoming 1.7 GDAL
release:
1) All swig bindings will be regenerated as part of the release process.
2) We will move up to SWIG 1.3.39 by for the release generation.
+0
I don't have the backg
+1
Ari
Howard Butler kirjoitti:
Dear SWIG bindings devs,
I would like to propose the following motions for the upcoming 1.7
GDAL release:
1) All swig bindings will be regenerated as part of the release process.
2) We will move up to SWIG 1.3.39 by for the release generation.
As far as moti
Dear SWIG bindings devs,
I would like to propose the following motions for the upcoming 1.7
GDAL release:
1) All swig bindings will be regenerated as part of the release process.
2) We will move up to SWIG 1.3.39 by for the release generation.
As far as motion 1 is concerned, I would note th
