Andrew Schwartzmeyer
50093b202a
Copy the Travis CI badge for 10.11. It is the same badge, but it will fail if the build fails. I don't see a way to have separate badges, but this highlights that the platform is being tested.
2.0 KiB
Build PowerShell on OS X
This guide supplements the Linux instructions, as building on OS X is almost identical.
.NET Core (and by transitivity, us) only supports OS X 10.11, per CoreFX issue #7731.
Environment
You will want Homebrew, the missing package manager
for OS X. Once installed, follow the same instructions to download and
install a self-hosted copy of PowerShell on your OS X machine, and use
Start-PSBootstrap to install the dependencies.
The Start-PSBootstrap function does the following:
- Uses
brewto install CMake, OpenSSL, and GNU WGet - Downloads and installs the latest .NET CLI package
- Adds
/usr/local/share/dotnetto the process path
Please heed that last step. You may want to add the .NET CLI tool location to your path more permanently by adding it to your shell's profile.
error: Too many open files
Due to a bug in NuGet, the dotnet restore command will fail
without the limit increased. Run ulimit -n 2048 to fix this in your
session; add it your shell's profile to fix it permanently.
We cannot do this for you in in the build module due to #847.
Build using our module
Instead of installing the Ubuntu package of PowerShell, download the
pkg from our GitHub releases page using your browser, complete the
wizard, start a powershell session, and use Start-PSBuild from the
module.
The output directory will be slightly different because your runtime
identifier is different. PowerShell will be at
./src/Microsoft.PowerShell.CoreConsoleHost/bin/Linux/netstandardapp1.5/osx.10.11-x64/powershell,
or osx.10.10 depending on your operating system version. Note that
configration is still Linux because it would be silly to make yet
another separate configuration when it's used soley to work-around a
CLI issue.