On Thu, Jan 28, 2016 at 2:07 PM, mark diener wrote:
> How do I submit something for Private API in 5.7 after feature-freeze date?
I'm sorry, but you can't add new features (even private) after the
feature freeze. That's the point of a freeze, after all. Just submit
in dev, get it merged, and it w
Shawn:
I went back an re-read your comments.
How do I submit something for Private API in 5.7 after feature-freeze date?
This may be the mechanism that gives me time to try to code my feature
addition and get it into the continous integration system
and NOT be required to do the work before feat
Regarding the server that is used for Qt 5.6 and onwards: It is an exact clone
of the virtual machine that ran in Jenkins with no changes
to the services, but it is in a different virtual network segment. The virtual
segment is the same as the virtual machines that run the tests,
and that has pr
Hi,
In principle that manual is still correct.
There was work going on towards automating the setup for everyone through the
use of a vagrant template
that would call puppet, etc. do to the installation. I believe that was still
part of a work-in-progress branch in qtbase,
but it hasn't hit any
>>> 2. Also lookup qt.conf in all of QLibraryInfo::libraryPaths() (this is
>>> how we got the plugins found)
>>
>> Potentially problematic if plugins might install a qt.conf that isn't
>> what your application needs.
>
> I have full control of the content of my application bundle and the
> libraryP
> Am 28.01.2016 um 11:38:26 schrieb Oswald Buddenhagen
> :
>
> On Thu, Jan 28, 2016 at 10:47:21AM +0100, Maximilian Hrabowski wrote:
>> 1. Add a new public API: static void QLibraryInfo::setQtConfFilePath( const
>> QString& filePath) which defaults to ":/qt/etc/qt.conf“ and is used in
>> QSett
> Am 28.01.2016 um 11:54:02 schrieb Welbourne Edward
> :
>
> Maximilian Hrabowski (28 January 2016 10:47):
>> What we need is a way to look up the qt.conf at another location as well.
> [...]
>> I thought about the following ways (order gives my personal opinion’s
>> priority):
>>
>> 1. Add a
Hi,
this is the same problem that the Qt installation program has, it solves
it by binary patching your copy of Qt5Core.dll when it installs Qt onto
your computer (e.g. set qt_prfxpath="C:\Qt\5.5\msvc2013").
Maybe you can to the same?
Or perhaps a more viable long-range solution is to introd
Maximilian Hrabowski (28 January 2016 10:47):
> What we need is a way to look up the qt.conf at another location as well.
[...]
> I thought about the following ways (order gives my personal opinion’s
> priority):
>
> 1. Add a new public API: static void QLibraryInfo::setQtConfFilePath(
> const QSt
On Thu, Jan 28, 2016 at 10:47:21AM +0100, Maximilian Hrabowski wrote:
> 1. Add a new public API: static void QLibraryInfo::setQtConfFilePath( const
> QString& filePath) which defaults to ":/qt/etc/qt.conf“ and is used in
> QSettings *QLibraryInfoPrivate::findConfiguration() instead of the hard-co
28.01.2016, 11:02, "Sarajärvi Tony" :
> Hi
>
> That manual is probably the only official one we have. Up until Qt 5.5 we've
> been using that one ourselves as well.
> We did have a work in progress version on top of Ubuntu 12.04:
> https://gitorious.org/qtqa/tosarajas-sysadmin-nts.git/?p=qtqa:t
Hi,
I can't response to the aspect of which bugs are considered and how code
reviews happen, but regarding your statement of the development being stalled:
I'm counting 37 landed changes in January 2016 until today, that's more than a
change per day. I can also see changes going in regularly
Hi,
our application has an auto-update feature that allows to download and install
a new version of the application. The update package includes everything, also
Qt. The only permanent files are a launcher executable and a config file that
points to the real application folder. The folder which
Hi Qt developers.
During a long time I see that a development of QtMultimedia module is
stalled... Tons of bugs are not considered at all, and a code-review
commits keeps in reviews at monts without touching/response... Besides,
many of QtMultimedia's API are not implemented yet, and are just as s
Hi
That manual is probably the only official one we have. Up until Qt 5.5 we've
been using that one ourselves as well.
We did have a work in progress version on top of Ubuntu 12.04:
https://gitorious.org/qtqa/tosarajas-sysadmin-nts.git/?p=qtqa:tosarajas-sysadmin-nts.git;a=blob;f=README.network_
15 matches
Mail list logo
