On 2018 M12 16, Sun 14:34:44 CET Thiago Macieira wrote:
> On Sunday, 16 December 2018 13:47:36 PST Alexander Neundorf wrote:
> > I also don't mind having moc6 etc. directly in bin/, instead of being
> > hidden in libexec. Well, I actually prefer if they are in bin/, because
> > there they are easy
On Sunday, 16 December 2018 13:47:36 PST Alexander Neundorf wrote:
> I also don't mind having moc6 etc. directly in bin/, instead of being hidden
> in libexec. Well, I actually prefer if they are in bin/, because there they
> are easy to find an run, and sometimes that's necessary during
On 2018 M11 14, Wed 03:43:03 CET Kevin Kofler wrote:
> Thiago Macieira wrote:
> > But I've just remembered that Designer loads plugins and those are quite
> > clearly tied to the Qt version. The file format is backwards compatible
> > and has remained so for a few years. It is possible that the
On Monday, 19 November 2018 11:42:48 PST Lisandro Damián Nicanor Pérez Meyer
wrote:
> b) If at some point we can agree it has been decided, is there any way I
> could start contributing code in order to achieve this? Maybe I should just
> wait until the new build system is on stage? something
El martes, 13 de noviembre de 2018 23:58:28 -03 Thiago Macieira escribió:
> On Tuesday, 13 November 2018 18:43:03 PST Kevin Kofler wrote:
[snip]
> > I think it would be much safer to just version everything.
> >
> > Just remember Assistant in Qt 4, where early 4.x releases shipped an
> >
On Tuesday, 13 November 2018 18:43:03 PST Kevin Kofler wrote:
> Thiago Macieira wrote:
> > But I've just remembered that Designer loads plugins and those are quite
> > clearly tied to the Qt version. The file format is backwards compatible
> > and has remained so for a few years. It is possible
Thiago Macieira wrote:
> But I've just remembered that Designer loads plugins and those are quite
> clearly tied to the Qt version. The file format is backwards compatible
> and has remained so for a few years. It is possible that the plugins
> generate the same XML regardless of version, but I
On Tuesday, 13 November 2018 15:19:58 PST Lisandro Damián Nicanor Pérez Meyer
wrote:
> Agreed, but this means that if an application is backwards compatible then
> it must be kept like that for all the Qt 6 lifetime. Is that feasible?
Yes. Assistant, Linguist, the D-Bus tools should be.
But
El martes, 13 de noviembre de 2018 19:56:29 -03 Thiago Macieira escribió:
> On Tuesday, 13 November 2018 13:43:20 PST Lisandro Damián Nicanor Pérez
> Meyer
> wrote:
> > a) Qt 5 and Qt 6 binaries should be coinstalable both in a developer
> > (libraries + binaries + build tools) and in a user's
On Tuesday, 13 November 2018 13:43:20 PST Lisandro Damián Nicanor Pérez Meyer
wrote:
> a) Qt 5 and Qt 6 binaries should be coinstalable both in a developer
> (libraries + binaries + build tools) and in a user's (only required
> libraries and binaries) perspective. For example: a user should not
10 matches
Mail list logo
