Tony Mountifield
Tony Mountifield
That suggests that your jamulus binary was built with Qt 6.5.2 embedded, rather than using dynamic linking. Check what shared libs it is pulling in by using: `ldd $(which jamulus)`
> > That suggests that your jamulus binary was built with Qt 6.5.2 embedded, rather than using dynamic linking > > Since `QT_VERSION_STR` comes from the header at compile time...
I have a simple solution for this, which is in my queue for raising a PR soon.
It is more than just the registry. If you want ASIO and Jack versions to co-exist on one system, you will need also to either give them different app names...
> That's bad. Does the same happen in the server where a comparable button is? I will look more closely. Checking the various dev versions I have installed, it seems...
It appears ok in the artifact I downloaded from #3260. I'll check again once that has been merged and built with Qt 5.15.2.
> Hmm... they're not identical. The button in the server is larger and the glyph in the client is bold... (And, of course, different fonts between Linux and Windows. Probably...
> If we've no MacOS developers, we may have to drop MacOS support... I can look at it after my holiday.
> Maybe it makes sense to delay this after the TCP support for more compatibility The TCP support is quite an involved project, and there are simpler things I want...
Hmm, that's frustrating. I think dropping translations would be a poorer choice than dropping support for archaic versions of macOS. How about if we went to Qt 5.12 first then,...