> On Sep 17, 2015, at 11:07 AM, Michael Jackson <[email protected]> wrote: > > *External Message - use caution* > > > On Sep 17, 2015, at 11:50 AM, John Weeks <[email protected]> wrote: > >> We use our own build of Qt 5.5, including a debug build. Debugging is often >> painfully slow but mostly works. And with a debug build of Qt we can step >> into Qt code and (usually) inspect d pointers. >> >> Be sure that you have gone into the Projects tab in Qt Creator, select the >> Run half of the button for the kit you're using and turn on the checkbox >> "Use debug version of frameworks" >> >> <PastedGraphic-1.png> >> >> Who else thinks that black Build button looks selected? But it's not- the >> Run button is active! >> >> -John Weeks >> WaveMetrics, Inc. > > I had not thought about trying the debug versions of the frameworks but I > don't think (for us) it is the issue. We can not even debug our _own_ codes, > let alone anything from Qt, but maybe the debug versions have something to do > with it? Worth a try. Of course trying to build Qt isn't as easy as it used > to be back in the 4.x days. We depend on QtWebEngine so there is all of that. > And our packaging system depends on an installation from Digia, not a home > built installation. I'll have to setup a couple of different sandboxes. One > with our build and one with the official Digia builds.
I have had some success building Qt 5.5 for OS X. I should setup some Jenkins jobs to grab the source from Qt and build it. Having to setup build environments and tweak the Jenkins jobs to build the same for Android, iOS, OS X, and Windows would likely burn a week or more. But hopefully once it was done would not not be too hard to maintain throughout the 5.x lifecycle. > > <starting opinion>Not that I expect this to help at all. The LLDB integration > is just plain is buggy. I'll assume none of the pertinent developers at Digia > actually use LLDB to debug. I bet they all use GDB because the LLDB > integration sucks. Such an evil circle to be in. Clearly no "dog fooding" > going on.</starting opinion> > > And yes, the nightly builds of QtCreator are buggy. There is a crasher in the > Clang code model where it tries to supply the editor with a completion hint > but crashes instead. And then the editor just gets slower and slower as you > type. I found a build from Sept 10 that _mostly_ works, at least the editing > mostly works. Only crashes a few times an hour. Just remember to "save often”. I think I have seen this slow-down behavior too. Qt Creator crashed 3 or 4 times yesterday under OS X 10.10.5 and maybe once under Windows too. And yes I lost a few lines of work today that had to be recreated. -Ed > > -- > Mike Jackson > > _______________________________________________ > Interest mailing list > [email protected] > http://lists.qt-project.org/mailman/listinfo/interest This email and any files transmitted with it from The Charles Machine Works, Inc. are confidential and intended solely for the use of the individual or entity to which they are addressed. If you have received this email in error please notify the sender. Our company accepts no liability for the contents of this email, or for the consequences of any actions taken on the basis of the information provided, unless that information is subsequently confirmed in writing. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. Finally, the recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. _______________________________________________ Interest mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/interest
