Bug 1266995 - Remove wrong docs about XPIDL_MODULE defaulting to MODULE; r?glandium draft
authorGregory Szorc <gps@mozilla.com>
Sat, 23 Apr 2016 11:21:11 -0700
changeset 355703 1fe1404146f94749ddaec0e7d36f2621c049d09b
parent 355702 558ce8195eb113f0c392985d4a1ea3bc990b9e23
child 355704 d3501b4c6b7a1db748a93138945835f9e5015b05
push id16364
push usergszorc@mozilla.com
push dateSun, 24 Apr 2016 18:56:23 +0000
reviewersglandium
bugs1266995
milestone48.0a1
Bug 1266995 - Remove wrong docs about XPIDL_MODULE defaulting to MODULE; r?glandium I can't find the code that makes this true. I don't think this has been true since the XPIDL rules code was ported from make gunk to mostly Python a few years ago. MozReview-Commit-ID: HZpuJ8EX9A6
python/mozbuild/mozbuild/frontend/context.py
--- a/python/mozbuild/mozbuild/frontend/context.py
+++ b/python/mozbuild/mozbuild/frontend/context.py
@@ -1417,18 +1417,17 @@ VARIABLES = {
         Entries must be files that exist. Entries are almost certainly ``.idl``
         files.
         """),
 
     'XPIDL_MODULE': (unicode, unicode,
         """XPCOM Interface Definition Module Name.
 
         This is the name of the ``.xpt`` file that is created by linking
-        ``XPIDL_SOURCES`` together. If unspecified, it defaults to be the same
-        as ``MODULE``.
+        ``XPIDL_SOURCES`` together.
         """),
 
     'XPIDL_NO_MANIFEST': (bool, bool,
         """Indicate that the XPIDL module should not be added to a manifest.
 
         This flag exists primarily to prevent test-only XPIDL modules from being
         added to the application's chrome manifest. Most XPIDL modules should
         not use this flag.