Closed Bug 408393 Opened 18 years ago Closed 16 years ago

pyxpcom mixes mscvr71 and msvcr80

Categories

(Other Applications Graveyard :: PyXPCOM, defect)

x86
Windows XP
defect
Not set
major

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: demomaker, Unassigned)

Details

User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 3.0.04506.30; .NET CLR 3.0.04506.590; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.04506.648; .NET CLR 3.5.21022) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b2) Gecko/2007121418 Minefield/3.0b2 pypcom uses official python distribution, hence 25 wich links against msvcr71 the current build uses msvcr80 (we build also using msvcr90) Reproducible: Always Steps to Reproduce: 1.build 2. 3. Actual Results: firefox loads msvcr71 when pyxpcom is loaded Expected Results: firefox doesn't mix msvc runtimes
Why shouldn't we mix runtimes? As long as each DLL only links with one runtime, I think we're safe...
Component: XPCOM → PyXPCOM
Product: Core → Other Applications
QA Contact: xpcom → pyxpcom
I agree with Benjamin - this should be fine. PythonExt (a build of PyXPCOM) extension for Windows mixes different versions of Visual Studio - 2005 for Firefox and 2008 for Python 2.6 - which does not appear to have any problems, it just requires that the appropriate Visual Studio C++ runtime(s) be installed (as PythonExt does not ship with any visual studio runtime).
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → INVALID
Product: Other Applications → Other Applications Graveyard
You need to log in before you can comment on or make changes to this bug.