Fix simpleservo binary check on macos
<!-- Please describe your changes on the following line: -->
When compiling libsimpleservo on MacOS 11.5.2 I would get an error at the end of the process saying
```
Error running mach:
['build', '-d', '--libsimpleservo']
The error occurred in code that was called by the mach command. This is either
a bug in the called code itself or in the way that mach is calling it.
You can invoke |./mach busted| to check if this issue is already on file. If it
isn't, please use |./mach busted file| to report it. If |./mach busted| is
misbehaving, you can also inspect the dependencies of bug 1543241.
If filing a bug, please include the full output of mach, including this error
message.
The details of the failure are as follows:
servo.command_base.BuildNotFound: No Servo binary found. Perhaps you forgot to run `./mach build`?
File "/Users/yuriwitte/_HtmlTests/servo/python/servo/build_commands.py", line 734, in build
self.get_binary_path(release, dev, target=target, simpleservo=libsimpleservo)
File "/Users/yuriwitte/_HtmlTests/servo/python/servo/command_base.py", line 394, in get_binary_path
raise BuildNotFound('No Servo binary found.'
```
The binary is there, it's just that `get_binary_path` on `command_base.py` checks for a libsimpleservo **.so** instead of a **.dylib**. This pr fixes this check.
---
<!-- Thank you for contributing to Servo! Please replace each `[ ]` by `[X]` when the step is complete, and replace `___` with appropriate data: -->
- [X] `./mach build -d` does not report any errors
- [X] `./mach test-tidy` does not report any errors
- [ ] These changes fix: didn't find a specific issue for this, but these two are also related to file extensions on MacOS:
https://github.com/servo/servo/issues/27654https://github.com/servo/servo/issues/27318
<!-- Either: -->
- [ ] There are tests for these changes OR
- [X] These changes do not require tests because: they _are_ the tests I guess?
<!-- Also, please make sure that "Allow edits from maintainers" checkbox is checked, so that we can help you if you get stuck somewhere along the way.-->
<!-- Pull requests that do not address these steps are welcome, but they will require additional verification as part of the review process. -->
add NixOS support to mach and automatically re-launch mach in nix-shell
<!-- Please describe your changes on the following line: -->
This is a followup for #28454 which adds nixos support directly to mach, saving the user from typing `nix-shell` everytime
---
<!-- Thank you for contributing to Servo! Please replace each `[ ]` by `[X]` when the step is complete, and replace `___` with appropriate data: -->
- [ ] `./mach build -d` does not report any errors
- [ ] `./mach test-tidy` does not report any errors
- [ ] These changes fix #___ (GitHub issue number if applicable)
<!-- Either: -->
- [ ] There are tests for these changes OR
- [x] These changes do not require tests because they just extend mach
<!-- Also, please make sure that "Allow edits from maintainers" checkbox is checked, so that we can help you if you get stuck somewhere along the way.-->
<!-- Pull requests that do not address these steps are welcome, but they will require additional verification as part of the review process. -->
This includes a “Fix for changed rustc directory layout.” change:
https://github.com/japaric/xargo/blob/master/CHANGELOG.md#v0322---2020-07-29
We use Xargo to compile rust-std for Windows UWP targets.
I built `xargo.exe` on Taskcluster with task
https://community-tc.services.mozilla.com/tasks/IHwGq_ViRpGuomBx82XmpQ
created through https://community-tc.services.mozilla.com/tasks/create
with this definition:
```yaml
provisionerId: proj-servo
workerType: win2016
schedulerId: taskcluster-github
created: '2021-01-25T19:39:29.952Z'
deadline: '2021-01-26T19:39:29.952Z'
expires: '2022-01-25T19:39:29.952Z'
payload:
mounts:
- file: rustup-init.exe
content:
url: https://win.rustup.rs/x86_64
command:
- '%HOMEDRIVE%%HOMEPATH%\rustup-init.exe --profile=minimal -y'
- set PATH=%HOMEDRIVE%%HOMEPATH%\.cargo\bin;%PATH%
- |-
cargo install xargo --version 0.3.22
copy %HOMEDRIVE%%HOMEPATH%\.cargo\bin\xargo.exe .
artifacts:
- name: public/xargo.exe
path: xargo.exe
type: file
expires: '2022-01-25T15:07:23.782706Z'
maxRunTime: 5400
metadata:
name: Xargo build for Windows
description: ''
owner: infra@servo.org
source: https://community-tc.services.mozilla.com/tasks/create
```
(Note the "update timestamps" button in the bottom-right menu.)
I then created a ZIP file that contains `xargo-v0.3.22/xargo.exe` and
uploaded it with `aws s3 cp ./xargo-v0.3.22.zip s3://servo-deps-2/msvc-deps/`
where our build system can find it.
