On sábado, 21 de janeiro de 2017 17:31:34 PST René J. V. Bertin wrote:
> Thiago Macieira wrote:
> >> OK, thanks, I didn't catch that bit from what Google told me. So I would
> >> not have gotten the same error if the symbol were present with another
> >> ELF version?
> >
> > No, you'd have got the
Oswald Buddenhagen wrote:
> feedback to them from the features. if the effect you're describing is
> genuine, there is something seriously screwed up in the qmake internals;
> you may get useful reports from valgrind or asan.
HAH! Would you believe I can no longer reproduce the error I copied ear
Thiago Macieira wrote:
>> OK, thanks, I didn't catch that bit from what Google told me. So I would not
>> have gotten the same error if the symbol were present with another ELF
>> version?
>
> No, you'd have got the same error message...
Hmm, is that useful, not being able to distinguish between
On sábado, 21 de janeiro de 2017 17:10:04 PST Olivier Goffart wrote:
> > I mentioned there that Q_NO_TYPESAFE_FLAGS is broken. [...]
> > The define could be removed from qflags.h. Perhaps something could be
> > changed in qnamespace.h to allow the code to compile instead (and make the
> > enum meta
On sábado, 21 de janeiro de 2017 09:50:50 PST René J. V. Bertin wrote:
> Thiago Macieira wrote:
> > A red herring. You've focused on the wrong part of the information.
> >
> > The linker told you that it can't find a symbol with a given ELF version.
> > That's because the symbol isn't present at a
On sábado, 21 de janeiro de 2017 11:30:40 PST Stephen Kelly wrote:
> Hi,
>
> Does anyone know why QFlags has a constructor taking a Zero pointer? My
> guess is that it's a hack to make initializing like
>
> Qt::WindowFlags = 0
>
> work? The problem encountered is that porting tools convert that
On Samstag, 21. Januar 2017 11:30:40 CET Stephen Kelly wrote:
> Hi,
>
> Does anyone know why QFlags has a constructor taking a Zero pointer? My
> guess is that it's a hack to make initializing like
>
> Qt::WindowFlags = 0
>
> work?
Correct.
We want to be able to initialize it with the literal
Oswald Buddenhagen wrote:
>>
> that makes just no sense whatsoever. the command line options are
> declared in a separate section near the top of the file, and there is no
That's what I had been thinking all the time too. It's only when you draw my
attention to config_help.txt and saw the "unix
> 21 янв. 2017 г., в 16:25, Sean Harmer написал(а):
>
> It's
> about being able to parse texture files into CPU addressable memory. From
> there
> it can be used by OpenGL, Direct3D, Vulkan, Metal, $OTHER_API.
>
Do I understand correctly that all is needed is to scan header of the texture,
On Saturday 21 January 2017 13:51:15 André Pönitz wrote:
> On Sat, Jan 21, 2017 at 10:51:11AM +, Sean Harmer wrote:
> > On Friday 20 January 2017 20:35:49 Konstantin Tokarev wrote:
> > > 20.01.2017, 00:22, "Oswald Buddenhagen" :
> > > > On Thu, Jan 19, 2017 at 07:34:08PM +0100, Giuseppe D'Angel
On Sat, Jan 21, 2017 at 10:51:11AM +, Sean Harmer wrote:
> On Friday 20 January 2017 20:35:49 Konstantin Tokarev wrote:
> > 20.01.2017, 00:22, "Oswald Buddenhagen" :
> > > On Thu, Jan 19, 2017 at 07:34:08PM +0100, Giuseppe D'Angelo wrote:
> > >> Nonetheless, since such loaders would be useful
Le 21/01/2017 à 00:20, Thiago Macieira a écrit :
It's a shift of responsibility. If we had the BlockingAutoConnection (or
SynchronousConnection, which is what I wanted to call it during Qt 4.5 when I
first proposed it), the deadlock would be Qt's fault. Since it's you doing
that, the deadlock bec
Hi,
Does anyone know why QFlags has a constructor taking a Zero pointer? My
guess is that it's a hack to make initializing like
Qt::WindowFlags = 0
work? The problem encountered is that porting tools convert that to
Qt::WindowFlags = nullptr
which is undesirable.
https://mail.kde.org/pip
On Friday 20 January 2017 20:35:49 Konstantin Tokarev wrote:
> 20.01.2017, 00:22, "Oswald Buddenhagen" :
> > On Thu, Jan 19, 2017 at 07:34:08PM +0100, Giuseppe D'Angelo wrote:
> >> Nonetheless, since such loaders would be useful in more than one place
> >> (qtbase, qtdeclarative, qt3d) I think th
On Fri, Jan 20, 2017 at 09:14:00PM +0100, René J. V. Bertin wrote:
> Oswald Buddenhagen wrote:
>
>
> > check whether qtmultimedia/{config_help.txt,configure.json} exist and
>
> They do.
>
> > claim support.
>
> I think I can do better: apparently I have found the culprit. In the Features
> se
Thiago Macieira wrote:
> A red herring. You've focused on the wrong part of the information.
>
> The linker told you that it can't find a symbol with a given ELF version.
> That's because the symbol isn't present at all, with any ELF version.
OK, thanks, I didn't catch that bit from what Google
16 matches
Mail list logo
