Fix broken links in `docs/` (flutter/engine#54815)
Fixes some links that were broken as a part of https://github.com/flutter/engine/pull/53595, because it was pointed out on discord
Specifically, replaces `../../` with `https://github.com/flutter/flutter/blob/master/docs/` in the places that `grep` surfaced it.
[C++, Objective-C, Java style guides]: https://github.com/flutter/engine/blob/main/CONTRIBUTING.md#style
diff --git a/engine/src/flutter/docs/contributing/Compiling-the-engine.md b/engine/src/flutter/docs/contributing/Compiling-the-engine.md
index f209d34..e970754 100644
--- a/engine/src/flutter/docs/contributing/Compiling-the-engine.md
+++ b/engine/src/flutter/docs/contributing/Compiling-the-engine.md
@@ -60,7 +60,7 @@
> 💡 **TIP**: When developing on a Mac with ARM (M CPU), prefer `host_debug_unopt_arm64`.
>
> You can continue to use `host_debug_unopt` (required for Intel Macs), but the engine will be run under Rosetta
-> which may be slower. See [Developing with Flutter on Apple Silicon](../../platforms/desktop/macos/Developing-with-Flutter-on-Apple-Silicon.md)
+> which may be slower. See [Developing with Flutter on Apple Silicon](https://github.com/flutter/flutter/blob/master/docs/platforms/desktop/macos/Developing-with-Flutter-on-Apple-Silicon.md)
> for more information.
4. Build your executables
@@ -80,11 +80,11 @@
`android/AndroidManifest.xml` file for the Flutter app you are using
to test the engine.
-See [The flutter tool](../../tool/README.md) for instructions on how to use the `flutter` tool with a local engine.
+See [The flutter tool](https://github.com/flutter/flutter/blob/master/docs/tool/README.md) for instructions on how to use the `flutter` tool with a local engine.
You will typically use the `android_debug_unopt` build to debug the engine on a device, and
`android_debug_unopt_x64` to debug in on a simulator. Modifying dart sources in the engine will
require adding a `dependency_override` section in you app's `pubspec.yaml` as detailed
-[here](../../tool/README.md#using-a-locally-built-engine-with-the-flutter-tool).
+[here](https://github.com/flutter/flutter/blob/master/docs/tool/README.md#using-a-locally-built-engine-with-the-flutter-tool).
Note that if you use particular android or ios engine build, you will need to have corresponding
host build available next to it: if you use `android_debug_unopt`, you should have built `host_debug_unopt`,
@@ -133,11 +133,11 @@
5. `ninja -C out/ios_debug_unopt && ninja -C out/host_debug_unopt` to build all artifacts (use `out/ios_debug_sim_unopt` for Simulator).
-See [The flutter tool](../../tool/README.md) for instructions on how to use the `flutter` tool with a local engine.
+See [The flutter tool](https://github.com/flutter/flutter/blob/master/docs/tool/README.md) for instructions on how to use the `flutter` tool with a local engine.
You will typically use the `ios_debug_unopt` build to debug the engine on a device, and
`ios_debug_sim_unopt` to debug in on a simulator. Modifying dart sources in the engine will
require adding a `dependency_override` section in you app's `pubspec.yaml` as detailed
-[here](../../tool/README.md#using-a-locally-built-engine-with-the-flutter-tool).
+[here](https://github.com/flutter/flutter/blob/master/docs/tool/README.md#using-a-locally-built-engine-with-the-flutter-tool).
See also [instructions for debugging the engine in a Flutter app in Xcode](../Debugging-the-engine.md#debugging-ios-builds-with-xcode).
@@ -155,10 +155,10 @@
4. `ninja -C out/host_debug_unopt` to build a desktop unoptimized binary.
* If you skipped `--unoptimized`, use `ninja -C out/host_debug` instead.
-See [The flutter tool](../../tool/README.md) for instructions on how to use the `flutter` tool with a local engine.
+See [The flutter tool](https://github.com/flutter/flutter/blob/master/docs/tool/README.md) for instructions on how to use the `flutter` tool with a local engine.
You will typically use the `host_debug_unopt` build in this setup. Modifying dart sources in the engine will
require adding a `dependency_override` section in you app's `pubspec.yaml` as detailed
-[here](../../tool/README.md#using-a-locally-built-engine-with-the-flutter-tool).
+[here](https://github.com/flutter/flutter/blob/master/docs/tool/README.md#using-a-locally-built-engine-with-the-flutter-tool).
## Compiling for Windows
diff --git a/engine/src/flutter/docs/contributing/Setting-up-the-Engine-development-environment.md b/engine/src/flutter/docs/contributing/Setting-up-the-Engine-development-environment.md
index c4b7c7c..3935239 100644
--- a/engine/src/flutter/docs/contributing/Setting-up-the-Engine-development-environment.md
+++ b/engine/src/flutter/docs/contributing/Setting-up-the-Engine-development-environment.md
@@ -91,8 +91,8 @@
## Next steps:
* [Compiling the engine](Compiling-the-engine.md) explains how to actually get builds, now that you have the code.
- * [The flutter tool](../../tool/README.md) has a section explaining how to use custom engine builds.
- * [Signing commits](../../contributing/Signing-commits.md), to configure your environment to securely sign your commits.
+ * [The flutter tool](https://github.com/flutter/flutter/blob/master/docs/tool/README.md) has a section explaining how to use custom engine builds.
+ * [Signing commits](https://github.com/flutter/flutter/blob/master/docs/contributing/Signing-commits.md), to configure your environment to securely sign your commits.
## Editor autocomplete support
diff --git a/engine/src/flutter/docs/testing/Testing-the-engine.md b/engine/src/flutter/docs/testing/Testing-the-engine.md
index 4426f80..aba1ad8 100644
--- a/engine/src/flutter/docs/testing/Testing-the-engine.md
+++ b/engine/src/flutter/docs/testing/Testing-the-engine.md
@@ -329,7 +329,7 @@
Dart unit tests are executed during pre-submit on our CI system when submitting
PRs to the `flutter/engine` repository.
-_See also: [Flutter Test Fonts](../../contributing/testing/Flutter-Test-Fonts.md)_
+_See also: [Flutter Test Fonts](https://github.com/flutter/flutter/blob/master/docs/contributing/testing/Flutter-Test-Fonts.md)_
### Framework tests
