MantisBT - GCC-XML
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0012632GCC-XML(No Category)public2011-12-18 11:472015-03-26 11:59
Reporterjmargeta 
Assigned ToBrad King 
PrioritynormalSeverityminorReproducibilityhave not tried
StatusresolvedResolutionsuspended 
PlatformPC x86 OSWindowsOS Version7 64bit
Summary0012632: Visual studio 2011 compiler support
DescriptionVisual studio 2011 compiler not supported and compilation fails.
Steps To Reproduce
Additional InformationSee attached diff file for proposed changes.
TagsNo tags attached.
Relationships
related to 0011463resolved Brad King msvc10 support. 
Attached Filestxt patchVC11.txt (23,500) 2011-12-18 11:47
https://public.kitware.com/Bug/file/4148/patchVC11.txt
Issue History
Date ModifiedUsernameFieldChange
2011-12-18 11:47jmargetaNew Issue
2011-12-18 11:47jmargetaFile Added: patchVC11.txt
2011-12-19 14:06Brad KingNote Added: 0028012
2011-12-19 16:16Brad KingRelationship addedrelated to 0011463
2011-12-19 16:17Brad KingNote Added: 0028013
2015-03-26 11:59Brad KingNote Added: 0038318
2015-03-26 11:59Brad KingStatusnew => resolved
2015-03-26 11:59Brad KingResolutionopen => suspended
2015-03-26 11:59Brad KingAssigned To => Brad King

Notes
(0028012)
Brad King   
2011-12-19 14:06   
Thanks for starting on this. The main work to support a new VS version is to construct the patches to VS system header files. There are two types of headers:

(1) The C/C++ standard library headers. These are installed in the VC/Include folder.

(2) The Windows SDK headers. These are installed as part of a separate Windows SDK package that happens to be provided by the VS installer.

Headers from both places need to be copied and patched by GCC_XML/VcInstall/* to make them parse-able with the gccxml builtin patched GCC 4.2 parser. The hard part is in creating files like vc10Include.patch and vc10PlatformSDK.patch. You need to create a local repository, copy all the headers into it, hack gxConfiguration.cxx to use your local copy instead of the system one, and then edit the headers until they can all be #include-d by gccxml.
(0028013)
Brad King   
2011-12-19 16:17   
See 0011463 for how this was done for VS 10.
(0038318)
Brad King   
2015-03-26 11:59   
As announced here:

 [ANNOUNCE] GCC-XML maintenance moving to Github
 http://thread.gmane.org/gmane.comp.compilers.gccxml/731 [^]
 http://public.kitware.com/pipermail/gccxml/2015-March/003206.html [^]

gccxml will no longer be developed by its original author, who will instead focus on CastXML:

 https://github.com/CastXML/CastXML#readme [^]

The original GCC-XML issue tracker is now closed. In order to facilitate ongoing maintenance by community participants, issues will now be tracked on the Github repository page:

 https://github.com/gccxml/gccxml/issues [^]