Changes between Version 2 and Version 3 of MapGuideRfc138


Ignore:
Timestamp:
Sep 2, 2013, 3:40:57 AM (11 years ago)
Author:
jng
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • MapGuideRfc138

    v2 v3  
    11
    2 = !MapGuide RFC XYZ - Upgrade Apache, Tomcat and PHP =
     2= !MapGuide RFC 138 - Upgrade Apache, Tomcat and PHP =
    33
    44This page contains a change request (RFC) for the !MapGuide Open Source project.
     
    3737In addition, we should ideally move to a version of Apache and PHP that is built off of the same Visual Studio 2012 C++ compiler, since the MapGuide codebase has already migrated to this compiler.
    3838
    39 Moving to Apache httpd 2.4.x and PHP 5.5.x solves both of these issues:
     39Moving to Apache httpd 2.4.6 and PHP 5.5.3 solves both of these issues:
    4040
    4141 * Apache 2.4.6 is the latest stable version of Apache. http://www.apachelounge.com offers VC11 builds of Apache 2.4.x.
     
    4848Upgrade PHP to 5.5.3
    4949
    50 Update the PHP generation code in our custom build of SWIG to address any API changes caused by moving to PHP 5.5
     50Update the PHP generation code in our custom build of SWIG to address any API changes caused by moving to PHP 5.5:
     51 * {{{function_entry}}} has been changed to {{{zend_function_entry}}}
     52 * The {{{zend_rsrc_list_get_rsrc_type()}}} function now returns {{{const char*}}} instead of {{{char*}}}
    5153
    5254Update our zip distributions of Apache, PHP and Tomcat under Installer\Support to these new versions
     55 * The 2.4.6 VC11 release of httpd from (http://www.apachelounge.com/download/)
     56 * The 5.5.3 VC11 thread-safe release of PHP from (
    5357
    5458For this upgrade, we will also streamline the build system and reduce the checkout footprint as follows: