| Summary: | Add MSVS 2019 support + fix nits | ||
|---|---|---|---|
| Product: | [Unmaintained] Craft | Reporter: | Ross Boylan <Ross.Boylan> |
| Component: | Core | Assignee: | Hannah von Reth <vonreth> |
| Status: | RESOLVED FIXED | ||
| Severity: | wishlist | CC: | julius.kuenzel, kare.sars, windows-bugs-null |
| Priority: | NOR | ||
| Version First Reported In: | master | ||
| Target Milestone: | --- | ||
| Platform: | Microsoft Windows | ||
| OS: | Microsoft Windows | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Ross Boylan
2019-03-19 20:11:08 UTC
After a lot of hacking, I have changes that might be appropriate. I still haven't a completely successful install, but the reasons appear unrelated. What is the best way to communicate the changes? They are in a branch in git in my local machine; I cloned from github, but I thought I read that is read-only. Some of the changes permit identification of pre-release versions of MSVS, which are otherwise invisible. Ross The preferred way to contribute (at the moment) is to do a review-request on phabricator.kde.org If you want to use the web-interface: https://phabricator.kde.org/differential/diff/create/ Upload the patch, select the proper repository and create the diff and describe the changes. Alternatively you can use arcanist (https://secure.phabricator.com/book/phabricator/article/arcanist/) See https://phabricator.kde.org/D19933 for the patch. Meanwhile we use MSVC2019 for Qt5 and MSVC2022 for Qt6 |