gecko/devtools/templates.mozbuild
J. Ryan Stinnett 1654ec935e Bug 1203159 - Add resource:// mapping in all DevTools directories. r=glandium,ochameau
Add resource mapping jar.mn for DevTools.  The DevToolsModules template method
is modified to install the files in their new flattened add-on location.
2015-10-21 12:22:58 -05:00

36 lines
1.6 KiB
Python

# -*- Mode: python; c-basic-offset: 4; 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.
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.'''
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]