Message: The following issue has been closed.
--------------------------------------------------------------------- View the issue: http://issues.apache.org/jira/browse/XERCESC-494 Here is an overview of the issue: --------------------------------------------------------------------- Key: XERCESC-494 Summary: xerces-com, custom build step occasionally corrupts copy of dll Type: Bug Status: Closed Resolution: CANNOT REPRODUCE Project: Xerces-C++ Components: Build Versions: 1.6.0 Assignee: Reporter: Antony Bartlett Created: Mon, 10 Jun 2002 12:36 PM Updated: Tue, 19 Oct 2004 9:19 AM Environment: Operating System: Windows NT/2K Platform: PC Description: Occasionally after a build, I've found that the xerces-c_1_6_0.dll in Build\Win32\xml4com\ReleaseMinDependency is corrupt. This only happens very rarely, and for no apparent reason, so I regret I am unable to provide steps to re-produce the problem. Originally I was inclined to put this problem down to a faulty hard drive, but I've now seen it happen on two separate PCs. As far a I can see, this has got to be a problem with the "Copy" command in the custom build step - I suspect Visual Studio (I'm using 6.0) of implementing it's own "Copy" command (as, surely command.com is stable) In my own version of the source code, I have changed "Copy" to "XCopy". Because I can't reproduce the bug, I cannot vouch for "XCopy" being any better, but if two months pass without me posting any more on this subject, please assume that I am happy with this work around. Please also note that if the regsvr32 in the custom build step fails (for this, or any other reason), no build error is triggered, hence this kind of problem can go completely undetected! (until the software is run). The messages that do appear quickly scroll by if you're building more than just xerces-com (we only noticed it because we do a second regsvr32 from a make file as part of our automated build). --------------------------------------------------------------------- JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
