Dennis Nienhüser wrote: >> On Feb. 28, 2015, 4:06 p.m., Dennis Nienhüser wrote: >> > Makes sense generally. I do not have a system to test with at the >> > moment, but the problems with plugin loading sound like a must-fix >> > before shipping. Got some details on it? Do some plugins load, or none? >> > Is it related to the qt version? >> >> Rex Dieter wrote: >> Looks like I'm getting the same crashes without this patch, so >> probably unrelated. I'll file a bug (separately). >> >> Rex Dieter wrote: >> bug filed, https://bugs.kde.org/show_bug.cgi?id=344692 > > With this patch we get > - Qt4: libmarblewidget > - Qt5: libmarblewidget-qt5 > > Other options would be > - Qt4: libmarblewidget-qt4 > - Qt5: libmarblewidget > > and also > - Qt4: libmarblewidget-qt4 > - Qt5: libmarblewidget-qt5
I'd suggest not changing api for older apps (qt4), and only require a change for qt5 (and newer). It will be easier to get newer application developers to adapt to a change than to fix legacy applications. -- Rex _______________________________________________ Marble-devel mailing list [email protected] https://mail.kde.org/mailman/listinfo/marble-devel
