On quinta-feira, 19 de janeiro de 2017 22:20:59 PST René J. V. Bertin wrote:
> I've also been talking since the beginning about configure. Sorry about the
> confusion.
There are two configure scripts: one in the top-level and one in qtbase. Please
be clear which one you mean.
--
Thiago
On quinta-feira, 19 de janeiro de 2017 16:18:30 PST Grégoire Barbier wrote:
> > The return value is interesting still.
>
> With lambdas the return value itself can be replaced with a captured
> reference, isn't it ?
> Anyway it's still convenient to have it when calling plain old methods
> rather
On quinta-feira, 19 de janeiro de 2017 12:24:34 PST Benjamin TERRIER wrote:
> template
> static typename
> QtPrivate::QEnableIf::IsPointerToMemberFun
> ction && QtPrivate::FunctionPointer::ArgumentCount == -1
> && !std::is_same::value, bool>::Type
> invokeMethod(QObject *object, Func
On quinta-feira, 19 de janeiro de 2017 22:22:17 PST Oswald Buddenhagen wrote:
> the central "regular" image loaders are in qtgui, and the "elementary"
> (6MeB of sources ...) opengl support is nowadays also in qtgui, so it
> seems quite plausible to put the texture loaders there as well.
And
On quinta-feira, 19 de janeiro de 2017 22:15:38 PST Oswald Buddenhagen wrote:
> the other solution would be not building host tools at all when doing a
> cross-build, but requiring a native build as a basis.
Long-term we should do that, but we need to support the current way for a
couple of
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 that the best place for them would
> be a new private library in qtimageformats.
>
you can't put it there if qtbase
Oswald Buddenhagen wrote:
> that doesn't matter. the point is that you talked about qtbase.pro
> instead of the top-level project qt.pro.
I've also been talking since the beginning about configure. Sorry about the
confusion. That configure script is obfuscated enough to make it very easy to
On Thu, Jan 19, 2017 at 02:31:29PM +0100, René J.V. Bertin wrote:
> Thiago Macieira wrote:
> > It must be the lack of -Wl,--enable-new-dtags: can you confirm qtdiag has it
> > but lrelease doesn't?
>
> Yep. Neither do lupdate and lconvert, but linguist does (they come all from
> the linguist
On Thu, Jan 19, 2017 at 02:40:43PM +0100, René J. V. Bertin wrote:
> Oswald Buddenhagen wrote:
> > that's what happens when you don't follow my instructions. i explicitly
> > told you that the configure approach is for a top-level (qt5.git) build.
>
> You wrote
> >> if you're doing a top-level
Hi,
As part of some ongoing work I'd like to add some private classes in Qt
to deal with loading of texture files.
Texture files (.dds, .ktx, etc.) are somehow different from ordinary
image files. Not only they store image data in GPU-oriented formats
(that don't require any decoding on the CPU),
Hi Bo
On Thu, 19 Jan 2017 at 09.25, Bo Thorsen wrote:
> Hej Thomas
>
> [...]
> You ask for the best way to proceed: As usual with issues like this, you
>
> should enter a bug in the bug tracker.
>
I did, QTBUG-57882. See original post.
Thomas
René J.V. Bertin wrote:
> 2. Has anything changed in the related functionality between Qt 5.7.1 and Qt
> 5.8.0? I'm currently testing 5.8.0RC installed into a "destroot" (make install
Something has indeed changed here, but apparently already in 5.7.1 . I have a
version check in my platform
Le 17/01/2017 à 18:11, Thiago Macieira a écrit :
Em terça-feira, 17 de janeiro de 2017, às 11:21:56 PST, Grégoire Barbier
escreveu:
And maybe lambdas too, if there was a way to choose the thread/eventloop
in which we want the lambda to be executed (but christmas was a few
weeks ago, I should
René J.V. Bertin wrote:
> 1. Does the platform theme plugin have to be called "kde", i.e. have the same
> name as the internal "kde" theme? IOW, are platform theme plugins matched to
> existing internal plugins themes (to extend them), or are they "plugins that
> provide additional platform
Oswald Buddenhagen wrote:
>>
> that's what happens when you don't follow my instructions. i explicitly
> told you that the configure approach is for a top-level (qt5.git) build.
You wrote
>> if you're doing a top-level build, you just pass it to configure.
I'm doing a top-level build, not
Thiago Macieira wrote:
> Can you compare the command-lines used to link those two applications? What's
> different?
qtdiag:
g++ -m64 -Wl,--gc-sections -Wl,--enable-new-dtags -Wl,-z,origin
-Wl,-rpath,\$ORIGIN/../lib -Wl,-rpath,/opt/local/lib
-Wl,-rpath,/opt/local/libexec/qt5/lib
Hi,
I've got an issue.
Adding
template
static typename
QtPrivate::QEnableIf::IsPointerToMemberFunction
&& QtPrivate::FunctionPointer::ArgumentCount == -1
&& !std::is_same::value, bool>::Type
invokeMethod(QObject *object, Func function)
to QMetaObject breaks existing code and the auto
On Wed, Jan 18, 2017 at 04:57:34PM +0100, René J. V. Bertin wrote:
> Oswald Buddenhagen wrote:
> > if you're doing a top-level build, you just pass it to configure.
>
> But how? Configure now yells on -no-pulseaudio :
> >> ERROR: Unknown command line option '-no-pulseaudio'.
>
> And that error
Hi,
You probably remember that I have been tinkering with an auto-loading Qt
platform theme plugin for Mac, an adapted version of the KDE platform theme
plugin from "Plasma Integration". The goal is to provide support for KDE's
colour & icon palettes plus font role definitions (from
On Wed, Jan 18, 2017 at 03:53:20PM -0800, Thiago Macieira wrote:
> Ossi: what was the conclusion of our discussion on --enable-new-dtags?
>
it's now enabled by default. i have no clue why it would be wrong for
lrelease. a more complete survey of the executables in the qt build dir
would be
Hej Thomas,
Please don't take silence as some indication that people are offended. I
just think you found a corner case that no one has considered and do not
consider one way or the other.
You ask for the best way to proceed: As usual with issues like this, you
should enter a bug in the bug
21 matches
Mail list logo