Le samedi 29 janvier 2011 22:40:20, Marius Jigmond a écrit :
> The link should work for another day or so (automatic server purge). I
> can re-upload it if you don't get the chance to download it. Warning:
> 1.2GB.
> https://www.twdb.state.tx.us/filetxfr/emaillinkdownload.aspx?id=&FileTransf
> erID
Hi Ari,
On Sun, 30. Jan 2011 at 11:36:49 +0200, Ari Jolma wrote:
>to the .def file. I create the .dll.a, which is the import library, with
>dlltool from the .def.
Did you try to link the gdal_c_i.lib instead of generating your own library
from the DLL? That what I do with GRASS. Works f
2011/1/30 Even Rouault
>
> On Windows, I think that the actual license of the odbc library doesn't
> really
> count as people won't distribute the windows odbc system library right ?
> Otherwise it would make it impossible to distribute GPL software on Windows
> since the system windows libraries
Folks,
I have updated the gdal-java package for OSGeo4W to be 1.8. I have also
rewritten the "building Java bindings on windows" topic in the GDAL Trac
to reflect how things work. I have only minimally tested the new package
so feel free to let me know if there are problems.
Best regards,
--
-
Ari,
Assuming you did mention to compile the Perl bindings with MinGW could you
describe the steps of the compilation in more detail? (by using the files
downloaded from http://vbkto.dyndns.org/sdk.) Which packages should be
installed as the prerequisites of the compilation?
I admit I'm not an exp
Le dimanche 30 janvier 2011 18:00:19, Frank Warmerdam a écrit :
> > b) For MySQL, it depends on whether you use the open source version (GPL)
> > or the commercial version.
>
> Really? I had assumed that the client libraries would have been
> under a non-reciprocal license even if the database s
On 11-01-29 06:16 PM, Even Rouault wrote:
1) I had a strange feeling when I read that "In the absence of a user or
application level policy, default to a policy of "PREFER_PROPRIETARY"". It
sounds a bit paradoxical for an open source library... I guess that on Linux,
it should be "PREFER_RECIPROC
On Sun, Jan 30, 2011 at 05:53:20PM +0530, Chaitanya kumar CH wrote:
> Thank you very much for pointing out the errors. I could blame it on the
> lack of enough sample data but that's just laziness. I should have read the
> specifications more throughly.
I noticed primarly because the GDAL interpr
On Sun, Jan 30, 2011 at 01:24:08PM +0100, Even Rouault wrote:
> Le dimanche 30 janvier 2011 12:09:12, strk a écrit :
> >
> > n1
> > +-e1-->-.
> > | F1 |
> > | n3 |
> > | ,-e2->-+|
> > | | F2 ||
> > | +-<-e7-'|
> > | n4|
>
Hi Sandro,
CC'ing Chaitanya who implemented the reading of topological GML3 elements.
Le dimanche 30 janvier 2011 12:09:12, strk a écrit :
> Hello,
> I'm writing GML output routines for Topologically-defined features
> in PostGIS and found what I think is a bug in how ogr interprets
> the tag co
strk,
Thank you very much for pointing out the errors. I could blame it on the
lack of enough sample data but that's just laziness. I should have read the
specifications more throughly.
I see your first point but I need to dig deeper for the second.
Please file a ticket at http://trac.osgeo.org/
Hello,
I'm writing GML output routines for Topologically-defined features
in PostGIS and found what I think is a bug in how ogr interprets
the tag contents.
Take this topology:
n1
+-e1-->-.
| |
| F1 |
| n3 |
| ,-e2->-+|
| | |
29.1.2011 20:43, Tamas Szekeres kirjoitti:
Ari,
I would be eager to know the exact use case you have. Did you have
some errors provided by the linker in this case?
For the stdcall functions I added entries like this
_CPLDefaultErrorHandler@12
CPLDefaultErrorHandler = _CPLDefaultErrorHandler@
13 matches
Mail list logo
