devtools/templates.mozbuild
author Nick Alexander <nalexander@mozilla.com>
Thu, 11 Feb 2016 12:44:53 -0800
changeset 320453 864a07b26d9365d8556872bb48605b9abf5c3c39
parent 302099 5bf7a8f46f7b8c0258f07a8016cd080335693e3e
child 346136 3ec6380fca8207fa199693206a3ca24975bf9833
permissions -rw-r--r--
Bug 1248005 - Use com.stanfy.spoon:spoon-gradle-plugin:1.0.4. r=me MozReview-Commit-ID: 8hSOCq8XpZ7

# -*- 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]