gecko-dev/devtools/templates.mozbuild
J. Ryan Stinnett 6bda31a889 Bug 1198013 - DevToolsModules now safe to call multiple times. r=miker
MozReview-Commit-ID: 2wg78JE6Cb7

--HG--
extra : rebase_source : d2c6b592fb096a4f65a4e4f7574816e4dd70f6e5
2017-11-03 12:38:05 -05:00

32 lines
1.4 KiB
Python

# -*- Mode: python; indent-tabs-mode: nil; tab-width: 40 -*-
# vim: set filetype=python:
# This Source Code Form is subject to the terms of the Mozilla Public
# License, v. 2.0. If a copy of the MPL was not distributed with this
# file, You can obtain one at http://mozilla.org/MPL/2.0/.
@template
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.'''
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
# moz.build files to do the installation so that we can enforce correct
# paths based on source tree location.
base = FINAL_TARGET_FILES.chrome.devtools.modules
for dir in RELATIVEDIR.split('/'):
base = base[dir]
base += [m for m in modules]