Summary
- original guide (Alpine): https://learn.microsoft.com/en-us/dotnet/core/install/linux-scripted-manual#manual-install
- dl:
- install location: /usr/lib/dotnet
- path var: $PATH:/usr/lib/dotnet:/usr/lib/dotnet/tools # Background I really like Technitium DNS. It could be a better DHCP, but I can't complain. One major downside to it over other DNS tools like dnsmasq and unbound is that it's not targeted for router-ware like OpenWRT. However, this isn't really a limitation of Technitium, but rather .NET.
Dotnet doesn't target OpenWRT. However, it does target Alpine.
This is important, because a lot of packages for Alpine also work for OpenWRT.
Both OSes use musl instead of glibc, so the above sentence is kind of a general rule of thumb.
Notable occurrences where this rule isn't true include this problem that previously prevented you from running dotnet on OpenWRT: - see: https://github.com/dotnet/sdk/issues/24448
To check your musl compatibility, use ldd:
``` root@openwrt:~# ldd
musl libc (x86_64) Version 1.2.4 Dynamic Program Loader Usage: ldd [options] [--] pathname ```
Since OpenWRT 23.05.3 supports 1.2.4, we should be able to use Alpine's dotnet build, so let's give it a try.
The Alpine Guide (Adapted)
To install dotnet, we will be operating mostly out of the official guide for installing it manually with some modifications for OpenWRT: - see: https://learn.microsoft.com/en-us/dotnet/core/install/linux-scripted-manual#manual-install
First, we need to add the libicu dependency: opkg update && opkg install icu-full-data73
Second, we will download, extract and install the package to OpenWRT.
Before running (and adapting) the following on your router, it is recommended to download the tar.gz in a desktop environment such as Windows to verify the directory structure of the archive. Not all tar.gz files are the same. The following is a general script for downloading and installing tar.gz files on Linux systems, but it should be adapted for changes in the archive structure.
```
Change this if the structure of the tar.gz archive ever changes
FILES_TO_BE_INSTALLED="" # in a lot of archives, the install files are actaully in a subdir named after the package (package.tar.gz/package/ instead of package.tar.gz/*)
Download URL
Download and extract destination name
DOWNLOAD=dotnet
Install path:
INSTALL="/usr/lib/dotnet"
cd $(mktemp -d)
Download and extract:
wget $URL -O "$DOWNLOAD.tar.gz" mkdir $DOWNLOAD tar -xzvf "$DOWNLOAD.tar.gz" -C $DOWNLOAD
Install:
mkdir -p "$INSTALL" cp -R \ ./$DOWNLOAD/$FILES_TO_BE_INSTALLED \ $INSTALL
chmod +x any files as necessary
export PATH="$PATH:$INSTALL:$INSTALL/tools" echo "export PATH=\"\$PATH:$INSTALL:$INSTALL/tools\"" >> /etc/profile
dotnet --version ```
One thing to note is that the above script diverges a bit from the script in the official docs. Both my script and the microsoft script do the same thing with only one change, and that change is where we install dotnet to: "/usr/lib/dotnet" instead of "~/.dotnet".
The rest of it the script adds variables for easier script reading. Either script can be used. This is the general workflow I use to install linux software without a package manager, so this was a matter of copy and paste for me from prior installation work.
[link] [comments]