The problem with VC10 has been confirmed and should now be fixed. The Apache Subversion Repository for XALAN-C has VC10 vcxproj files repaired. This commit fixes the situation where both Release and Debug *.lib files were referenced when linking sample projects.
Steven J. Hathaway > This seems unusual, but here is a description of a fix to the .NET 2010 > IDE build problem. > I have worked almost 2 days researching the problem and testing the > build prototypes. > > The automatic Microsoft Upgrade from VS 2008 created problematic > settings for the linker. > > The resolution for each executable build project in the solution is to > open > the project properties and make the following changes to: > > Configuration Properties -> Linker -> Gemeral > Set Link Library Dependencies = No > > Configuration Properties -> Linker -> Input > Set Additional Dependencies -> [For Release Configurations] > xerces-c_3.lib > Xalan-C_1.lib > [x} Inherit from parent or project defaults > > Configuration Properties -> Linker -> Input > Set Additional Dependencies -> [For Debug Configurations] > xerces-c_3D.lib > Xalan-C_1D.lib > [x} Inherit from parent or project defaults > > Adding the proper Xalan-C_1.lib resolves the links without the IDE doing > additional > searching of projects. > > Setting the "Link Library Dependencies = No" also removes some automatic > searching > of projects for links that may not be required for the executable > application. > > I will be making the corrections to the repository later today -- > 12/4/2011. > > Sincerely, > Steven J. Hathaway > > On 12/1/2011 11:31 AM, Goffena, Robert wrote: >> I researched a little more and came up with the following conclusion. >> >> My problems seem to be due to the way project dependencies/references >> are handled in VS2010: >> http://blogs.msdn.com/b/vcblog/archive/2010/02/16/project-settings-chang >> es-with-vs2010.aspx?PageIndex=3 >> >> Easiest solution seems to be: >> 1) set Properties->Common Properties->Framework and >> References->Reference Assembly Output to true >> 2) set Properties->Configuration Properties->Linker->General->Link >> Library Dependencies to false >> for each project that has this problem. >> >> Still curious if other developers have encountered this problem, or if I >> have something incorrectly configured in VS2010. >> >> Robert Goffena >> Ball Aerospace& Technologies Corp. >> 2875 Presidential Dr. Fairborn, OH 45324-6269 >> Phone: (937) 320-4096 >> Fax: (937) 429-1687 >> Email: rgoff...@ball.com >> >> -----Original Message----- >> From: Goffena, Robert [mailto:rgoff...@ball.com] >> Sent: Thursday, December 01, 2011 1:58 PM >> To: xalan-c-users@xml.apache.org >> Subject: Visual Studio 2010 IDE Build Problem >> >> I tried building the latest revision (1207768) of the xalanc trunk using >> Visual Studio 2010 IDE, and am running into link problems. >> Various projects (ie: XalanTransform) try to link against both the debug >> and release builds of Xalan-C_1.lib. >> >> Unchecking Configuration Properties->Linker->General->Link Library >> Dependencies and then adding appropriate Xalan-C_1.lib to >> Properties->Linker->General->Input->Additional Dependencies will likely >> resolve this error. >> >> Is anyone else seeing this problem? Have I configured something in >> VS2010 incorrectly? >> >> Robert Goffena >> Ball Aerospace& Technologies Corp. >> 2875 Presidential Dr. Fairborn, OH 45324-6269 >> Phone: (937) 320-4096 >> Fax: (937) 429-1687 >> Email: rgoff...@ball.com >> >> > >
