> -Original Message-
> From: Thiago Macieira [mailto:thiago.macie...@intel.com]
> Sent: 29. huhtikuuta 2015 18:42
> To: development@qt-project.org
> Cc: Turunen Tuukka
> Subject: Re: [Development] Licensing of WinRT and Windows Embedded in Qt
> 5.5
>
> On Wednesday 29 April 2015 10:00:30
On Monday 27 April 2015 11:46:05 Lind Jorgen wrote:
> Its a small library, so I think it is sensible to compile it in the plugin
> (even with the error data). I don't think it makes much sense at current
> time to check if there is a system version available and then use that.
Oh yes it's sensible
On Wed, Apr 29, 2015 at 6:01 PM, Konstantin Ritt wrote:
> Any links/code/docs?)
Yes, sorry :)
Wiki page: http://wiki.qt.io/QtModeling
Git repository: http://www.gitorious.org/qt/qtmodeling
DuSE-MT (QtModeling-based tool) website: http://duse.sourceforge.net/
DuSE-MT repository: www.gitorious.org
Konstantin,
here you are:
http://wiki.qt.io/QtModeling
On Thu, Apr 30, 2015 at 12:01 AM, Konstantin Ritt wrote:
> Any links/code/docs?)
>
> Konstantin
>
> 2015-04-30 0:26 GMT+04:00 Sandro Andrade :
>
>> Hi there,
>>
>> Some time ago, I started the development of QtModeling : a qt add-on
>> aime
Any links/code/docs?)
Konstantin
2015-04-30 0:26 GMT+04:00 Sandro Andrade :
> Hi there,
>
> Some time ago, I started the development of QtModeling : a qt add-on
> aimed at providing metamodeling features and the basic infrastructure
> for dealing with software models. It already has a lot of int
Hi there,
Some time ago, I started the development of QtModeling : a qt add-on
aimed at providing metamodeling features and the basic infrastructure
for dealing with software models. It already has a lot of interesting
features and now I have the available time to making it good enough to
be relea
On Wednesday 29 April 2015 11:15:21 Simon Hausmann wrote:
> How can we do this in Qt and in our tests?
The problem here is the fact that they're tests. Unlike regular applications,
we're doing things at times when applications shouldn't be doing the same
action.
Strictly speaking, we should fix
On Wednesday 29 April 2015 10:02:29 Simon Hausmann wrote:
> In my opinion the overhead of the read-write lock is not worth the
> prospective gain in the unlikely event of repeated concurrent environment
> access.
Agreed.
An RWLock has a benefit when there are multiple *read* threads trying to acc
On Wednesday 29 April 2015 10:00:30 Turunen Tuukka wrote:
> The Qt Company has decided that the license of WinRT port of Qt will be
> LGPLv3 / GPLv2+ / Commercial in Qt 5.5. Microsoft is soon to release
> Windows 10, and Qt 5.5.x is planned to bring full support for it. We prefer
> LGPLv3 and there
Hello dear developers!
Recently we learned the good news about the release QtIFW 2.0:
http://blog.qt.io/blog/2015/04/07/qt-installer-framework-2-0-released
And I too was delighted at once. But then I was faced with an unstable work of
the installer on Windows and it upset me.
I think QtIFW 2.0
> On Apr 21, 2015, at 11:46 AM, René J.V. Bertin wrote:
>
> Hi,
>
> I know I should ask this on the QC ML (but I'd prefer not to sign up for just
> an occasional question like this):
>
> Is there a (good) reason why DocumentManagerPrivate::linkWatcher() forces the
> use of a polling watcher?
Hello,
The Qt Company has decided that the license of WinRT port of Qt will be LGPLv3
/ GPLv2+ / Commercial in Qt 5.5. Microsoft is soon to release Windows 10, and
Qt 5.5.x is planned to bring full support for it. We prefer LGPLv3 and
therefore we want to adjust the licensing now and discontin
On Wednesday, April 29, 2015 11:55:48 AM Marc Mutz wrote:
> On Tuesday 28 April 2015 10:52:32 Simon Hausmann wrote:
> > There are various options about what we can do with different degrees of
> > "perfection", but ultimately it's all going to require a compromise. The
> > option that we are favori
On Wednesday 29 April 2015 11:55:48 Marc Mutz wrote:
> 1. man putenv on Linux says that since glibc 2.1, putenv is reentrant
http://osxr.org/glibc/source/stdlib/setenv.c#0109
but getenv isn't protected by any lock, indeed:
http://osxr.org/glibc/source/stdlib/getenv.c#0033
--
Marc Mutz | Senio
On Tuesday 28 April 2015 10:52:32 Simon Hausmann wrote:
> There are various options about what we can do with different degrees of
> "perfection", but ultimately it's all going to require a compromise. The
> option that we are favoring at the moment is two-fold:
>
> 1) Policy in Qt is to use the Q
Oh, for me this is good enough. I am just playing around with new stuff.
But if the qt project can wait for 5.2? 3-4 month if I googled correctly?
No idea.
Guido
On Wed, 29 Apr 2015 08:16:03 +0200
Markus Trippelsdorf wrote:
> This will be fixed in 5.2, see:
> https://gcc.gnu.org/bugzilla/show_
On Tuesday, April 28, 2015 10:26:13 AM Matthew Woehlke wrote:
> On 2015-04-28 04:52, Simon Hausmann wrote:
> > [getenv/setenv not thread safe]
> >
> > There are various options about what we can do with different degrees of
> > "perfection", but ultimately it's all going to require a compromise. T
17 matches
Mail list logo