249194 - xpidl in gecko-SDK doesn't run because missing DLL libIDL-0.6.dll

Status: RESOLVED WONTFIX

(Firefox Build System :: General, defect)

Description

[Peter Ross]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040206 Firefox/0.8
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040206 Firefox/0.8

When attempting to run xpidl from the gecko SDK for mozilla 1.7, xpidl fails
because it cannot find the DLL libIDL-0.6.dll

A search of the gecko-sdk directory reveals that this DLL doesn't exist in any
other directory.


Reproducible: Always
Steps to Reproduce:
1. Download
http://ftp.mozilla.org/pub/mozilla.org/mozilla/releases/mozilla1.7/gecko-sdk-i586-pc-msvc-1.7.zip

2. Unzip it.

3. Add the bin directory of the SDK to your path.

4. Run xpidl from the command prompt.
Actual Results:  
One gets an error message about the missing DLL libIDL-0.6.dll

Expected Results:  
xpidl should run with no errors, and I assume output a help message or something.

Comment 1

[Peter Ross]

Note that libIDL-0.6.dll doesn't exist in the gecko SDK for 1.8a either.

Comment 2

[David Bradley]

libidl as well glib-1.2.dll can be downloaded from the ftp site
ftp://ftp.mozilla.org/pub/mozilla.org/mozilla/libraries/win32/

Make sure you get the right version for your compiler. And for those not using
windows you can get these as regular packages. You can find more information
under your specific platform build instructions.

Maybe the installation instructions for the SDK needs to be updated to note
this. I'll leave this open for now, to verify this, but otherwise this is invalid.

Comment 3

[Peter Ross]

> Maybe the installation instructions for the SDK needs to be updated to note
> this. I'll leave this open for now, to verify this, but otherwise this is invalid.

Where are the installation instructions for the gecko SDK?

I can't find any instructions on either a web-page or in the binary package itself.

A simple README file in the binary release would be extremely useful.

Comment 4

[timeless]

this isn't a bug in xpidl. at best it's a bug in packaging or documentation.

Comment 5

[Christian :Biesinger (don't email me, ping me on IRC)]

bug 242870 would fix this

Comment 6

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

[Benjamin Smedberg]

This is real, and statically linking libidl/glib would be really nice.

Comment 8

[Timothee Besset]

agreed. or at least don't ship xpidl.exe in the SDK if you know it's broken anyway

Comment 9

[Makoto Kato [:m_kato]]

no longer use libIDL now since we switch to pyidl.