-
-
Notifications
You must be signed in to change notification settings - Fork 395
ARM64 Build #2985
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: dev
Are you sure you want to change the base?
ARM64 Build #2985
Changes from all commits
2afebcb
6772f25
3ce5554
cea6560
e288be3
fd2eb28
4430fb5
cf10e9e
f4f5f40
99f19b2
20561ab
429e8d2
11f5249
73570fd
1d3f11b
f8c49a6
7088885
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,5 +1,6 @@ | ||
<Project> | ||
<PropertyGroup> | ||
<AccelerateBuildsInVisualStudio>true</AccelerateBuildsInVisualStudio> | ||
<RuntimeIdentifier>$(FlowRuntimeIdentifier)</RuntimeIdentifier> | ||
</PropertyGroup> | ||
</Project> |
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -25,7 +25,7 @@ assembly_info: | |
assembly_informational_version: $(flowVersion) | ||
|
||
image: Visual Studio 2022 | ||
platform: Any CPU | ||
platform: ARM64 | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Critical: AppVeyor does not support ARM64 builds Setting the platform to ARM64 in AppVeyor configuration is problematic as AppVeyor does not provide native ARM64 build support. This could lead to build failures or incorrect artifacts. As mentioned in the PR discussion, consider migrating to GitHub Actions for proper ARM64 build support. Consider:
|
||
configuration: Release | ||
before_build: | ||
- ps: | | ||
|
@@ -41,6 +41,7 @@ before_build: | |
build: | ||
project: Flow.Launcher.sln | ||
verbosity: minimal | ||
|
||
test_script: | ||
- dotnet test --no-build -c Release | ||
after_test: | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🛠️ Refactor suggestion
Cache keys need better invalidation
Two small issues reduce the usefulness of the new cache steps:
hashFiles('~/.dotnet/tools/**')
always returns an empty string because the path is outside the workspace. The key ends up aswindows-latest-dotnet-tools-
, so the cache never busts when tool versions change.*.csproj
; it misses other restore-affecting files such asDirectory.Packages.props
,packages.lock.json
, andglobal.json
.Suggested adjustments:
(The dotnet-tools key can also hash a repo file like
.github/workflows/dotnet.yml
if you prefer a content-based key.)These tweaks keep caches both reusable and correctly invalidated.
🤖 Prompt for AI Agents