Hello Stephen, I have recently incorporated Xerces-C 3.1.2 and Xalan 1.11 in our product which was previously using versions 2.7 and 1.10 respectively. When building the VS 2010 version of Xalan for 32-bit, I have noticed that the release build seems to want to link to the debug version of XalanMessages_1_11D.dll (via XalanMsgLib.lib). If I build both release and debug, it all builds find but at runtime the release build requires that the debug version of XalanMessages_1_11D.dll be present. If I clean everything and build only the release version, I get the following errors:
------ Build started: Project: AllInOne, Configuration: Release Win32 ------ Build started 6/1/2015 5:21:34 PM. InitializeBuildStatus: Touching "..\..\..\..\Build\Win32\VC10\Release\AllInOne\AllInOne.unsuccessfulbuild". ClCompile: All outputs are up-to-date. ResourceCompile: All outputs are up-to-date. C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Microsoft.CppBuild.targets(990,5): warning MSB8012: TargetPath(E:\xalan-c-1.11\c\Projects\Win32\VC10\AllInOne\..\..\..\..\Build\Win32\VC10\Release\AllInOne.dll) does not match the Linker's OutputFile property value (E:\xalan-c-1.11\c\Build\Win32\VC10\Release\Xalan-C_1_11.dll). This may cause your project to build incorrectly. To correct this, please make sure that $(OutDir), $(TargetName) and $(TargetExt) property values match the value specified in %(Link.OutputFile). C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Microsoft.CppBuild.targets(992,5): warning MSB8012: TargetName(AllInOne) does not match the Linker's OutputFile property value (Xalan-C_1_11). This may cause your project to build incorrectly. To correct this, please make sure that $(OutDir), $(TargetName) and $(TargetExt) property values match the value specified in %(Link.OutputFile). LINK : fatal error LNK1181: cannot open input file 'E:\xalan-c-1.11\c\Build\Win32\VC10\Debug\XalanMsgLib.lib' Build FAILED. Time Elapsed 00:00:14.78 It seems that the release build includes the .lib file from the debug directory. Any ideas on what might be causing this? I apologize if this is not the correct way to get in touch, I have not used JIRA before so wasn't sure if I should respond through that or via email. Thanks in advance for your assistance. Regards, Cameron D. Cameron DeHeer Vice President, Research & Development Blaze Systems Corporation Phone: 302.733.7236 Fax: 302.733.7248 Email: [email protected] Web: www.blazesystems.com Follow: -----Original Message----- From: [email protected] [mailto:[email protected]] Sent: Wednesday, May 06, 2015 12:22 AM To: [email protected] Subject: Xalan-C Integration Builds I am preparing integration builds of Xalan-C with current release of Xerces-C. Your experience with integration builds and testing is welcomed. Builds Completed Linux GNU Planned Unix Builds FreeBSD Microsoft Visual Studio VS 2003 (VS7.1) VS 2005 (VS8) VS 2008 (VS9) VS 2010 (VS10) VS 2012 (VS11) - Platform upgrade being created VS 2013 (VS12) - Platform upgrade being created Assistance with other platforms requested IBM AIX HP-UX MAC OSX Solaris Studio Sincerely, Steven J. Hathaway --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
