From 1eba1a673a160ae4635270fdcf823da4bfe66d3d Mon Sep 17 00:00:00 2001 From: Omair Majid Date: Thu, 9 Jul 2020 14:55:21 -0400 Subject: [PATCH] Include the built SDK location in README (#1651) --- README.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/README.md b/README.md index 3f4c99f921..fec42fa8a7 100644 --- a/README.md +++ b/README.md @@ -17,6 +17,18 @@ The scripts are written for Bash and supported on macOS and Linux. See [Document ./build.sh ``` +Once the build is successful, the built SDK tarball is placed at: + +``` +artifacts/${ARCHITECTURE}/Release/dotnet-sdk-${SDK_VERSION}-${RUNTIME_ID}.tar.gz +``` + +- `${ARCHITECTURE}` is your platform architecture (probably `x64`) +- `${SDK_VERSION}` is the SDK version you are building +- `${RUNTIME_ID}` is your OS name and architecture (something like `debian.9-x64` or `fedora.33-x64`) + +For example, building a 3.1.105 SDK on an x64 (aka x86\_64) platform running Fedora 32 will produce `artifacts/x64/Release/dotnet-sdk-3.1.105-fedora.32-x64.tar.gz`. + ## Goals The key goal of this repository is to satisfy the official packaging rules of commonly used Linux distributions, such as [Fedora](https://fedoraproject.org/wiki/Packaging:Guidelines) and [Debian](https://www.debian.org/doc/manuals/maint-guide/build.en.html). Many Linux distributions have similar rules. These rules tend to have two main principles: consistent reproducibility, and source code for everything.