devtools/templates.mozbuild
author Andreas Tolfsen <ato@sny.no>
Wed, 03 Oct 2018 15:00:04 +0000
changeset 439423 7735290158111b061f91f88f7ff73ec357b5d251
parent 390350 f541c03beb5f21a380ec2146f37c609b708b5661
permissions -rw-r--r--
bug 1491288: geckodriver: release 0.23.0; r=whimboo Depends on D7301 Differential Revision: https://phabricator.services.mozilla.com/D7302

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