Changes between Version 3 and Version 4 of FDORfc70


Ignore:
Timestamp:
Jun 9, 2015, 6:33:56 AM (9 years ago)
Author:
kwi
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • FDORfc70

    v3 v4  
    88||RFC Template Version||1.1|| 
    99||Submission Date||March 26, 2015||
    10 ||Last Modified||Karsten Winter - March 26, 2015||
     10||Last Modified||Karsten Winter - June 09, 2015||
    1111||Author||Karsten Winter||
    1212||RFC Status||draft||
    13 ||Implementation Status||pending||
     13||Implementation Status||under development||
    1414||Proposed Milestone||4.1.0||
    1515||Assigned PSC guide(s)||||
    1616||'''Voting History'''||(vote date)||
    17 ||+1||Greg||
     17||+1||Greg, Jackie||
    1818||+0||||
    1919||-0||||
     
    2222== Overview ==
    2323
    24 This is a proposal to update the FDO project to completely support the VC15 compiler and the v150 runtime for the current FDO 4.1.0 release. These changes will be made for the FDO, FDO Provider unmanaged and managed C++ projects. With the completion of this RFC, all binaries shipped with FDO 4.1.0 will use the v150 runtime, and none will remain using the v110 runtime.
     24This is a proposal to update the FDO project to completely support the VC14 compiler and the v140 runtime for the current FDO 4.1.0 release. These changes will be made for the FDO, FDO Provider unmanaged and managed C++ projects. With the completion of this RFC, all binaries shipped with FDO 4.1.0 will use the v140 runtime, and none will remain using the v110 runtime.
    2525
    2626== Motivation ==
    2727
    28 Supporting the new v150 runtime shipped with Visual Studio 2015 will allow clients and developers to take advantage of the latest Microsoft compiler release and its associated APIs and functionality.
     28Supporting the new v140 runtime shipped with Visual Studio 2015 will allow clients and developers to take advantage of the latest Microsoft compiler release and its associated APIs and functionality.
    2929
    3030== Proposed Solution ==
    3131
    32 •       All *_vs12.sln solution files in the trunk will be renamed to *_vs15.sln and the project files will be upgraded to use the VC15 compiler and v150 runtime.[[BR]]
     32•       All *_vs12.sln solution files in the trunk will be renamed to *_vs15.sln and the project files will be upgraded to use the VC14 compiler and v140 runtime.[[BR]]
    3333•       All projects will be recompiled and code changes made as appropriate[[BR]]
    3434•       All unit tests will be run and must pass before the above changes can be submitted back to the FDO Trunk.[[BR]]
     
    3737
    3838•       The KingInformix, KingKML and KingMsSqlSpatial providers will not be updated to VC15 by Autodesk.[[BR]]
    39 Responsibility for updating the build settings for these providers and verifying that these providers build with the v150 runtime will have to be undertaken by other Open Source FDO developers, potentially the King developer group.
     39Responsibility for updating the build settings for these providers and verifying that these providers build with the v140 runtime will have to be undertaken by other Open Source FDO developers, potentially the King developer group.
    4040
    4141== Implications ==