-
-
Notifications
You must be signed in to change notification settings - Fork 838
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
First build of Stellarium for Windows on ARM on AppVeyor #3447
Conversation
A few questions:
|
I don't think I have access to that part / tab? I can't find it because I'm not part of the project? |
@@ -39,7 +39,7 @@ environment: | |||
qtver: 6.5 | |||
qtbin: msvc2019_arm64 | |||
msvcname: Visual Studio 17 2022 | |||
cmake_args: -A ARM64 -DQT_HOST_PATH=C:/Qt/6.5/msvc2019_64 -DENABLE_SPOUT=OFF -DENABLE_QTWEBENGINE=OFF | |||
cmake_args: -A ARM64 -DQT_HOST_PATH=C:/Qt/6.5/msvc2019_64 -DQT_PATHS=C:/Qt/6.5/msvc2019_arm64/bin/qtpaths.bat -DENABLE_SPOUT=OFF -DENABLE_QTWEBENGINE=OFF |
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.
I guess C:/Qt/6.5/msvc2019_arm64/bin/qtpaths.bat
should be run for ARM64 environment.
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.
Not, not run, it's not a batch file to set environment variables like vsvars.bat.
I can show you what the file is if you are curious. But x-compilation is a bit complicated, that's why we need both Qt compiled for x64 and for ARM64 at the same machine at the same time.
It uses qmake, moc, rcc, from the HOST (x64), but when windeployqt copies files it needs to be the TARGET (ARM64) ones. qtpaths tells windeployqt which folder to use when copying the files.
Hmm... please see https://ci.appveyor.com/project/alex-w/stellarium/history |
|
It is supposed to be empty. As in: no parameters? AppVeyor does not accept that? I can change to |
See https://github.com/leadedge/Spout2 or http://spout.zeal.co/
You can add keyword |
|
I can't do that yet. I don't want to try to build the installer yet, there's more work after this PR regarding creating the installer |
I'm looking at https://ci.appveyor.com/project/alex-w/stellarium/builds/48199679 |
Ahh, VS2017 does not support passing |
Using |
No, I mean, how can I download the files from the AppVeyor build without publishing anything! I know how to check if a file is ARM64. I use |
See |
Allright. I'll wait until all the builds are green then I'll add another Pull Request to deal with publishing! |
All green with https://ci.appveyor.com/project/alex-w/stellarium/builds/48200516 |
But you can do it within this PR |
The changes are unrelated, are you sure you don't prefer to have the builds working in a PR and dealing with publushing in a separate PR? The PR will get too big, atomic unrelated changes per PR are better. |
Hello @hmartinez82! Please check the fresh version (development snapshot) of Stellarium: |
Hello @hmartinez82! Please check the latest stable version of Stellarium: |
Description
I had absolutely no idea that AppVeyor had Qt 6 for Windows on ARM already compiled and ready for use for x-compilation in its base images!! This makes things orders of magnitude easier! We don't even have to use MSYS2 to build Stellarium for Windows on ARM!
This is a first, build only, no deployment of Windows on ARM 64 binaries.
No QtWebEngine because Qt doesn't build that for x-compilation yet. And no Spout either since there's no precompiled Spout for ARM64.
Partially fixes #2962 and #1436
Type of change
How Has This Been Tested?
No unit tests run because AppVeyor does not provide Windows on ARM runners. We can only x-compile for now from x64 for ARM64.
Checklist: