Bug 1198013 - DevToolsModules now safe to call multiple times. r=miker
authorJ. Ryan Stinnett <jryans@gmail.com>
Fri, 03 Nov 2017 12:38:05 -0500
changeset 390350 f541c03beb5f
parent 390349 e96092796151
child 390351 d3ed36f4fb7a
push id32827
push userccoroiu@mozilla.com
push dateMon, 06 Nov 2017 23:02:00 +0000
treeherdermozilla-central@62aeebcc676e [default view] [failures only]
perfherder[talos] [build metrics] [platform microbench] (compared to previous push)
reviewersmiker
bugs1198013
milestone58.0a1
first release with
nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
last release without
nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
Bug 1198013 - DevToolsModules now safe to call multiple times. r=miker MozReview-Commit-ID: 2wg78JE6Cb7
devtools/templates.mozbuild
--- a/devtools/templates.mozbuild
+++ b/devtools/templates.mozbuild
@@ -9,21 +9,17 @@ def DevToolsModules(*modules):
     '''Installs JS modules at a resource:// path that corresponds directly to
     their source tree location.
 
     For this to work as intended, a moz.build file should be placed in each
     source directory which uses this template to install only the JS files in
     its own directory.  Subdirectories should use their own moz.build.
 
     By following this pattern, there's less magic to require() and resource://
-    paths, since they now match the source tree.
-
-    Currently `DevToolsModules` can only be called once per moz.build, so we
-    build a list manually above.  Bug 1198013 tracks fixing this to make it more
-    like other moz.build constructs.'''
+    paths, since they now match the source tree.'''
 
     for m in modules:
         if '/' in m:
             error('DevToolsModules must be used from the same directory as ' +
                   'the files to be installed.')
 
     # jar.mn manifest files are typically used to install files to chrome
     # locations.  Instead of doing this, use this DevToolsModules syntax via