GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
GeezerVison is showing github.com — build: Enable building for win-arm and win-arm64 by SteveL-MSFT · Pull Request #5524 · PowerShell/PowerShell Conversation
|
|
Waiting on mmi.dll to be published for win-arm and win-arm64 |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Confirmed that basic PSCore6 works on win-arm, I think we can merge this. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Aditya Patwardhan (@adityapatwardhan) hold off on merging this, looks like I need to build pwshplugin.dll for arm |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
!$env:PROCESSOR_ARCHITECTURE -match "arm"
!$env:PROCESSOR_ARCHITECTURE will be evaluated first in this case.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Will fix
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Once the changes to building |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Steve Lee (@SteveL-MSFT) please update here when |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Note that PR #5617 would also require |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
5acc38e to
2db001b
Compare
|
Have some paths hardcoded to validate build. Will update, but requires user to have VS2017 latest installed to build for win-arm. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
9c0d641 to
730336b
Compare
fix finding vs2017 dynamically
730336b to
384e38b
Compare
|
Verified pwrshplugin.dll works on both arm and arm64. Aditya Patwardhan (@adityapatwardhan) can you re-review this PR as I've made substantial changes for the native compilation? |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
…er than reg.exe so that error doesn't show on success fix formatting issue in cmake.defs
8f19ae4 to
28a9d8a
Compare
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
LGTM with minor comment.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
|
||
| # Clean up | ||
| Remove-Item .\$fileName | ||
| New-Item $regKey -Force |
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
New-Item $regKey -Force > $null
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Will change
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Dongbo Wang (@daxian-dbw) Can you have a look too? |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Aditya Patwardhan (@adityapatwardhan) Yes, will look tonight or first thing tomorrow morning. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Question: Steve Lee (@SteveL-MSFT) Is it going to be required to use VS2017 to build the plugin dll?
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Dongbo Wang (@daxian-dbw) The build worker image we use in AppVeyor is Visual Studio 2015. Do we need to update that?
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Actually we are using Visual Studio 2017 through the AppVeyor.yml
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
We don't build the native binaries in CI, so it shouldn't matter. Maybe we should switch to an image that doesn't have VS pre-installed.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Dongbo Wang (@daxian-dbw) VS2017 is required to build arm64
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Left a question comment.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
x64_arm and x64_arm64 seems weird to me. Why are we combining two architectures?
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
I'll add a comment. This is the form that the Visual Studio build environment expects for cross compilation. The first is the host and the second the target. VS supports x86_arm64, for example which I'm not supporting here.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Steve Lee (@SteveL-MSFT) Can you comment?
Sorry, something went wrong.
There was an error while loading. Please reload this page.
5540bb7 to
e0e5a02
Compare
address PR feedback
e0e5a02 to
34aa98b
Compare
|
Travis Plunk (@TravisEz13) Dongbo Wang (@daxian-dbw) Aditya Patwardhan (@adityapatwardhan) please review the change to the pwrshplugin config reader to address #5286 Decided to do that as part of this PR since I'm publishing a new drop to myget might as well do it once rather than twice. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Published https://powershell.myget.org/feed/powershell-core/package/nuget/psrp.windows/6.0.0-rc |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
A few non-blocking comments.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
| if (*slashIter != L'\\') | ||
| CloseHandle(dirHandle); | ||
| this->pathToPowerShellAssemblies = psHomeDir; | ||
| if (this->pathToPowerShellAssemblies.size() > 0) // Found a match |
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
It seems the size() > 0 check should be moved to before the CreateFileW call.
Or maybe the size() > 0 is not needed, because if getValueFromLine returns an empty string, I think CreateFileW will fail.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Wrote a small program to test this and an empty string does return an invalid handle. I can remove the size check.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
| slashIter--; | ||
| if (*slashIter != L'\\') | ||
| CloseHandle(dirHandle); | ||
| this->coreClrDirectory = this->getValueFromLine(line, coreClrDirTag); |
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Why calling this->getValueFromLine(line, coreClrDirTag); again instead of use coreClrDir?
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Mistake, should have been coreClrDir. Will fix.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
| if (*slashIter != L'\\') | ||
| CloseHandle(dirHandle); | ||
| this->coreClrDirectory = this->getValueFromLine(line, coreClrDirTag); | ||
| if (this->coreClrDirectory.size() > 0) // Found a match |
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Same comment about the size() check here.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
same as above
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Steve Lee (@SteveL-MSFT) Making those changes means we need to create a new |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
…HOME/source address PR feedback
|
Dongbo Wang (@daxian-dbw) yeah, I realize that. After this is merged, I'll create one called RC2. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Dongbo Wang (@daxian-dbw) Travis Plunk (@TravisEz13) Any ideas why WIP might be blocking this? |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
it hasn't run, edit the title and it will run. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
* enable win-arm and win-arm64 builds * fix using arm64 tools for build fix finding vs2017 dynamically * change install-powershellremoting.ps1 script to use reg provider rather than reg.exe so that error doesn't show on success fix formatting issue in cmake.defs * add check that path being read from config file is valid address PR feedback * fix copying of PowerShell.Core.Instrumentation as VS2017 puts it in $HOME/source address PR feedback
* enable win-arm and win-arm64 builds * fix using arm64 tools for build fix finding vs2017 dynamically * change install-powershellremoting.ps1 script to use reg provider rather than reg.exe so that error doesn't show on success fix formatting issue in cmake.defs * add check that path being read from config file is valid address PR feedback * fix copying of PowerShell.Core.Instrumentation as VS2017 puts it in $HOME/source address PR feedback
* enable win-arm and win-arm64 builds * fix using arm64 tools for build fix finding vs2017 dynamically * change install-powershellremoting.ps1 script to use reg provider rather than reg.exe so that error doesn't show on success fix formatting issue in cmake.defs * add check that path being read from config file is valid address PR feedback * fix copying of PowerShell.Core.Instrumentation as VS2017 puts it in $HOME/source address PR feedback
* enable win-arm and win-arm64 builds * fix using arm64 tools for build fix finding vs2017 dynamically * change install-powershellremoting.ps1 script to use reg provider rather than reg.exe so that error doesn't show on success fix formatting issue in cmake.defs * add check that path being read from config file is valid address PR feedback * fix copying of PowerShell.Core.Instrumentation as VS2017 puts it in $HOME/source address PR feedback
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
Pwrshplugin Config File Paths Should be Validated Before Use
There was an error while loading. Please reload this page.