<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body ><div>Steve, </div><div><br></div><div>the best would be then that you create the account since it will need an e mail for activation and in case of password forgetting. You can then add my github account as additional administrator.</div><div><br></div><div>Even</div><div><br></div><div><br></div>---<div>Spatialys - Geospatial professional services</div><div>http://www.spatialys.com</div><br><br><div>-------- Message d'origine --------</div><div>De : "Lime, Steve D (MNIT)" <Steve.Lime@state.mn.us> </div><div>Date :07/08/2015 00:00 (GMT+01:00) </div><div>À : Even Rouault <even.rouault@spatialys.com>, mapserver-dev <mapserver-dev@lists.osgeo.org> </div><div>Cc : </div><div>Objet : RE: [mapserver-dev] Appveyor Windows continuous integration </div><div><br></div>Hi Even: Thanks for taking this on. Seems useful I since most devs have zero way to test changes in the context of Windows. Making it work with a MapServer-specific account against master sounds like the way to go rather than burdening your account. I'd be happy being the username/password custodian if need be.<br><br>Steve<br><br>-----Original Message-----<br>From: mapserver-dev-bounces@lists.osgeo.org [mailto:mapserver-dev-bounces@lists.osgeo.org] On Behalf Of Even Rouault<br>Sent: Thursday, August 06, 2015 7:34 AM<br>To: mapserver-dev <mapserver-dev@lists.osgeo.org><br>Subject: [mapserver-dev] Appveyor Windows continuous integration<br><br>Hi,<br><br>I've experimented a Appveyor Windows continuous integration setup in my fork :<br>https://github.com/rouault/mapserver/blob/appveyor/appveyor.yml<br><br>And finally managed to get a successful build:<br>https://ci.appveyor.com/project/rouault/mapserver/build/1.0.33<br><br>It does 32 and 64 bit builds, with Visual Studio 12 2013 (other versions could <br>be added to the matrix). <br><br>The current options are :<br>-- * Summary of configured options for this build<br>-- * Mandatory components<br>-- * png: C:\projects\mapserver\sdk\release-1800-x64\lib\libpng.lib<br>-- * jpeg: C:/projects/mapserver/sdk/release-1800-x64/lib/libjpeg.lib<br>-- * freetype: C:/projects/mapserver/sdk/release-1800-<br>x64/lib/freetype2411.lib<br>-- * Optional components<br>-- * GDAL: C:/projects/mapserver/sdk/release-1800-x64/lib/gdal_i.lib<br>-- * OGR: C:/projects/mapserver/sdk/release-1800-x64/lib/gdal_i.lib<br>-- * GIF: C:/projects/mapserver/sdk/release-1800-x64/lib/giflib.lib<br>-- * MYSQL: disabled<br>-- * FRIBIDI: C:/projects/mapserver/sdk/release-1800-x64/lib/fribidi.lib<br>-- * HARFBUZZ: C:/projects/mapserver/sdk/release-1800-x64/lib/harfbuzz.lib<br>-- * GIF: C:/projects/mapserver/sdk/release-1800-x64/lib/giflib.lib<br>-- * CAIRO: C:/projects/mapserver/sdk/release-1800-x64/lib/cairo.lib<br>-- * SVGCAIRO: C:/projects/mapserver/sdk/release-1800-x64/lib/libsvg-<br>cairo.lib<br>-- * RSVG: disabled<br>-- * CURL: C:/projects/mapserver/sdk/release-1800-x64/lib/libcurl_imp.lib<br>-- * PROJ: C:/projects/mapserver/sdk/release-1800-x64/lib/proj_i.lib<br>-- * PIXMAN: disabled<br>-- * LIBXML2: C:/projects/mapserver/sdk/release-1800-x64/lib/libxml2.lib<br>-- * POSTGIS: C:/projects/mapserver/sdk/release-1800-x64/lib/libpqdll.lib<br>-- * GEOS: C:/projects/mapserver/sdk/release-1800-x64/lib/geos_c.lib<br>-- * FastCGI: C:/projects/mapserver/sdk/release-1800-x64/lib/libfcgi.lib<br>-- * Oracle Spatial: disabled<br>-- * Exempi XMP: disabled<br>-- * Optional features<br>-- * WMS SERVER: ENABLED<br>-- * WFS SERVER: ENABLED<br>-- * WCS SERVER: ENABLED<br>-- * SOS SERVER: ENABLED<br>-- * WMS CLIENT: ENABLED<br>-- * WFS CLIENT: ENABLED<br>-- * ICONV: ENABLED<br>-- * Thread-safety support: ENABLED<br>-- * KML output: ENABLED<br>-- * Z+M point coordinate support: ENABLED<br>-- * XML Mapfile support: disabled<br>-- * Mapscripts<br>-- * Python: ENABLED<br>-- * PHP: disabled<br>-- * PERL: disabled<br>-- * RUBY: disabled<br>-- * JAVA: disabled<br>-- * C#: disabled<br>-- * V8 Javascript: disabled<br>-- * Apache Module (Experimental): disabled<br>-- <br><br>So pretty much all external libs + python. No tests are run.<br><br>This relies heavily on Tamas' SDKs to provide all the required dependencies. <br>But I had some hard time figuring out a few cmake options. I couldn't find any <br>online page with a cmake Windows setup. The weirdest oddity I had to fight is <br>that I had to do "copy libpng.lib libpng.lib.lib" to be able to link. iconv <br>was a bit particular too since you have to specify ICONV_DLL unlike other <br>libraries. And for curl linking I add to specify -<br>DMS_EXTERNAL_LIBS=wsock32.lib<br><br>Is there interest in migrating this to master ? My experience is that Appveyor <br>response time is rather dependant on the hour of the day. It can fire jobs a <br>few seconds after push at morning/early afternoon European time, but I found <br>that later in the day when North Americans wake up, builds can be queued for <br>minutes or hours. At least, this seems true for free accounts like mine.<br><br>The appveyor account used is mine currently. I could update it to build from <br>the official mapserver github repo instead of my fork, and I believe that should <br>work, even for pull requests.<br>Perhaps it would be best to have a appveyor "mapserver" account, but there's <br>no easy way with Appveyor to create a Appveyor account linked to a github <br>organization account like mapserver (contrary to Travis I believe). I found <br>that one can create manually a appveyor mapserver account, with independant <br>login&password identification, and then add github accounts of individuals as <br>administrators. I can try that if that's OK.<br><br>Best regards,<br><br>Even<br><br>-- <br>Spatialys - Geospatial professional services<br>http://www.spatialys.com<br>_______________________________________________<br>mapserver-dev mailing list<br>mapserver-dev@lists.osgeo.org<br>http://lists.osgeo.org/mailman/listinfo/mapserver-dev<br><br></body>