maxmustermann/PowerShell
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Use one fragment per line in Markdown

Browse source
This commit is contained in:
Jason Shirk (POWERSHELL) 2016-07-21 15:50:04 -07:00
parent 082e35e009
commit 7b3ace4be4
3 changed files with 21 additions and 26 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
docs/building/internals.md
View file

@ -5,7 +5,7 @@ The purpose of this document is to explain build process **internals** with subt
This document is not by any means complete.
The ultimate source of truth is the code in `.\build.psm1` that's getting executed on the corresponding CI system.
This document assumes, that you can successfully build PowerShell from sources for your platform.
This document assumes that you can successfully build PowerShell from sources for your platform.
Top directory

36
docs/building/osx.md
View file

@ -12,10 +12,10 @@ CoreFX issue #[7731][].
Environment
===========
You will want [Homebrew](http://brew.sh/), 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.
You will want [Homebrew](http://brew.sh/), 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:
@ -24,15 +24,15 @@ The `Start-PSBootstrap` function does the following:
- Uninstalls any prior versions of .NET CLI
- Downloads and installs the latest .NET CLI 1.0.0-preview2 SDK to `~/.dotnet`
If you want to use `dotnet` outside of `Start-PSBuild`, add `~/.dotnet` to your
`PATH` environment variable.
If you want to use `dotnet` outside of `Start-PSBuild`,
add `~/.dotnet` to your `PATH` environment variable.
error: Too many open files
--------------------------
Due to a [bug][809] 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.
Due to a [bug][809] 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][].
@ -71,15 +71,11 @@ brew link --force openssl
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.
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/powershell/bin/Linux/netcoreapp1.0/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.
The output directory will be slightly different because your runtime identifier is different.
PowerShell will be at `./src/powershell/bin/Linux/netcoreapp1.0/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.

9
docs/building/windows-core.md
View file

@ -24,9 +24,8 @@ repository and `cd`ed into it.
.NET CLI
--------
We use the [.NET Command Line Interface][dotnet-cli] (`dotnet`) to
build PowerShell. The `Start-PSBootstrap` function will automatically
install it and add it to your path:
We use the [.NET Command Line Interface][dotnet-cli] (`dotnet`) to build PowerShell.
The `Start-PSBootstrap` function will automatically install it and add it to your path:
```powershell
Import-Module ./build.psm1
@ -40,8 +39,8 @@ Invoke-WebRequest -Uri https://raw.githubusercontent.com/dotnet/cli/rel/1.0.0/sc
./install.ps1
```
If you have any problems installing `dotnet`, please see their
[documentation][cli-docs].
If you have any problems installing `dotnet`,
please see their [documentation][cli-docs].
If you are using Windows 7, Windows Server 2008 or Windows Server 2012
you will also need to install