gecko-dev/devtools/templates.mozbuild
Tom Tromey 5538d692d3 Bug 1286877 - do not set c-basic-offset for python-mode; r=gps
This removes the unnecessary setting of c-basic-offset from all
python-mode files.

This was automatically generated using

    perl -pi -e 's/; *c-basic-offset: *[0-9]+//'

... on the affected files.

The bulk of these files are moz.build files but there a few others as
well.

MozReview-Commit-ID: 2pPf3DEiZqx

--HG--
extra : rebase_source : 0a7dcac80b924174a2c429b093791148ea6ac204
2016-07-14 10:16:42 -06:00

36 lines
1.5 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.
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]