Also just wanted to feedback to the QtDevelopers that recent Clang code model code fixes have significantly improved the completion time for, at least, our codes. The editor has gone from unusable to actually usable now. Still a bit slower than Xcode and Visual Studio, but fairly usable now.
The debugging start up is just about normal now but getting some variables like “this” take an extended amount of time (like 15~20 seconds) to gather and display. Not sure if this is because of some deep hierarchy in our classes or something else. But generally the 3.6 release is starting to shape up nicely and is becoming very usable on OS X again for our project setup*. — Mike Jackson * CMake + Boost + Qt 5.5 + ITK + Qwt + Eigen + TBB + HDF5. > On Dec 10, 2015, at 11:28 AM, Mike Jackson <imikejack...@gmail.com> wrote: > >> >> On Dec 10, 2015, at 4:54 AM, Ziller Eike <eike.zil...@theqtcompany.com >> <mailto:eike.zil...@theqtcompany.com>> wrote: >> >>> >>> On Dec 2, 2015, at 8:34 PM, Mike Jackson <imikejack...@gmail.com >>> <mailto:imikejack...@gmail.com>> wrote: >>> >>> Hello, >>> The issue seems to be resolved. I can debug again. BUT the start up time >>> when launching my application is very long. It seems to be taking about 1 >>> minute to launch to my gui. >> >> Could you please take a look at the debugger log, what it does during that >> long time? >> >> Br, Eike > > The Dec 10 nightly build of 5.6.0 seems to have fixed these issues. The > debugger startup is back to normal. The initial gathering of variables on > first break is still a bit slower when compared to things like Xcode but is > very usable. > > Thanks > Mike Jackson > > > >> >>> That was with NO breakpoints active. If this last piece is being worked on >>> then I think the 3.6 release is shaping up very nicely to make a comeback >>> on OS X. I have switched back to the QtCreator code model and the >>> completion speed and quality is very close to the likes of Visual Studio >>> and Xcode. Keep up the great work. >>> >>> Mike Jackson >>> >>>> On Dec 1, 2015, at 4:38 AM, Stenger Christian >>>> <christian.sten...@theqtcompany.com >>>> <mailto:christian.sten...@theqtcompany.com>> wrote: >>>> >>>> Hi Mike, >>>> >>>> can you please re-check with the newest snapshot? The issue you've >>>> mentioned should have been fixed yesterday afternoon, but I assume the >>>> package of Nov 30th did not include this fix. >>>> >>>> Kind regards, >>>> Christian >>>> >>>> >>>> ________________________________________ >>>> From: Qt-creator <qt-creator-boun...@qt-project.org >>>> <mailto:qt-creator-boun...@qt-project.org>> on behalf of Mike Jackson >>>> <imikejack...@gmail.com <mailto:imikejack...@gmail.com>> >>>> Sent: Monday, November 30, 2015 7:08 PM >>>> To: qt-creator >>>> Subject: [Qt-creator] Latest 3.6.0-rc1 & Debugging on OS X >>>> >>>> The latest RC’s for the 3.6.0 release are really starting to look nice but >>>> just wanted to report here a few issues with the debugging on OS X to see >>>> if anyone else was seeing the issues? >>>> >>>> Basically with the latest nightly from NOV 30 2015 the debugger errors out >>>> and does not start up. One of the nightlies from mid-last week would start >>>> up but would just spin LLDB at 100% indefinitely and never seem to come >>>> back with the locals and stack when attempting to stop at a break point. >>>> >>>> This is with OS X 10.10 (Yosemite) and Xcode 6.4. >>>> >>>> Thanks >>>> Mike Jackson >>>> _______________________________________________ >>>> Qt-creator mailing list >>>> Qt-creator@qt-project.org <mailto:Qt-creator@qt-project.org> >>>> http://lists.qt-project.org/mailman/listinfo/qt-creator >>> >>> _______________________________________________ >>> Qt-creator mailing list >>> Qt-creator@qt-project.org <mailto:Qt-creator@qt-project.org> >>> http://lists.qt-project.org/mailman/listinfo/qt-creator >>> <http://lists.qt-project.org/mailman/listinfo/qt-creator>
_______________________________________________ Qt-creator mailing list Qt-creator@qt-project.org http://lists.qt-project.org/mailman/listinfo/qt-creator
