[Qt-creator] Latest 3.6.0-rc1 & Debugging on OS X

Ziller Eike Eike.Ziller at theqtcompany.com
Tue Dec 15 10:07:44 CET 2015 

> On Dec 14, 2015, at 5:14 PM, Mike Jackson <imikejackson at gmail.com> wrote:
> 
>> 
>> On Dec 14, 2015, at 9:43 AM, Ziller Eike <Eike.Ziller at theqtcompany.com> wrote:
>> 
>>> 
>>> On Dec 14, 2015, at 2:53 PM, Mike Jackson <imikejackson at gmail.com> wrote:
>>> 
>>>> 
>>>> On Dec 14, 2015, at 4:07 AM, Ziller Eike <Eike.Ziller at theqtcompany.com> wrote:
>>>> 
>>>>> 
>>>>> On Dec 11, 2015, at 5:22 PM, Mike Jackson <imikejackson at gmail.com> wrote:
>>>>> 
>>>>> 
>>>>>> On Dec 11, 2015, at 1:42 AM, Ziller Eike <Eike.Ziller at theqtcompany.com> wrote:
>>>>>> 
>>>>>>> 
>>>>>>> On Dec 10, 2015, at 19:15, Mike Jackson <imikejackson at gmail.com> wrote:
>>>>>>> 
>>>>>>> I should have noted that I am running OS X 10.10.5 and Xcode 6.4. I have no idea if I can move up to Xcode 7.x and still use Qt 5.5?
>>>>>> 
>>>>>> As far as I know there are no issues with that. I’m using Qt 5.5 on El Capitan on my Notebook as well.
>>>>> 
>>>>> I may try Xcode 7.2 over the weekend on a test machine. Xcode 7 tolerates CMake projects better than the 6.x series did.
>>>>> 
>>>>>> 
>>>>>>> We have to self compile due to our requirement for C++11 support.
>>>>>> 
>>>>>> Why do you need to compile Qt yourself for that? We use C++11 in Qt Creator and use the default Qt package build for that (and CONFIG+=c++11 in our .pro files).
>>>>>> 
>>>>>> Br, Eike
>>>>> 
>>>>> The default Qt packages turn OFF C++11 support which means that the Qt Frameworks are linking against libstdc++ which is the older NON-C++11 compliant package.
>>>> 
>>>> Default Qt binaries link against libc++ since Qt 5.4 (which removed support for OS X 10.6).
>>> 
>>> Maybe I am confused about the C++11 support when compiling Qt. The downloadable Qt 5.5.1 packages specifically have C++11=OFF in the configure line.
>> 
>> Not sure what you mean by that or where you see it.
>> For me mkspecs/qconfig.pri from the binary Qt package from qt.io contains "c++11" in its QT_CONFIG line, and the frameworks link against libc++ (checked with otool -L). The QT_CONFIG+=c++11 means that the Qt modules are compiled with C++11 support, and on OS X that also means CONFIG+=c++11 for applications built against it with qmake (mkspecs/features/mac/default_post.prf).
>> 
>> Br, Eike
> 
> http://code.qt.io/cgit/qtsdk/qtsdk.git/tree/packaging-tools/bld_config/configure_mac_opensource
> 
> One of the last arguments is -no-c++11

No idea for what or if that file is used anywhere. The actually used configure options seem to be here:
http://code.qt.io/cgit/qtsdk/qtsdk.git/tree/packaging-tools/releases

Br, Eike

>> 
>>> Does this mean that Qt itself does not use C++11 BUT it is linked against a C++11 compliant (libc++) library? OS X changed the default C++ library from libstdC++ to libC++ at 10.9 I believe. If this is the case then we might actually be able to go back to using the prebuilt Qt packages (Which is a good thing.. )
>>> 
>>> —
>>> Mike Jackson
>>> 
>>>> 
>>>> Br, Eike
>>>> 
>>>>> This has been causing issues with our projects where some of our 3rd party libraries link against libc++ with C++11 compliance turned on. We get spurious crashes and runtime issues unless we get all our our 3rd party libraries to specifically link against libc++. Since the default Qt packages have a minimum OS X runtime of 10.7 they will link against libstdc++. We crank up the minimum to 10.9 and config with C++11 support. This (and other config options to other 3rd party libs) have fixed our issues.
>>>>> 
>>>>> There were other benefits to moving to C++11 (like moving from boost::shared_ptr to std::shared_ptr) which allowed QtCreators code models (both Clang and the internal one) to offer completions MUCH faster than before and more completely.
>>>>> 
>>>>> —
>>>>> Mike Jackson
>>>>> 
>>>>>> 
>>>>>>> 
>>>>>>> Also note that my tests are quick and dirty. Just quick “does it launch quickly when compared to Xcode”.
>>>>>>> 
>>>>>>> Thanks
>>>>>>> Mike Jackson
>>>>>>> 
>>>>>>>> On Dec 10, 2015, at 11:33 AM, rpzrpzrpz at gmail.com wrote:
>>>>>>>> 
>>>>>>>> Thanks mike for doing this "guinea pig" work.
>>>>>>>> 
>>>>>>>> I spend all of my time on OSX and Qt, so not losing developer tool effectiveness
>>>>>>>> on this OSX platform is really important for 5.6. (even though I can tied up on 5.5.1 right now and cannot donate cycles.)
>>>>>>>> 
>>>>>>>> I am running El Capitan, so that may be a sticking point in late January for 6.5RC.
>>>>>>>> 
>>>>>>>> md
>>>>>>>> 
>>>>>>>> On 12/10/2015 10:28 AM, Mike Jackson wrote:
>>>>>>>>> 
>>>>>>>>>> On Dec 10, 2015, at 4:54 AM, Ziller Eike <Eike.Ziller at theqtcompany.com> wrote:
>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>>> On Dec 2, 2015, at 8:34 PM, Mike Jackson <imikejackson at 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.Stenger at 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-bounces at qt-project.org> on behalf of Mike Jackson <imikejackson at 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 at qt-project.org
>>>>>>>>>>>> http://lists.qt-project.org/mailman/listinfo/qt-creator
>>>>>>>>>>> 
>>>>>>>>>>> _______________________________________________
>>>>>>>>>>> Qt-creator mailing list
>>>>>>>>>>> Qt-creator at qt-project.org
>>>>>>>>>>> http://lists.qt-project.org/mailman/listinfo/qt-creator
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> _______________________________________________
>>>>>>>>> Qt-creator mailing list
>>>>>>>>> 
>>>>>>>>> Qt-creator at qt-project.org
>>>>>>>>> http://lists.qt-project.org/mailman/listinfo/qt-creator
>>>>>>>> 
>>>>>>>> _______________________________________________
>>>>>>>> Qt-creator mailing list
>>>>>>>> Qt-creator at qt-project.org
>>>>>>>> http://lists.qt-project.org/mailman/listinfo/qt-creator
>>>>>>> 
>>>>>>> _______________________________________________
>>>>>>> Qt-creator mailing list
>>>>>>> Qt-creator at qt-project.org
>>>>>>> http://lists.qt-project.org/mailman/listinfo/qt-creator
>>>>>> 
>>>>>> -- 
>>>>>> Eike Ziller, Senior Software Engineer | The Qt Company
>>>>>> Digia Germany GmbH, Rudower Chaussee 13, D-12489 Berlin
>>>>>> Geschäftsführer: Mika Pälsi, Juha Varelius, Tuula Haataja
>>>>>> Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 B
>>>>> 
>>>>> _______________________________________________
>>>>> Qt-creator mailing list
>>>>> Qt-creator at qt-project.org
>>>>> http://lists.qt-project.org/mailman/listinfo/qt-creator
>>> 
>>> _______________________________________________
>>> Qt-creator mailing list
>>> Qt-creator at qt-project.org
>>> http://lists.qt-project.org/mailman/listinfo/qt-creator

More information about the Qt-creator mailing list