Skip to content

Commit 1eba1a6

Browse files
authored
Include the built SDK location in README (#1651)
1 parent 05e2a03 commit 1eba1a6

File tree

1 file changed

+12
-0
lines changed

1 file changed

+12
-0
lines changed

README.md

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -17,6 +17,18 @@ The scripts are written for Bash and supported on macOS and Linux. See [Document
1717
./build.sh
1818
```
1919

20+
Once the build is successful, the built SDK tarball is placed at:
21+
22+
```
23+
artifacts/${ARCHITECTURE}/Release/dotnet-sdk-${SDK_VERSION}-${RUNTIME_ID}.tar.gz
24+
```
25+
26+
- `${ARCHITECTURE}` is your platform architecture (probably `x64`)
27+
- `${SDK_VERSION}` is the SDK version you are building
28+
- `${RUNTIME_ID}` is your OS name and architecture (something like `debian.9-x64` or `fedora.33-x64`)
29+
30+
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`.
31+
2032
## Goals
2133

2234
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.

0 commit comments

Comments
 (0)