Update the powershell executable location in building guide docs (#7205)
This commit is contained in:
parent
839ecb866f
commit
c83e0e8462
|
@ -71,7 +71,7 @@ Start-PSBuild
|
|||
Congratulations! If everything went right, PowerShell is now built.
|
||||
The `Start-PSBuild` script will output the location of the executable:
|
||||
|
||||
`./src/powershell-unix/bin/Linux/netcoreapp2.0/linux-x64/publish/pwsh`.
|
||||
`./src/powershell-unix/bin/Debug/netcoreapp2.1/linux-x64/publish/pwsh`.
|
||||
|
||||
You should now be running the PowerShell Core that you just built, if your run the above executable.
|
||||
You can run our cross-platform Pester tests with `Start-PSPester`, and our xUnit tests with `Start-PSxUnit`.
|
||||
|
|
|
@ -36,5 +36,4 @@ We cannot do this for you in the build module due to #[847][].
|
|||
|
||||
Start a PowerShell session by running `pwsh`, and then use `Start-PSBuild` from the module.
|
||||
|
||||
After building, PowerShell will be at `./src/powershell-unix/bin/Linux/netcoreapp2.0/osx-x64/publish/powershell`.
|
||||
Note that configuration is still `Linux`.
|
||||
After building, PowerShell will be at `./src/powershell-unix/bin/Debug/netcoreapp2.1/osx-x64/publish/pwsh`.
|
||||
|
|
|
@ -58,11 +58,11 @@ Import-Module ./build.psm1
|
|||
Start-PSBuild
|
||||
```
|
||||
|
||||
Congratulations! If everything went right, PowerShell is now built and executable as `./src/powershell-win-core/bin/Debug/netcoreapp2.0/win7-x64/publish/pwsh`.
|
||||
Congratulations! If everything went right, PowerShell is now built and executable as `./src/powershell-win-core/bin/Debug/netcoreapp2.1/win7-x64/publish/pwsh.exe`.
|
||||
|
||||
This location is of the form `./[project]/bin/[configuration]/[framework]/[rid]/publish/[binary name]`,
|
||||
and our project is `powershell`, configuration is `Debug` by default,
|
||||
framework is `netcoreapp2.0`, runtime identifier is `win7-x64` by default,
|
||||
framework is `netcoreapp2.1`, runtime identifier is `win7-x64` by default,
|
||||
and binary name is `pwsh`.
|
||||
The function `Get-PSOutput` will return the path to the executable;
|
||||
thus you can execute the development copy via `& (Get-PSOutput)`.
|
||||
|
|
Loading…
Reference in a new issue