Skip to content

Document flags for building against system libraries #1939

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Dec 7, 2020
Merged

Document flags for building against system libraries #1939

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions Documentation/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand Down