[Osgeo4w-trac] Re: [osgeo4w] #2: Add existing MS4W mapscript packages

[OSGeo4W]

#2: Add existing MS4W mapscript packages
-----------------------+----------------------------------------------------
  Reporter:  jmckenna  |       Owner:  warmerdam   
      Type:  task      |      Status:  new         
  Priority:  major     |   Milestone:  Beta Release
 Component:  Package   |     Version:  Alpha       
Resolution:            |    Keywords:              
-----------------------+----------------------------------------------------
Comment (by tamas):

 Replying to [comment:4 warmerdam]:
 > OK, mapscript-python (stable and dev) are now packaged.
 >
 > Tamas,
 >
 > I would suggest you start out with c# bindings for 5.0.x stable.  The
 mapserver source file
 (http://download.osgeo.org/osgeo4w/release/mapserver/mapserver-5.0.2-2-src.tar.bz2)
 contains the nmake.opt file that was used.  So using that it should be
 fairly easy to recreate the mapscriptvars file (if you use that).  The
 main mapserver package also installs the include files which is helpful.
 >
 > Does csharp use the mapscriptvars file?
 >

 No, it doesn't. Currently the csharp makefile includes the nmake.opt from
 the root directory. Therefore if you specify something different (like
 using an external optfile in addition) then we might also specify this
 when building the csharp bindings. It must be noted that I use only the
 make or nmake tools for making up the builds, therefore the mapscriptvars
 should be created in a makefile friendly fashion in order to use it
 direcly when creating the bindings.

 > Tamas - I think (hope) it is possible for MSVC80 compiled C# bindings to
 call an MSVC7.1 compiled libmap.dll for the core.  I don't want to see us
 producing multiple copies of the mapserver package for different
 compilers. If we have to do that, I think we have failed to some extent.
 But it should be possible for you to produce C# mapscript packages for
 .net 2.0 using MSVC8 and .net 1.1 using something older (VC7.1?).  Or just
 pick one .net framework that you want to support and only produce a
 package for that.
 >
 >

 It might be possible but it's potentially unsupported by microsoft,
 therefore it's not guaranteed to work in every condition. Though the
 assemblies targeting different runtimes may definitely work side by side
 (except for the win64 and win32 relations) but we cannot safely use dlls
 with different CRT dependecies.

 I think it would be reasonable to restrict the builds to the same compiler
 and platform at osgeo4w, I'll be trying to create a script to produce
 csharp package using your sources and compiled libs.

 In addition I'm just working on a makefile to create a consistent build
 for various compilers and platforms for those who cannot rely on the
 osgeo4w versions. I guess the  mapscript csharp users are potentially an
 addressed group in this regard.

 Tamas

-- 
Ticket URL: <http://trac.osgeo.org/osgeo4w/ticket/2#comment:6>
OSGeo4W <http://trac.osgeo.org/osgeo4w>
OSGeo4W is the Windows installer for the OSGeo stack.