GNOME Bugzilla – Bug 697511
doxygen.vcproj Would Not Load on Visual Studio.net 2010 SP1
Last modified: 2015-06-29 02:10:41 UTC
I attempted to load the tarball of doxygen 1.8.3.1 on Visual Studio.net 2010 Service Pack 1. doxygen.vcproj could not be converted or even compile due to the following error: The following error has occurred during XML parsing: File: C:\Users\Kevin\Documents\Doxygen\doxygen-1.8.3.1\winbuild\Doxygen.vcproj Line: 37 Column: 5 Error Message: System error: -2146233088. The file 'C:\Users\Kevin\Documents\Doxygen\doxygen-1.8.3.1\winbuild\Doxygen.vcproj' has failed to load. More details follow: Conversion Report - Doxygen.vcproj: Converting project file 'C:\Users\Kevin\Documents\Doxygen\doxygen-1.8.3.1\winbuild\Doxygen.vcproj'. VCConvertEngine.dll encountered an error. VCConvertEngine.dll encountered an error. VCConvertEngine could not convert attribute ConfigurationType = 1 under Configuration Debug|Win32. VCConvertEngine could not convert attribute UseOfMFC = 0 under Configuration Debug|Win32. VCConvertEngine could not convert attribute CharacterSet = 2 under Configuration Debug|Win32. The "Output" item metadata name is reserved, and cannot be used. C:\Users\Kevin\Documents\Doxygen\doxygen-1.8.3.1\winbuild\Lex.props Project upgrade failed. Converting 'C:\Users\Kevin\Documents\Doxygen\doxygen-1.8.3.1\winbuild\Lex.rules'. Done processing 'C:\Users\Kevin\Documents\Doxygen\doxygen-1.8.3.1\winbuild\Lex.rules'. Semicolon is the only supported separator in MSBuild. Usage of any other separator for Custom Build Rule string properties is invalid after conversion. At the moment, I do not have the time to edit the original files, or even make new ones. I will have to analyze doxygen.vcproj to see what the specs are so that I can get a working build system for doxygen to compile on Visual Studio.net 2010.
Created attachment 240907 [details] Visual Studio Files Attached are the build files that have been converted in place to Visual Studio 2010 format.
Created attachment 248084 [details] [review] Replace for Doxygen.vcproj Visual Studio 2010 and following have problems with "Output" field and changing the command line for the tools. I fixed it manually.
Be advised that the laptop I had containing VS 2010 is about to be delivered to a service center for warranty repair. I will mark this bug as NEW if someone else verifies that the patch in comment 2 fixes this bug, or if I get my laptop back probably two more weeks from now and confirm that the patch works.
I got my laptop back and ran some software maintenance on it. I tried to replace Doxygen.vcproj with that in comment 2 and got the following error: The following error has occurred during XML parsing: File: C:\Users\Kevin\Documents\Doxygen\doxygen-1.8.3.1\winbuild\Doxygen.vcproj Line: 9 Column: 2 Error Message: System error: -2146233088. The file 'C:\Users\Kevin\Documents\Doxygen\doxygen-1.8.3.1\winbuild\Doxygen.vcproj' has failed to load. jochen.kiene, can you attach a zip file of your "winbuild" directory without the Debug and SQL files? That will probably be an easier way to get this bug closed.
Closing this bug report as no further information has been provided. Furthermore, Visual Studio 2013 is now in mainstream, so I think it is better to file a new bug report with new .vcprojx files whenever we figure out how to get Visual Studio 2013 to compile doxygen and the dependents included with the tarball.
Changing bug resolution to obsolete due to introduction of CMake in the source code of Doxygen 1.8.11.