mirrors/dotnet-installer
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
dotnet-installer/Documentation/cli-prerequisites.md
Zlatko Knezevic bcc3094e01 Add pre-reqs doc to the repo (#2219) 
* Add pre-reqs doc to the repo 

This document outlines all of the native dependencies that are needed to run the CLI tools for Ubuntu, Windows, CentOS and OS X. 
As per chat with @leecow documentation does not need special approval to get merged. 

skip ci please

* Update cli-prerequisites.md

* Responding to PR feedback

I've changed the Ubuntu reqs to be the same as CentOS pre-reqs just with the correct package names. This seems like a more sane thing to do.

* Update cli-prerequisites.md
2016-04-08 13:55:26 -07:00

1.8 KiB
Raw Blame History

CLI native prerequisites

This document outlines the dependencies needed to run .NET Core CLI tools. Most of these dependencies are also .NET Core's general dependencies, so installing them will make sure that you can run applications written for .NET Core in general.

Windows dependencies

On Windows, the only dependency is the VC++ Redistributable. Depending on the version of Windows you are running on, the versions are changing.

Note: these dependencies are chained in the installer, you only need to install them manually if you are using the installer script (dotnet-install.sh or dotnet-install.ps1).

Ubuntu

Ubuntu distributions require the following libraries installed:

  • libunwind8
  • libunwind8-dev
  • gettext
  • libicu-dev
  • liblttng-ust-dev
  • libcurl4-openssl-dev
  • libssl-dev
  • uuid-dev
  • unzip

CentOS

CentOS distributions require the following libraries installed:

  • deltarpm
  • epel-release
  • unzip
  • libunwind
  • gettext
  • libcurl-devel
  • openssl-devel
  • zlib
  • libicu-devel

OS X

OS X requires the following libraries and versions installed:

  • libssl 1.1

Installing the dependencies

Please follow the recommended practices of each operating system in question. For Linux, we recommend using your package manager such as apt-get for Ubuntu and yum for CentOS. For OS X and upgrading the libssl, we recommend using Homebrew; if you do use it, do not forget the link phase you need to do at the end of install (brew link openssl --force).