Hi,
Today I published all modules from the Qt5 Beta1 for packaged Precise
and Quantal : https://launchpad.net/~canonical-qt5-edgers/+archive/qt5-daily
The packages are for i386, amd64 and armhf architectures.
Each module is a single installable package and they just simple install
under the /o
Forwarded from mingw-w64 list:
> niXman:
> I, though, would recommend you to use SJLJ for 32 and 64 bit, in order
> not to have multiple ways for exceptions handling. This can cause some
> differences in the behavior of the programs. Besides, SJLJ for
> win32/win64 currently does not contain any k
Jonathan Liu:
> Also, GCC 4.7.x has problem where it runs out of
> memory in some cases (https://bugs.archlinux.org/task/28329).
I just checked for the i686 and x86_64 - all ok.
--
Regards,
niXman
___
Dual-target(32 & 64 bit) MinGW compilers for 3
On domingo, 9 de setembro de 2012 13.25.29, Boudewijn Rempt wrote:
> The solution for a bug can never be to wilfully break existing applications!
> What can I as an application developer depend on if that's deemed
> acceptable? "Yeah, we had a feature, and yeah, people depend on it, but we
> don't
On Sunday 09 September 2012 Sep, Thiago Macieira wrote:
> On domingo, 9 de setembro de 2012 11.46.31, Boudewijn Rempt wrote:
> > > Preferably, it should be fixing it once and for all.
> >
> > Well, given that Digia actually seems to have a patch for the bug in
> > question, I'd say that the choice
On domingo, 9 de setembro de 2012 11.39.36, Frank Hemer wrote:
> On Sunday 09 September 2012 11:19:41 Thiago Macieira wrote:
> > What were you referring to when you said "you cannot be serious about
> > that"?
> I refer to the very last part of your statement, citing: 'So there's nothing
> we need
On domingo, 9 de setembro de 2012 11.46.31, Boudewijn Rempt wrote:
> > Preferably, it should be fixing it once and for all.
>
> Well, given that Digia actually seems to have a patch for the bug in
> question, I'd say that the choice is easy. Use the bug fix. If Qt goes
> down the way of "it's bette
On Sun, 9 Sep 2012, Thiago Macieira wrote:
> On domingo, 9 de setembro de 2012 10.55.10, Frank Hemer wrote:
>>> Note that this also applies for Qt 4.8. If the support is broken there and
>>> causing issues like Ariel is describing, it's definitely a P1 that needs
>>> fixing. If we can't muster the
> That combination of items just doesn't make sense to me.
> Your scenario might differ, but try this: a clean Win7 HP or Pro
> install, get any of the latest Intuos4 driver, Qt 4.8.x (I used the
> SDK) and QtC 2.5.x, create a new QtQuick UI, just the simple "Hello
> World" QtC creates for you. Swi
On Sunday 09 September 2012 11:19:41 Thiago Macieira wrote:
> On domingo, 9 de setembro de 2012 10.55.10, Frank Hemer wrote:
> > > Note that this also applies for Qt 4.8. If the support is broken there
> > > and
> > > causing issues like Ariel is describing, it's definitely a P1 that needs
> > > fi
On domingo, 9 de setembro de 2012 10.55.10, Frank Hemer wrote:
> > Note that this also applies for Qt 4.8. If the support is broken there and
> > causing issues like Ariel is describing, it's definitely a P1 that needs
> > fixing. If we can't muster the knowledge of how to fix it properly, we
> > s
On Sunday 09 September 2012 09:25:20 Thiago Macieira wrote:
> On sábado, 8 de setembro de 2012 21.25.21, Ariel Molina R. wrote:
> > > 3. So, you propose to remove tablet support in Qt 5.
> >
> > I proposed on the IRC channel two options and a third one appeared:
> > 1) Qt::WA_AcceptWacom flag, to
On sábado, 8 de setembro de 2012 21.25.21, Ariel Molina R. wrote:
> > 3. So, you propose to remove tablet support in Qt 5.
>
> I proposed on the IRC channel two options and a third one appeared:
> 1) Qt::WA_AcceptWacom flag, to be used explicitly to get wacom events
> 2) --enable-wacom on the comma
13 matches
Mail list logo
