Re: [Development] [Interest] Current status of the co-installation

On segunda-feira, 29 de outubro de 2012 18.51.10, Thiago Macieira wrote: > However, if you do a -prefix /usr configuration, then the layout will be: > > /usr/binUser applications only (qdbus, > linguist, etc.) /usr/liblibs > /usr/lib/

Re: [Development] [Interest] Current status of the co-installation

I stil don't like the qml2x convention too much. If you go through the list, only qmlplugindump is both qtquick1 and qtquick2, so adding a '2' to all the tools isn't necessary. ./lib64/qt5/bin/qml2bundle ./lib64/qt5/bin/qml2min I'm pretty sure qml2min also works for qml1 files, so why not just

Re: [Development] Qt 4.8 CI problems

Hi Janne, thanks a lot about the update, good to know why it was failing and that it is going to be resolved. Keep up the good work. Regards, Thomas On Monday 29 October 2012 14:29:53 Anttila Janne wrote: > Hi, > > There have been various problems on Qt 4.8 CI since we moved that project > fro

Re: [Development] QML Profiler for Qt5

Hello Christiaan, thx for the answere. So as i understood now QML Profiler does only show animation events an not initial paintings? For QtQuick1.0 it was working. Is it planned? We have a roation of an arrow every 100ms and even there we can't see any paint events. Greetings Torsten With

[Development] Qt5 Beta/Qt Quick 2.0 and Antialiasing

Hello, we created some prototype with Qt Quick 2 on a ARM board. Its running verry well except antialiasing. As i can see in the Qt5 Documentation there is a new flag for antialiasing * antialiasing : bool but this

Re: [Development] Qt5 Beta/Qt Quick 2.0 and Antialiasing

On 10/30/2012 11:14 AM, Labs, Torsten wrote: > Hello, > we created some prototype with Qt Quick 2 on a ARM board. Its running > verry well except antialiasing. As i can see in the Qt5 Documentation > # there is a new flag for antialiasing **antialiasing >

Re: [Development] QDateTime::currentDateTime().toString(Qt::SystemLocaleLongDate) returns as if the DST was still in effect

On Monday, October 29, 2012 09:09:48 AM Thiago Macieira wrote: > It's got to be a glibc bug. > > We only do: > tzset(); > localtime(); > > Since we don't do anything special, I'm forced to conclude that the bug is > in glibc. Jan, if you do report it to whoever is responsible for gli

Re: [Development] Consistency in Qt headers (extends: 'renaming all QWindow properties that have "window" in them')

On Mon, Oct 29, 2012 at 5:45 PM, Knoll Lars wrote: >> - QDoc loses all ability to differentiate between modules and namespaces > > In principle that's fixable in qdoc. If we were to start from scratch, I > think QtNamespace would be more consistent, as it's the same as the module > name. But it'

Re: [Development] Qt 4.8 CI problems

Bornemann Joerg wrote: > On 29/10/2012 14:29, Anttila Janne wrote: > >> 4. Marked flaky tst_qlocalsocket autotest insignificant: >> https://codereview.qt-project.org/38137 > > Could you please point me to a log that shows that this test is flaky in > Qt 4.8? I can then look into this issue.

Re: [Development] Dependencies of Qt5

> This time we will need RUBY. What next? Webkit also requires bison. -- This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original.

Re: [Development] Dependencies of Qt5

Note that qt5.git also contains binaries of bison and win_flex needed by WebKit. If qtwebkit is built as part of qt5.git then those binaries will be used automatically. Simon -- Sendt fra min Nokia N930.10.12 13:57 skrev shane.kea...@accenture.com: > This time we will need RUBY. What next? Web

Re: [Development] Dependencies of Qt5

On terça-feira, 30 de outubro de 2012 13.38.03, Hausmann Simon wrote: > Note that qt5.git also contains binaries of bison and win_flex needed by > WebKit. If qtwebkit is built as part of qt5.git then those binaries will be > used automatically. ANGLE requires bison and flex. Simon: what's the dif

Re: [Development] [Interest] Current status of the co-installation

On terça-feira, 30 de outubro de 2012 07.29.57, Koehne Kai wrote: > I stil don't like the qml2x convention too much. If you go through the list, > only qmlplugindump is both qtquick1 and qtquick2, so adding a '2' to all > the tools isn't necessary. > > ./lib64/qt5/bin/qml2bundle > ./lib64/qt5/bin/q

[Development] Pending decisions on co-installation

If I've forgotten anything, please add. As far as I can tell, here are the pending decisions, in increasing order of severity: 1) QML environment variables The variable for import paths has been versioned from QML_IMPORT_PATH to QML2_IMPORT_PATH. But I have not changed any of the other variable

Re: [Development] Pending decisions on co-installation

On Tue, Oct 30, 2012 at 01:47:03PM -0700, Thiago Macieira wrote: > 5) executable split between end-user applications and indirect tooling > The most controversial proposal so far is to split the binaries into two > groups: one that gets installed to PREFIX/bin, containing the executables for > ap

Re: [Development] Pending decisions on co-installation

On terça-feira, 30 de outubro de 2012 23.52.08, André Pönitz wrote: > On Tue, Oct 30, 2012 at 01:47:03PM -0700, Thiago Macieira wrote: > > 5) executable split between end-user applications and indirect tooling > > The most controversial proposal so far is to split the binaries into two > > groups: