ajtribick wrote:
...
particularly since I'm using a patched version of Qt (and would then have to determine exactly what the terms are for distributing the patch).
...
But wouldn't it be way easier (licensewise) to pull eventual patches into the code rather than patching a standard Qt4 library ?
Quote:
In order to get something I could make available as binaries, I'd probably have to further update Celestia SVN to use a Qt5 version that's compatible with MSVC 2015, so would not have to worry about the various issues with distributing patched Qt. If Fridger and collaborators are ok with me doing that I could take a look into making the updates and if it works, put code and relevant binaries somewhere, e.g. on GitHub, but obviously would not want it to be a distraction from upcoming Celestia.Sci releases.
How about a brilliant alternative option

: you just decide at last to join the
celestia.Sci dev team ?? There are so many things to do where you are a longstanding expert!
And -as I emphasized above, celestia.Sci is working very well with the recommended Qt5 libraries (Qt5.4.2 and Qt5.6.0). The Qt-based GUI code of .Sci is meanwhile widely different compared to Celestia.SVN. The cooperation of Qt5 and VS2013 (at least) is fine.
On the other hand, a mere porting of Celestia.SVN to Qt5 is really not difficult and follows a few clear-cut rules that are explained in the official Qt4->Qt5 porting documents... Of course, I would be not so happy if we'd start entering into something like a "multi fork" mode.
Cheers,
Fridger