To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=71828
------- Additional comments from [EMAIL PROTECTED] Thu Nov 23 01:18:54 -0800 2006 ------- I don't really understand much of the issues described here and in the links, manifests etc. I have never used manifest files. Is this simply the question of how to make sure that an OOo built with VS 2005 finds the msvcr80.dll at run-time? Why can't we do the same as in the "normal" case when building with VS .NET 2003, where we bundle msvcr71.dll and msvcp71.dll in the installer, and install them into the "program" folder of OOo? No manifests involved. Is there some legal or technical reason why it wouldn't work to do the same with msvcr80.dll (and msvcp80.dll)? --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- 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]
