-
Notifications
You must be signed in to change notification settings - Fork 8.1k
Closed
Labels
Issue-Questionideally support can be provided via other mechanisms, but sometimes folks do open an issue to get aideally support can be provided via other mechanisms, but sometimes folks do open an issue to get aResolution-AnsweredThe question is answered.The question is answered.
Description
Recently tried to compile PowerShell native Windows binaries and this last copy operation:
Lines 307 to 311 in d04fef4
| # Copy the binary to the packaging directory | |
| # NOTE: No PDB file; it's a resource-only DLL. | |
| # VS2017 puts this in $HOME\source | |
| $srcPath = [IO.Path]::Combine($HOME, "source", $Configuration, 'PowerShell.Core.Instrumentation.dll') | |
| Copy-Item -Path $srcPath -Destination $dstPath |
of
Start-BuildNativeWindowsBinaries failed due to absence of file in expected location.
For me file (result of compilation) was located in \src\PowerShell.Core.Instrumentation relative to repo root, but not in $HOME\source as stated in the comment. Is that error here or location was changed or is dependent of environment? Should build script be fixed or enhanced to cover other location of build artifacts?
Metadata
Metadata
Assignees
Labels
Issue-Questionideally support can be provided via other mechanisms, but sometimes folks do open an issue to get aideally support can be provided via other mechanisms, but sometimes folks do open an issue to get aResolution-AnsweredThe question is answered.The question is answered.