Changes between Version 3 and Version 4 of FDORfc70
- Timestamp:
- 06/09/15 06:33:56 (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
FDORfc70
v3 v4 8 8 ||RFC Template Version||1.1|| 9 9 ||Submission Date||March 26, 2015|| 10 ||Last Modified||Karsten Winter - March 26, 2015||10 ||Last Modified||Karsten Winter - June 09, 2015|| 11 11 ||Author||Karsten Winter|| 12 12 ||RFC Status||draft|| 13 ||Implementation Status|| pending||13 ||Implementation Status||under development|| 14 14 ||Proposed Milestone||4.1.0|| 15 15 ||Assigned PSC guide(s)|||| 16 16 ||'''Voting History'''||(vote date)|| 17 ||+1||Greg ||17 ||+1||Greg, Jackie|| 18 18 ||+0|||| 19 19 ||-0|||| … … 22 22 == Overview == 23 23 24 This is a proposal to update the FDO project to completely support the VC1 5 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.24 This 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. 25 25 26 26 == Motivation == 27 27 28 Supporting the new v1 50 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.28 Supporting 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. 29 29 30 30 == Proposed Solution == 31 31 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 VC1 5 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]] 33 33 • All projects will be recompiled and code changes made as appropriate[[BR]] 34 34 • All unit tests will be run and must pass before the above changes can be submitted back to the FDO Trunk.[[BR]] … … 37 37 38 38 • 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 v1 50 runtime will have to be undertaken by other Open Source FDO developers, potentially the King developer group.39 Responsibility 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. 40 40 41 41 == Implications ==