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

Make Microsoft feeds the default (#24098)

Browse Source
This commit is contained in:
Travis Plunk
2024-07-31 19:41:15 +00:00
committed by GitHub
parent 5eb9ae43f5
commit 8a8f2d4b23
13 changed files with 114 additions and 49 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/building/linux.md
+3 -3
View File
@@ -12,7 +12,7 @@ The build module works on a best-effort basis for other distributions.
Using Git requires it to be set up correctly;
refer to the [Working with the PowerShell Repository](../git/README.md),
[README](../../README.md), and [Contributing Guidelines](../../.github/CONTRIBUTING.md).
[Readme](../../README.md), and [Contributing Guidelines](../../.github/CONTRIBUTING.md).
**This guide assumes that you have recursively cloned the PowerShell repository and `cd`ed into it.**
@@ -63,7 +63,7 @@ If you have followed the toolchain setup section above, you should have PowerShe
```powershell
Import-Module ./build.psm1
Start-PSBuild
Start-PSBuild -UseNuGetOrg
```
Congratulations! If everything went right, PowerShell is now built.
@@ -72,4 +72,4 @@ The `Start-PSBuild` script will output the location of the executable:
`./src/powershell-unix/bin/Debug/net6.0/linux-x64/publish/pwsh`.
You should now be running the PowerShell Core that you just built, if you run the above executable.
You can run our cross-platform Pester tests with `Start-PSPester`, and our xUnit tests with `Start-PSxUnit`.
You can run our cross-platform Pester tests with `Start-PSPester -UseNuGetOrg`, and our xUnit tests with `Start-PSxUnit`.
docs/building/macos.md
+1 -1
View File
@@ -34,6 +34,6 @@ We cannot do this for you in the build module due to #[847][].
## Build using our module
Start a PowerShell session by running `pwsh`, and then use `Start-PSBuild` from the module.
Start a PowerShell session by running `pwsh`, and then use `Start-PSBuild -UseNuGetOrg` from the module.
After building, PowerShell will be at `./src/powershell-unix/bin/Debug/net6.0/osx-x64/publish/pwsh`.
docs/building/windows-core.md
+3 -3
View File
@@ -11,7 +11,7 @@ R2, though they should work anywhere the dependencies work.
### Git Setup
Using Git requires it to be setup correctly; refer to the
[README](../../README.md) and
[Readme](../../README.md) and
[Contributing Guidelines](../../.github/CONTRIBUTING.md).
This guide assumes that you have recursively cloned the PowerShell repository and `cd`ed into it.
@@ -56,7 +56,7 @@ We maintain a [PowerShell module](../../build.psm1) with the function `Start-PSB
```powershell
Import-Module ./build.psm1
Start-PSBuild -Clean -PSModuleRestore
Start-PSBuild -Clean -PSModuleRestore -UseNuGetOrg
```
Congratulations! If everything went right, PowerShell is now built and executable as `./src/powershell-win-core/bin/Debug/net6.0/win7-x64/publish/pwsh.exe`.
@@ -77,7 +77,7 @@ You can run our cross-platform Pester tests with `Start-PSPester`.
```powershell
Import-Module ./build.psm1
Start-PSPester
Start-PSPester -UseNuGetOrg
```
## Building in Visual Studio