296711 - gdi+ not found when run on different machine than the one that built it

Status: RESOLVED EXPIRED

(Toolkit Graveyard :: XULRunner, defect)

Description

[Ed Anuff]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050601 Firefox/1.0+
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050601 Firefox/1.0+

Xulrunner built on Windows XP box with following settings in .mozconfig:

export MOZILLA_OFFICIAL=1
mk_add_options MOZILLA_OFFICIAL=1
ac_add_options --enable-application=xulrunner
ac_add_options --enable-svg

ac_add_options --enable-optimize
ac_add_options --disable-debug
ac_add_options --disable-tests 

GLIB_PREFIX=c:/vc71
LIBIDL_PREFIX=c:/vc71

I'm following the standard instructions for Windows build of mozilla.

gdiplus.dll is present on the target machine.

Reproducible: Always

Steps to Reproduce:
1. Build xulrunner with the above .mozconfig
2. Move dist to a different machine (tried an XP SP2 box and a Win2K box)
3. Run xulrunner app


Actual Results:  
"gdi+ is not installed" alert appears


I've tried putting a copy of gdiplus.dll in just about every place possible on
both target machines tested.  

Using Sysinternals Process Explorer
(http://www.sysinternals.com/Utilities/ProcessExplorer.html), I can see that
xulrunner appears to have actually loaded the gdiplus.dll, which may mean that
the error message is being incorrectly triggered rather than the dll not, in
fact, being found.

An install of Deer Park on the same machines in question runs fine and is able
to use SVG via GDI+, apparently finding gdiplus.dll ok, so it's something unique
to the xulrunner build.

Comment 1

[Jean-Marc Desperrier]

And could you try a debug build ? That would make it easy for you to find more
info on what happens exactly.

Comment 2

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 3

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.