mirror of
https://gitlab.winehq.org/wine/wine-gecko.git
synced 2024-09-13 09:24:08 -07:00
Gecko engine for Wine
ab697fda8e
On Windows, IUknown::AddRef and IUnknown::Release are defined to return ULONG, which is defined as unsigned long. The existing code relies on the PR_BYTES_PER_LONG macro which is #defined in prtypes.h to always be 4 on Windows. If we remove the prtypes.h inclusion from nscore.h, in the places where prtypes.h is not included by other things, we will fall into the other path in the #ifdef condition which defines nsrefcnt to be unsigned int, which causes the signature of AddRef and Release to change, which results in linker errors. There are a couple of reasons why this change is correct: 1. On both Win32 and Win64, the size of the long type is 4 bytes, always. And prtypes.h doesn't detect the size of longs, it just assumes it, so this check is really a tautology. 2. If the size of the long type changes on Windows, sometime, the return value of AddRef and Release on Windows should change size as well in order to maintain binary compatibility with IUnknown, and before this change, the code would fail to hold that promise. --HG-- extra : rebase_source : 8333582b494aaca17c91cf35287a084083219050 |
||
|---|---|---|
| accessible | ||
| b2g | ||
| browser | ||
| build | ||
| caps | ||
| chrome | ||
| config | ||
| content | ||
| db/sqlite3 | ||
| dbm | ||
| docshell | ||
| dom | ||
| editor | ||
| embedding | ||
| extensions | ||
| gfx | ||
| hal | ||
| image | ||
| intl | ||
| ipc | ||
| js | ||
| layout | ||
| media | ||
| memory | ||
| mfbt | ||
| mobile | ||
| modules | ||
| mozglue | ||
| netwerk | ||
| nsprpub | ||
| other-licenses | ||
| parser | ||
| probes | ||
| profile | ||
| python | ||
| rdf | ||
| security | ||
| services | ||
| startupcache | ||
| storage | ||
| testing | ||
| toolkit | ||
| tools | ||
| uriloader | ||
| view | ||
| webapprt | ||
| widget | ||
| xpcom | ||
| xpfe | ||
| xulrunner | ||
| .gdbinit | ||
| .gitignore | ||
| .hgignore | ||
| .hgtags | ||
| aclocal.m4 | ||
| allmakefiles.sh | ||
| client.mk | ||
| client.py | ||
| configure.in | ||
| LEGAL | ||
| LICENSE | ||
| Makefile.in | ||
| mozilla-config.h.in | ||
| README.txt | ||
An explanation of the Mozilla Source Code Directory Structure and links to
project pages with documentation can be found at:
https://developer.mozilla.org/en/Mozilla_Source_Code_Directory_Structure
For information on how to build Mozilla from the source code, see:
http://developer.mozilla.org/en/docs/Build_Documentation
To have your bug fix / feature added to Mozilla, you should create a patch and
submit it to Bugzilla (https://bugzilla.mozilla.org). Instructions are at:
http://developer.mozilla.org/en/docs/Creating_a_patch
http://developer.mozilla.org/en/docs/Getting_your_patch_in_the_tree
If you have a question about developing Mozilla, and can't find the solution
on http://developer.mozilla.org, you can try asking your question in a
mozilla.* Usenet group, or on IRC at irc.mozilla.org. [The Mozilla news groups
are accessible on Google Groups, or news.mozilla.org with a NNTP reader.]
You can download nightly development builds from the Mozilla FTP server.
Keep in mind that nightly builds, which are used by Mozilla developers for
testing, may be buggy. Firefox nightlies, for example, can be found at:
ftp://ftp.mozilla.org/pub/firefox/nightly/latest-trunk/
- or -
http://nightly.mozilla.org/