[Gdal-dev] GDAL 1.5.0 managed wrapper binaries
max at geoinova.com
Thu Mar 27 04:04:12 EDT 2008
Throwing it all into the single binary package would be great :-)
Just a quick note regarding package naming - it's actually "managed
package", rather than "csharp package". I'm aware that this specific port
has been written in C#, still it's deployed over .NET/Mono platforms.
Tamas Szekeres wrote:
> 2008/3/26, Chris Howell <chowell at pyxisinnovation.com>:
>> Since this closely relates to.
>> http://trac.osgeo.org/gdal/ticket/2290 I felt like
>> throwing my two sense in.
>> I wonder if we could incorporate a policy in gdal how these
>> complementary packages (like gdal-csharp) are created for the osgeo4w
>> [chowell] - Great idea. I suggest a layout something like this.
>> gdalVERSION.dll (native dll)
>> gdalVERSION-wrap.dll (wrapper dll)
>> gdalVERSION-CSharp.dll (C# dll obviously), or whatever binary language
>> we're building to.
> Either the *_wrap.dll -s or the *_csharp.dll-s are belong to the same
> csharp interface so these files should be placed into the same binary
> package. But we should possibly rename the *_wrap.dll-s to a more c#
> specific name (like ogr_cswrap.dll for example) since these files
> should go to the common osgeo4w/bin folder where the other unmanaged
> dll-s are placed.
> Currenly we have an install target in the gdal makefile.vc but I'm not
> sure how it is used actually. It should possibly provide the necessary
> actions to copy the compiled binaries to the expected location in the
> target folder (or something like this). In addition each of the
> language bindings should include some additional steps to package the
> desired files into a single compressed file ready to use by the
> osgeo4w installer.
> Best regards,
> gdal-dev mailing list
> gdal-dev at lists.osgeo.org
View this message in context: http://www.nabble.com/GDAL-1.5.0-managed-wrapper-binaries-tp16302768p16323332.html
Sent from the GDAL - Dev mailing list archive at Nabble.com.
More information about the gdal-dev