From d7ffa9478b7e9583f7a938de744d4172e47655c1 Mon Sep 17 00:00:00 2001 From: Omair Majid Date: Fri, 4 Dec 2020 16:49:05 -0500 Subject: [PATCH] Document flags for building against system libraries Fixes: #1884 --- Documentation/README.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/Documentation/README.md b/Documentation/README.md index e237c2db1b..b17e88dd42 100644 --- a/Documentation/README.md +++ b/Documentation/README.md @@ -36,6 +36,12 @@ For example, building a 3.1.105 SDK on an x64 (aka x86\_64) platform running Fed If you are interested in "installing" this SDK system wide or making a Linux package out of the SDK, please see [Packaging and Installation](packaging-installation.md). +`./build.{cmd|sh}` accepts a number of parameters to control the build. + +- `/p:UseSystemLibraries=true` or `/p:UseSystemLibraries=false` can be used to explicitly link against the system libraries. `false` will make it `dlopen` any required libraries at runtime. + +- `/p:UseSystemLibunwind=true` or `/p:UseSystemLibunwind=false` can be used to use either the system libunwind or the version of libunwind included in the dotnet/runtime repository. Defaults to the value of `UseSystemLibraries`. + ## Building one repo By default we build the cli and its dependencies but the default root repository to build can be passed in. For example, if you just want to build the .NET Core Runtime, you would just build the `core-setup` repo and its dependencies: