Re: [Development] ICU decision?

On quarta-feira, 7 de agosto de 2013 00:22:59, John Layt wrote: > The question really then is how to expose the advanced features from an > optional ICU: > * Separate module That's fallback. > * In QtCore, but classes only available on Win32 if ICU used That's out of the question. > * In QtCo

Re: [Development] RPATH in libraries

On terça-feira, 6 de agosto de 2013 23:22:10, Konrad Rosenbaum wrote: > Ok, I found the answer to my own question: DT_RUNPATH is radically different > from DT_RPATH - if it was only evaluated after $LD_LIBRARY_PATH it would > not be a problem, but it also does not apply to libraries loaded by the >

Re: [Development] RPATH in libraries

Hi, On Tuesday 06 August 2013 17:10:31 Thiago Macieira wrote: > On terça-feira, 6 de agosto de 2013 15:41:21, Konrad Rosenbaum wrote: > > On Sunday 04 August 2013 18:51:10 Thiago Macieira wrote: > > > On domingo, 4 de agosto de 2013 10:20:51, Dmitry Ashkadov wrote: > > > > LDD finds library using

Re: [Development] QML engine changes

As far as i know, the only thing our CI system can do is actually executing "qmake && make". So we cannot rely on the init-repository.py script, and will therefore need "git submodule init --recursive" as soon as we start using the CI. I was planning to get the QtWebEngine repository ready for t

Re: [Development] QML engine changes

Zeno, do we still need that or is init-repository.py required anyway? Simon Fra: Sergio Ahumada Sendt: 21:35 tirsdag 6. august 2013 Til: development@qt-project.org Emne: Re: [Development] QML engine changes On 08/06/2013 09:25 PM, Hausmann Simon wrote: > Darn, I see. Maybe the solution is not r

Re: [Development] QML engine changes

Darn, I see. Maybe the solution is not remove the --recursive Parameter from the submodule update call. Simon Fra: Sergio Ahumada Sendt: 20:40 tirsdag 6. august 2013 Til: development@qt-project.org Emne: Re: [Development] QML engine changes On 08/06/2013 08:35 PM, Hausmann Simon wrote: > Yes,

Re: [Development] Puzzled by desktop development priorities, Mac OS specifically [Warning: Rant]

On terça-feira, 6 de agosto de 2013 15:38:43, Rutledge Shawn wrote: > On 6 Aug 2013, at 5:09 PM, Thiago Macieira wrote: > > Note that there is nothing "Plugins/qml" in that bundle. > > > > Copy that photosurface.app to a system with no Qt (or remove/rename your > > original Qt so that the plugins

Re: [Development] QML engine changes

Yes, that's intentional. However it is not required for use or development. It is useful when doing changes on the ecmascript bits. Simon Fra: Sergio Ahumada Sendt: 20:24 tirsdag 6. august 2013 Til: development@qt-project.org Emne: Re: [Development] QML engine changes On 08/06/2013 05:04 PM, S

[Development] ICU decision?

Have we reached a decision? I'd like an answer: do we depend on ICU on all platforms? Or will we allow platforms to build without ICU? I'm talking about QtCore here. WebKit is a whole other matter. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Tec

Re: [Development] Puzzled by desktop development priorities, Mac OS specifically [Warning: Rant]

On terça-feira, 6 de agosto de 2013 11:41:41, Rutledge Shawn wrote: > $ find photosurface.app/ > photosurface.app/ > photosurface.app//Contents > photosurface.app//Contents/Info.plist > photosurface.app//Contents/MacOS > photosurface.app//Contents/MacOS/photosurface > photosurface.app//Contents/Pkg

Re: [Development] RPATH in libraries

On terça-feira, 6 de agosto de 2013 15:41:21, Konrad Rosenbaum wrote: > On Sunday 04 August 2013 18:51:10 Thiago Macieira wrote: > > On domingo, 4 de agosto de 2013 10:20:51, Dmitry Ashkadov wrote: > > > LDD finds library using RPATH first of all, so, for local installed Qt5 > > > > That's why RPA

Re: [Development] RPATH in libraries

On Sunday 04 August 2013 18:51:10 Thiago Macieira wrote: > On domingo, 4 de agosto de 2013 10:20:51, Dmitry Ashkadov wrote: > > LDD finds library using RPATH first of all, so, for local installed Qt5 > > That's why RPATH was deprecated and replaced with RUNPATH. Stupid question: is there a reason

Re: [Development] Puzzled by desktop development priorities, Mac OS specifically [Warning: Rant]

thanks a lot ... I will try this :) 2013/8/6 Rutledge Shawn > > On 6 Aug 2013, at 1:41 PM, Shawn Rutledge wrote: > > Rene's script is for Qt 4. (Kudos on the egrep/awk bit especially.) I > updated it for Qt 5 as follows: > > > > #!/bin/bash > > QT_INSTALL_QML=`qmake -query QT_INSTALL_QML` > >

Re: [Development] Puzzled by desktop development priorities, Mac OS specifically [Warning: Rant]

I have just reread the qt documentation and it seems that we need to use macdeployqt to have a working bundle. Le mardi 6 août 2013, qtnext a écrit : > I don't need macdeployqt to build a complete .app ? I come from windows so > mac dev is for me a little bit exotic and i was sure that i need > m

Re: [Development] Puzzled by desktop development priorities, Mac OS specifically [Warning: Rant]

I don't need macdeployqt to build a complete .app ? I come from windows so mac dev is for me a little bit exotic and i was sure that i need macdeployqt ? How can i create a complete file with qmake ? From qt creator? Or command line ? Le mardi 6 août 2013, Rutledge Shawn a écrit : > > On 6 Aug 20

[Development] QPlatformWindow isActive implementation on Windows

Hi all, The documentation in the source for QPlatformWindow states that isActive is used to indicate whether a window should appear active from a style perspective. The implementation of isActive in qwindows

Re: [Development] Puzzled by desktop development priorities, Mac OS specifically [Warning: Rant]

On Tuesday 06 August 2013 09:57:42 qtnext wrote: > I always package the qml in a ressource file. That is not the issue It's the QML imports that aren't deployed properly, but that's already an issue in Qt 4. I fixed that with the attached script that's called after macdeployqt... HTH, René #!/bi

Re: [Development] Puzzled by desktop development priorities, Mac OS specifically [Warning: Rant]

I always package the qml in a ressource file. That is not the issue Le mardi 6 août 2013, Rutledge Shawn a écrit : > > On 5 Aug 2013, at 9:37 PM, qtnext wrote: > > > I have tryed various fix (script to fix // issue, macdeployqt from git > instead of native one, but at end it don't works ... ) hop