Current versions of mozilla-build ignore the current working directory
so use full path to mach. Due to path mangling issues copying from
vscode -> powershell -> msys-bash, I used a PowerShell fragment to
translate the path.
Differential Revision: https://phabricator.services.mozilla.com/D52084
--HG--
extra : moz-landing-system : lando
The ${workspaceRoot} variable was deprecated when multi-folder workspaces
were added to VSCode.
Depends on D52082
Differential Revision: https://phabricator.services.mozilla.com/D52083
--HG--
extra : moz-landing-system : lando
In the migration to the 2.0 format we seem to have dropped the base mach
command from a few of the defined tasks.
Depends on D52081
Differential Revision: https://phabricator.services.mozilla.com/D52082
--HG--
extra : moz-landing-system : lando
These options default to outer contexts so we don't need to repeat ourselves.
We were already setting the top level values anyways.
Differential Revision: https://phabricator.services.mozilla.com/D52081
--HG--
extra : moz-landing-system : lando
The original regex could match linux&mac outputs that look like:
`/[...]/ffmpeg/FFmpegVideoDecoder.cpp:315:6: error: expected expression`
However on Windows the same outputs have a different line&column format:
`c:/[...]/ffmpeg/FFmpegVideoDecoder.cpp(315,7): error: expected expression`
Differential Revision: https://phabricator.services.mozilla.com/D6442
--HG--
extra : moz-landing-system : lando
Most of the keywords used were deprecated and following versioning 0.1.0 even though it was marked as version 2.0.0.
This also defines build-binaries as the default task, so that Command-Shift-B doesn't need any confirmation.
MozReview-Commit-ID: UGDxqJYaFs
--HG--
extra : rebase_source : aafcc4839ec39d2d5998b2663fc0d24f10ec288e
Ted Campbell
Panos Astithas
Michael Cooper
Gerald Squelart
ExE Boss
Jean-Yves Avenard
Marco Bonardo