forked from mirrors/gecko-dev
Bug 1746286: Don't recommend adding "Mach" to your PATH r=ahal
This can cause issues when Mach from sourcetree A fails when used in sourcetree B because an expected file is missing. Differential Revision: https://phabricator.services.mozilla.com/D133951
This commit is contained in:
parent
15bea1de0d
commit
168707a1e5
2 changed files with 1 additions and 11 deletions
|
|
@ -31,8 +31,7 @@ The preferred method, is using the
|
|||
:ref:`mach` command-line tool to run the
|
||||
debugger, which can bypass several optional defaults. Use "mach help
|
||||
run" to get more details. If inside the source directory, you would use
|
||||
"./mach". If you have previously :ref:`added mach to your path <Adding_mach_to_your_shell>`,
|
||||
then just use "mach". Please note that :ref:`mach is aware of mozconfigs <mach_and_mozconfigs>`.
|
||||
"./mach". Please note that :ref:`mach is aware of mozconfigs <mach_and_mozconfigs>`.
|
||||
|
||||
.. code:: bash
|
||||
|
||||
|
|
|
|||
|
|
@ -146,14 +146,5 @@ The settings file follows the ``ini`` format, e.g:
|
|||
[try]
|
||||
default = fuzzy
|
||||
|
||||
.. _Adding_mach_to_your_shell:
|
||||
|
||||
Adding ``mach`` to your ``PATH``
|
||||
--------------------------------
|
||||
|
||||
If you don't like having to type ``./mach``, you can add your source directory
|
||||
to your ``PATH``. DO NOT copy the script to a directory already in your
|
||||
``PATH``.
|
||||
|
||||
|
||||
.. _bash completion: https://searchfox.org/mozilla-central/source/python/mach/bash-completion.sh
|
||||
|
|
|
|||
Loading…
Reference in a new issue