From 91b84848bc8779326c11fb24317e0df2d05ac188 Mon Sep 17 00:00:00 2001 From: Carlos Sanchez Lopez <1175054+carlossanlop@users.noreply.github.com> Date: Wed, 11 Sep 2019 11:15:03 -0700 Subject: [PATCH] Fixing mono/linker doc link --- samples/linker-instructions-advanced.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/samples/linker-instructions-advanced.md b/samples/linker-instructions-advanced.md index 0db2cc67..c6b84fca 100644 --- a/samples/linker-instructions-advanced.md +++ b/samples/linker-instructions-advanced.md @@ -80,4 +80,4 @@ The ILLink task can be invoked just like any other msbuild task. For example, it ``` -Here, the ItemGroups `AssemblyFilesToLink`, `LinkerRootAssemblies`, and `LinkerRootDescriptors` would be defined elsewhere in the project, and the `ExtraArgs` input consists of flags described in the [mono/linker documentation](https://github.com/mono/linker/blob/master/linker/README). By default, the `RootAssemblyNames` are rooted as if illink had been called with `-a RootAssemblyName1 -a RootAssemblyName2` ... as arguments, but this behavior is subject to change and should not be relied upon. +Here, the ItemGroups `AssemblyFilesToLink`, `LinkerRootAssemblies`, and `LinkerRootDescriptors` would be defined elsewhere in the project, and the `ExtraArgs` input consists of flags described in the [mono/linker documentation](https://github.com/mono/linker/blob/master/README.md). By default, the `RootAssemblyNames` are rooted as if illink had been called with `-a RootAssemblyName1 -a RootAssemblyName2` ... as arguments, but this behavior is subject to change and should not be relied upon.