[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 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?

 Assefa - it would be helpful (I think) if the mapserver package installed
 mapscriptvars in the install include directory along with the include
 files.  That would make it cleaner to build the various mapscripts in a
 compatible way.  What do you think?

 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.

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