admin/PowerShell-PowerShell
1
0
Fork 0
mirror of https://github.com/PowerShell/PowerShell synced 2026-06-08 12:12:50 +00:00
Code Issues Packages Projects Releases Wiki Activity

[Feature] Clean up FullCLR related scripts/docs (#4580)

Browse Source
This commit is contained in:
Dongbo Wang
2017-08-16 12:07:45 -07:00
committed by Aditya Patwardhan
parent 3a8f923e03
commit feeb8e1d25
6 changed files with 45 additions and 459 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/building/internals.md
+2 -7
View File
@@ -6,14 +6,12 @@ The ultimate source of truth is the code in `.\build.psm1` that's getting execut
This document assumes that you can successfully build PowerShell from sources for your platform.
## Top directory
We are calling `dotnet` tool build for `$Top` directory
- `src\powershell-win-core` for CoreCLR on Windows.
- `src\powershell-unix` for CoreCLR on Linux and macOS.
- `src\powershell-win-full` for FullCLR builds (Windows only)
### Dummy dependencies
@@ -25,11 +23,8 @@ Dummy dependencies allows us to build just `$Top` folder, instead of building se
### Dummy dependencies rules
- If assembly is part of FullCLR build,
it should be listed as a dependency for FullCLR $Top folder (src\powershell-win-full)
- If assembly is part of CoreCLR build,
it should be listed as a dependency for $Top folder (src\powershell-unix or src\powershell-win-core)
If assembly is part of CoreCLR build,
it should be listed as a dependency for $Top folder (src\powershell-unix or src\powershell-win-core)
## Preliminary steps
docs/installation/windows.md
+1 -1
View File
@@ -126,7 +126,7 @@ Note that `New-PSSession` and `Enter-PSSession` invocations that do not specify
## Artifact Installation Instructions
We publish an archive with CoreCLR and FullCLR bits on every CI build with [AppVeyor][].
We publish an archive with CoreCLR bits on every CI build with [AppVeyor][].
[releases]: https://github.com/PowerShell/PowerShell/releases
[signing]: ../../tools/Sign-Package.ps1