To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=105603
                 Issue #|105603
                 Summary|VC80 runtime for prebuilt Mozilla bits for 3.2
               Component|tools
                 Version|DEV300m58
                Platform|PC
                     URL|
              OS/Version|Windows, all
                  Status|UNCONFIRMED
       Status whiteboard|
                Keywords|
              Resolution|
              Issue type|PATCH
                Priority|P3
            Subcomponent|configure
             Assigned to|rene
             Reported by|tml





------- Additional comments from [email protected] Mon Oct  5 07:50:39 +0000 
2009 -------
The prebuilt Mozilla Windows binaries for OOo 3.2 at
http://tools.openoffice.org/moz_prebuild/OOo3.2/index.html are built against the
VC80 runtime (msvcr80.dll), but they don't contain embedded manifests, nor do
they come with external .manifest files. Shouldn't they?

Isn't the VC80 runtime like the VC90 one (which OOo itself is built against),
that it should not be installed in the system32 folder, and not somewhere in
PATH either, but instead be present only in the side-by-side assembly 
repository?

The configure.in, scp2 and solenv infrastructure does not contain any code, as
far as I could see, to make sure that the merge module for the VC80 runtime is
present and gets included in the installer. (If that would be the correct thing
to do?)

I think the solution would be to either build the Mozilla DLLs with MSVS9, too,
so that they thus would use the same VC90 runtime as OOo itself does, or then
add the necessary code to configure.in, scp2 etc to take care of the VC80
runtime, too.

---------------------------------------------------------------------
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]

Reply via email to