There are still some very large enterprise users running on vc2008 build
systems. Would this mean that all hope for building new releases on vc2008
would be lost, or that it just may take more effort than normal? As it
stands, I had to apply some manual fixes to get 5.1 to build with vc2008,
but it
Le 06/02/2014 00:15, Bruno Coudoin a écrit :
Le 05/02/2014 21:58, Bruno Coudoin a écrit :
Hi,
Looking at the latest release 5.2.1 the Audio in QRC has been fixed:
https://bugreports.qt-project.org/browse/QTBUG-31422
I have not tested yet, I was in the process of managing the issue in
my appl
Le 05/02/2014 21:58, Bruno Coudoin a écrit :
Hi,
Looking at the latest release 5.2.1 the Audio in QRC has been fixed:
https://bugreports.qt-project.org/browse/QTBUG-31422
I have not tested yet, I was in the process of managing the issue in
my application and is is not that easy. I hope the QR
> >I’ve now gone through all changes. The set looks pretty good overall, and
> >testing on Linux showed no regressions compared to 5.2.
>
> One correction here: The paperRect as shown in the preview of the dialogs
> manual test shows some slightly different results, that look like a
> rounding iss
I don't have the time to write the class, the docs, the unit tests, fix all the
issues we've found, integrate it with QVariant and possibly QtDBus in the next
week.
So I'll just proceed to add overloads to toInt & family that take an int*
instead of bool*.
If we decide to add QOptional overloa
Em qua 05 fev 2014, às 12:52:07, Alan Ezust escreveu:
> I have the same question.
> Interesting that assets:/ is used in both android and blackberry 10...
> It would be nice if we could get assets:/ to work on the desktop platforms
> also,
> perhaps by packaging the assets into an accompanying .zi
Em qua 05 fev 2014, às 14:28:36, Matthew Woehlke escreveu:
> > You will just have an undefined behaviour. You will return the content of
> > the uninitialized memory cast to the type, and it will likely cause a
> > crash later. Debug build will abort, release build will probably crash
> > somehow
Hi,
Looking at the latest release 5.2.1 the Audio in QRC has been fixed:
https://bugreports.qt-project.org/browse/QTBUG-31422
I have not tested yet, I was in the process of managing the issue in my
application and is is not that easy. I hope the QRC way is working fine.
Bruno.
Le 05/02/201
I have the same question.
Interesting that assets:/ is used in both android and blackberry 10...
It would be nice if we could get assets:/ to work on the desktop platforms
also,
perhaps by packaging the assets into an accompanying .zip file so it
doesn't cause memory bloat on the executable.
On
+1
On Wednesday, February 5, 2014, Sylvain THIBAUT <
sylvain.thib...@amplitude-ortho.com> wrote:
> Hi Sean,
>
> > The project is far from dead. We are hacking on it right now, but given
> how
> > much we want to change from Qt3D 1 we have been working on it in private.
> > However, we are now abo
On 2014-02-05 13:04, Olivier Goffart wrote:
> On Wednesday 05 February 2014 09:44:39 Thiago Macieira wrote:
>> Em qua 05 fev 2014, às 12:36:42, Matthew Woehlke escreveu:
>>> On 2014-02-05 12:19, Thiago Macieira wrote:
We need to return something.
>>>
>>> ...or you could abort, which I assume i
I've followed std::optional closely through the standardization process, so I
can give some background info:
- from the beginning Boost::optional was written with a pointer-like syntax:
optional op = maybe_get_the_value();
if (op) {
int x = *op;
.
Hi!
Trying build Qt-5.2.1 with mingw-w64 GCC-4.8.2 I got error linking Qt5Test
library for both 32 and 64 bit.
I fill bug report: https://bugreports.qt-project.org/browse/QTBUG-36661
Regards,
Alexey.
___
Development mailing list
Development@qt-project.
On 2014-02-05 12:19, Thiago Macieira wrote:
> Em qua 05 fev 2014, às 10:37:27, Robert Knight escreveu:
>>> The idea was to silently return a default-constructed type.
>>
>> I'm not keen on that. Aside from adding extra restrictions to the
>> types that the class can be used with as you mention,
>>
On Wednesday 05 February 2014 09:44:39 Thiago Macieira wrote:
> Em qua 05 fev 2014, às 12:36:42, Matthew Woehlke escreveu:
> > On 2014-02-05 12:19, Thiago Macieira wrote:
> > > Em qua 05 fev 2014, às 10:37:27, Robert Knight escreveu:
> > >>> The idea was to silently return a default-constructed typ
Em qua 05 fev 2014, às 12:36:42, Matthew Woehlke escreveu:
> On 2014-02-05 12:19, Thiago Macieira wrote:
> > Em qua 05 fev 2014, às 10:37:27, Robert Knight escreveu:
> >>> The idea was to silently return a default-constructed type.
> >>
> >> I'm not keen on that. Aside from adding extra restrictio
Em qua 05 fev 2014, às 09:44:39, Thiago Macieira escreveu:
> First, Q_ASSERT() is eliminated in a debug build, so we're left with no
> abort.
I meant release build.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
Hi,
Regarding Qt 5.2.2 - let's see how well 5.2.1 is received. We have now 1,5
months shorter cycle than the usual 6 months for Qt 5.3. I agree that it was a
long wait between 5.1.1 and 5.2.0.
Yours,
Tuukka
Lähettäjä: development-bounces+tuukka.turune
Em qua 05 fev 2014, às 11:58:50, Simon Hausmann escreveu:
> Hi Shane,
>
> Interesting stuff :)
>
> How do you determine that a particular header file is the "hot spot"? (I
> didn't understand that part from the slide set) Is that header file
> commonly included in other files that result in long-
Em qua 05 fev 2014, às 10:37:27, Robert Knight escreveu:
> > The idea was to silently return a default-constructed type.
>
> I'm not keen on that. Aside from adding extra restrictions to the
> types that the class can be used with as you mention,
> it runs the much more severe risk of masking seri
Em qua 05 fev 2014, às 14:17:20, Shane McIntosh escreveu:
> > I just went over your list and have not been overly surprised with
> > which files are causing long rebuild times: All of them are header
> > files that are widely used in Qt and by Qt applications. E.g. almost
> > the complete set of no
Hello guys
Is it maybe time to get rid of MSVC 2008 from our build farm? Do the new
versions support wince builds?
> c:\work\build\qt\qtbase\tests\auto\corelib\global\qtendian\tst_qtendian.cp
> p(140) : fatal error C1001: An internal error has occurred in the
> compiler.
>
> Build log
We have the branch model to make it easy to choose the right branch, usually
without worrying about the releases too much.
"Normal" bug fixes go always to stable.
Stable is guaranteed to be merged into dev before the next release, so you'll
never have to worry, no patch gets lost.
Show stoppers
On 5 February 2014 15:55, John Layt wrote:
> Hi,
>
> I've seeing contradictory advice on Gerrit as to which branch to push bug-
> fixes to, some say there will be no 5.2.2 so to use dev instead, others say to
> keep using stable in case there is. What is the current "official" policy?
>
> Oh, and
For now the policy is still to push to stable. We haven’t made any
decision on whether to do or not do a 5.2.2 release yet, but it’s
something we need to figure out rather soon.
Cheers,
Lars
On 05/02/14 15:55, "John Layt" wrote:
>Hi,
>
>I've seeing contradictory advice on Gerrit as to which bra
On 5 Feb 2014, at 11:16 AM, Damian Ivanov wrote:
> Hi,
>
> I made a c++ QML plugin for X11 functions like windowlist, active
> window, setting, getting icon of apps, names, id and setting netwm
> properties. Source code is here
> https://build.opensuse.org/package/show/home:damianator:qmlx11/qm
Hi,
I've seeing contradictory advice on Gerrit as to which branch to push bug-
fixes to, some say there will be no 5.2.2 so to use dev instead, others say to
keep using stable in case there is. What is the current "official" policy?
Oh, and please remember when making such decisions to clearly
Hi all,
We are happy to announce that Qt 5.2.1 & Qt Creator 3.0.1 is released today,
see http://blog.qt.digia.com/blog/2014/02/05/qt-5-2-1-released/ &
http://blog.qt.digia.com/blog/2014/02/05/qt-creator-3-0-1-released/
Big thanks to everyone who has helped to make the releases happen!
Br,
Jani
On 05/02/14 13:59, "Knoll Lars" wrote:
>Hi John,
>
>I’ve now gone through all changes. The set looks pretty good overall, and
>testing on Linux showed no regressions compared to 5.2.
One correction here: The paperRect as shown in the preview of the dialogs
manual test shows some slightly differe
Hi Sean,
> The project is far from dead. We are hacking on it right now, but given how
> much we want to change from Qt3D 1 we have been working on it in private.
> However, we are now about to begin upstreaming it to a non-CI controlled
> branch in the Qt3D repo.
Is this non-CI branch already pu
Hi Andre,
On Feb 5, 2014, at 12:11 PM, Poenitz Andre wrote:
> Shane McIntosh [mcint...@cs.queensu.ca] wrote:
>> Hi Qt developers!
>>
>> My name is Shane. I’m a PhD student at Queen’s University in Canada.
>>
>> I’ve been working on an approach for detecting build hotspots, i.e.,
>> files that
Hi Simon,
On Feb 5, 2014, at 11:58 AM, Simon Hausmann wrote:
> On Monday 3. February 2014 22.39.27 Shane McIntosh wrote:
>> Hi Qt developers!
>>
>> My name is Shane. I’m a PhD student at Queen’s University in Canada.
>>
>> I’ve been working on an approach for detecting build hotspots, i.e., fi
Hi Tobias,
On Feb 5, 2014, at 11:45 AM, Tobias Hunger wrote:
> The list of yours seems to be ordered alphabetically. I guess that is
> not necessarily the order in which we should look at the files:-) This
> list is rather long and slide 36 of your presentation shows that the
> files listed trig
Hi John,
I’ve now gone through all changes. The set looks pretty good overall, and
testing on Linux showed no regressions compared to 5.2.
IMO, you can go ahead and stage the first set of changes that are mainly
cleanups.
There are quite a few comments on the changes adding the new public API.
Hi Shane,
On Monday 3. February 2014 22.39.27 Shane McIntosh wrote:
> Hi Qt developers!
>
> My name is Shane. I’m a PhD student at Queen’s University in Canada.
>
> I’ve been working on an approach for detecting build hotspots, i.e., files
> that not only take a long time to rebuild, but also ch
Hi Shane,
thanks again for the presentation at FOSDEM. I really enjoyed it:-)
The list of yours seems to be ordered alphabetically. I guess that is
not necessarily the order in which we should look at the files:-) This
list is rather long and slide 36 of your presentation shows that the
files lis
> The idea was to silently return a default-constructed type.
I'm not keen on that. Aside from adding extra restrictions to the
types that the class can be used with as you mention,
it runs the much more severe risk of masking serious bugs.
Regard,
Rob.
On 4 February 2014 23:12, Matthew Woehlke
Something similar happened to me too on the dev branch. Tried merging a
change. First a test case failed (tst_QDnsLookup) even though it runs fine
on my local setup. I tried re-staging the change but now I got some merge
errors. Local update of dev and rebase worked.
-mandeep
On Wed, Feb 5, 20
Hello,
I'm trying for two days to merge this https://codereview.qt-project.org/77207
patch, but CI doesn't like me.
It is a know issue or just me? Should I wait for other patches to be merged
before I'll try the 8th time? :)
Cheers,
BogDan.
___
D
39 matches
Mail list logo
