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
Port to Qt6 #3983
Comments
Did your GC 6.2QT build actually startup ? |
Yes, it started. It loaded the stored activities. It segfaulted after a few clicks. |
All Qt6 Refactor PRs are merged and master builds using Qt 6.2.4 (without R, Python and KML for now): We can start testing! |
Thank you Ale and so good to see Andreas’ work finally committed. |
Also need to get Andreas on the about box contributors list- this was a fantastic effort ! |
Hi Mark, I added Andreas to About Box in 1fb92d1 It looks like R/Python issues are similar to the ones fixed by Andreas, I think we can fix them following the same pattern, not sure about KML since it uses Boost, perhaps we could drop it. |
KML is dropped on Windows already I think? |
In official builds is dropped for macOS and no one has ever complained, it is included for Windows and Linux builds, but I don't know if it is used.
Agree, for now I will exclude it from my builds. |
Hi, |
I continued testing my Windows build using Qt 6.2.4 and it is working pretty well. Except for R/Python which I am planning to review later, all remaining charts in all 3 views are working and they look nice and responsive, even overlay widgets over VLC video is working to my surprise. |
No sorry. I changed jobs in January 2023 and I am not that deep in Qt any more. |
Nice one, was worried this was going to be much harder ! @andreasbuhr congratulations on your new job - albeit a year late :) |
Update: installing libkml-dev package on Ubuntu 22.04, enabling KML, and building master using Qt 6.2.4 is working, no additional changes required. |
Agree to drop it. Not sure if anybody uses this feature at all. With the
port to QT6 I also suggest to put the "WindowsSDK" to status "deprecated".
Am Di., 16. Jan. 2024 um 20:51 Uhr schrieb Alejandro Martinez <
***@***.***>:
… KML is dropped on Windows already I think?
In official builds KML is dropped on macOS, on Windows a libkml and Boost
version from https://github.com/GoldenCheetah/WindowsSDK are being used,
these were built by @Joern-R <https://github.com/Joern-R> long time ago,
IIRC.
Anyway I think it can be dropped, maybe we clean out in 3.7 since there
are lots of features almost no one uses
For now I am dropping it from my Windows builds, I will give it another
try when I start building on Linux.
—
Reply to this email directly, view it on GitHub
<#3983 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABZFBE3NOLMYUXPXGHTJBU3YO3K2ZAVCNFSM5BAM4RR2U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOBZGQ2DCMBRGA2Q>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
I think the signals are not connected, so no output occurs?
|
May be we can ask in users forum (?)
For now we are using some components in AppVeyor builds, since the ABI has not change they still useful. |
Yes, I should have qualified that affirmation, neither of R/Python charts I use and tested use GC Charts, only R Graphics Device/Web Chart. If we migrate to the new connect syntax, can this be detected at compile time instead of runtime? |
No worries at all- will look at it today |
The problem was caused by 466bdf1, after reversion (42aa241) Python Charts work with GC Charts when building with Qt6 |
Main pending issue for me now when building with Qt6 is Metric Trends chart not being correctly saved. They work initially (new Athlete or existing one used with Qt5 build) and also after View > Reset Layout / Charts > Reset to default, but they become blank after GoldenCheetah restart. Exporting the same chart (PMC) with the versions using Qt 5.15.2 and Qt 6.5.3 they differ only in LTMSettings, the former can be imported on either version and the second gives a blank chart on both. Supposedly the difference should come from: GoldenCheetah/src/Charts/GoldenCheetah.cpp Lines 970 to 976 in 573967f
This makes Qt6 builds unusable, except for testing purposes, I couldn't find the cause yet. |
Fixed by 4224fd1, solution was trivial, to find the cause, not so much :( |
Related to #3983, see discussion there for the rationale.
Hi, I just wanted to let you know about the current state of my efforts to build with Qt 6.2 (dev branch)
With all the changes in the pull requests I created, I just compiled and linked GoldenCheetah successfully with Qt 6.2. No testing has been done so far on any of the pull requests I created.
Next would be testing, modifying the patches to work with both Qt5 and Qt6, and sorting out some remaining issues. Most of the pull requests I created a very low risk, I assume. But some need more testing, most prominently the Qwt upgrade #3956 and the QRegExp->QRegularExpression transition #3960 .
Unfortunately, I will run out of time allocated for this project soon and won't be able to finish it. I'll have to stop working on GoldenCheetah and the open pull requests.
Anyway, I hope that the sequence of pull request generated will be of value to you and I will be around if you have any questions.
The text was updated successfully, but these errors were encountered: