On Wednesday 25 November 2015 06:25:34 Hausmann Simon wrote:
> Hi,
>
> It would seem that recent QPair changes have a negative impact on the
> ability to compile some existing code :)
>
> Is this an issue in the usage or an issue with QPair?
Compiler bug.
> C:\Users\qt\work\qt\qtbase\include\Qt
Hi,
It would seem that recent QPair changes have a negative impact on the ability
to compile some existing code :)
Is this an issue in the usage or an issue with QPair?
Simon
Original Message
From: Qt CI Bot (Code Review)
Sent: Wednesday, November 25, 2015 07:22
To: Qi Liang
Cc: Hausmann Si
On Tuesday 24 November 2015 23:04:59 René J. V. Bertin wrote:
> Thiago Macieira wrote:
> > It mustn't be $TMPDIR. It needs to be a directory owned by the user so no
>
> You're missing a detail. On OS X, $TMPDIR (and QDir::tempPath()) *are* user
> specific. They're also very "immemorable"...
They'
Thiago Macieira wrote:
> It mustn't be $TMPDIR. It needs to be a directory owned by the user so no
You're missing a detail. On OS X, $TMPDIR (and QDir::tempPath()) *are* user
specific. They're also very "immemorable"...
> It could be a subdir of $TMPDIR, but then we run into a race condition pr
On Tuesday 24 November 2015 19:58:22 René J. V. Bertin wrote:
> I'd have chosen $TMPDIR (aka QDir::tempPath()) myself. Contrary to
> ~/Library/Cache that one is cleared on each reboot, which seems advantageous
> at least for the kind of things RuntimeLocation is used for in
> FOSS/Freedesktop app
Petroules Jake wrote:
> PS: why did Qt choose ~/Library/Application Support for that location? Isn't
> the stuff stored there supposed to be volatile that doesn't need to survive
> reboots or end up in (Time Machine) backups?
>
> ~/Library/Application Support is non volatile and absolutely must s
On Nov 24, 2015, at 2:25 AM, René J. V. Bertin
mailto:rjvber...@gmail.com>> wrote:
PS: why did Qt choose ~/Library/Application Support for that location? Isn't the
stuff stored there supposed to be volatile that doesn't need to survive reboots
or end up in (Time Machine) backups?
~/Library/Appl
I would like to nominate Pasi Petäjäjärvi for Approver status in the Qt Project.
Pasi is the maintainer of the VxWorks port and has also been contributing a lot
for other embedded platforms over the years.
+1 from me as well. Great to have more embedded experts as approvers ;-)
Regards,
Andy
On Tuesday November 24 2015 10:30:32 Hausmann Simon wrote:
Hi,
>I think the chances of a Qt application depending on glib on Mac OS X are
>extremely slim,
>given that glib is not part of the default system installation.
That strikes me as a bit of a surprising argument for a middleware that is
Hi,
I think the chances of a Qt application depending on glib on Mac OS X are
extremely slim, given that glib is not part of the default system installation.
I think the much more common case of a Qt application on Mac OS X is to just
use Qt and the system APIs without any third-party library d
Hello,
This is a follow-up question to one I posted yesterday.
Looking into the paths used for QSP::RuntimeLocation in more detail I noticed
that GLib has its own ideas, using $HOME/.cache on OS X:
https://developer.gnome.org/glib/stable/glib-Miscellaneous-Utility-Functions.html#g-get-user-runt
On 11/24/2015 10:04 AM, Agocs Laszlo wrote:
Hello,
I would like to nominate Pasi Petäjäjärvi for Approver status in the Qt
Project.
Pasi is the maintainer of the VxWorks port and has also been
contributing a lot for other embedded platforms over the years.
+1
- Eirik Aa.
_
Hello,
I would like to nominate Pasi Petäjäjärvi for Approver status in the Qt Project.
Pasi is the maintainer of the VxWorks port and has also been contributing a lot
for other embedded platforms over the years.
Public Gerrit dashboard:
https://codereview.qt-project.org/#/q/owner:pasi.p
13 matches
Mail list logo
