Xcode 6...
-
Downloading 10.8.sdk doesn't seem to be an option this time. I'd like to know if anyone has gotten lldb working before I go the route of using 10.9.sdk.
-
I've retry with a simple example, since my project is non-trivial. I tried qtbase/mainwindows/application and I still cannot launch with lldb, it just hangs. I use gdb installed from macports, not perfect but works.
I'd say keep Xcode 5 around if you're not ready to do that.
As for compiling Qt 5.3.2 with Xcode 6 and retaining OS X 10.6 compatibility, I do this:
@> export PATH=/usr/bin:/bin:/usr/sbin:/sbin
./configure -debug-and-release -prefix /usr/local/Qt-5.3.2 -nomake examples -sdk macosx10.9 -no-c++11
make
make install
make generate_docs
make qch_docs
make install_qch_docs@Note the "-no-c++11"
-
Like Sandy says, Xcode 6 debugger does not work inside Qt Creator. So the answer is pretty clear here that Qt just isn't ready for Xcode 6, and we are all better off just sticking with Xcode 5.1.1. Nice thing about Apple is that the various Xcode versions are completely self contained. So I just renamed Xcode.app to Xcode6.app and then reinstalled Xcode 5.1.1 as Xcode.app. And Qt Creator found all the compiler and debugger tools.
Sandy, can you post instructions on setting up gdb for those nuts who really want to transition to Xcode 6?
-
Hi everybody,
I had the same problem yesterday. I just had to change from "macosx10.8" to "macosx10.9" in ~/Qt/5.3/clang_64/mkspecs/qdevice.pri
You'll be able to use online installed Qt
-
What about debugging?
-
Oh sh*t, I haven't debug anything since I upgrade...
Looks like I'll downgrade to 5.1.1 >_> -
About gdb:
I installed gdb with macports, it end up in /opt/local/libexec/gnubin/gdb. Go in Preferences / Build & Run / Debuggers and add a new debugger with that path. Then go to Preferences / Build & Run / Kits and you can now select that new debugger for your Qt kit.
Note 1: it's not perfect, my debugging experience is not as stable as it used to be.
Note 2: macports also provide a "gdb-apple" port, which is a gdb with some Apple's patches, gdb that was used before they switch to lldb. Maybe I'll give this one a try too.
Note 3: Keeping Xcode 5 around is probably a wise advise for now.
-
Hi
I change the 'macroosx10.8' to macroosx10.9 as Max13 mentioned above (thanks for that tip Max13) and set the 'Run Settings" for debug to "Run in terminal" mode for the debug and it works! (It doesn't work in view "Application output")
-
For those who want to use lldb from QtCreator without downgrading XCode, if you're willing to risk running unstable code, you can grab lldbbridge.py from the git repo at https://qt.gitorious.org/qt-creator/qt-creator/raw/4d12c017de5cf452480d6a627c927ae8c4278300:share/qtcreator/debugger/lldbbridge.py and use it to replace Qt Creator.app/Contents/Resources/debugger/lldbbridge.py. I did that, and now I can use lldb from XCode 6.0.1 in QtCreator 3.2.1.
-
One more thing.
If you just reinstalled Mavericks and are searching for XCode 5, it is no longer available in the App Store.
Here are a few download links right from Apple servers.
http://stackoverflow.com/a/10335943 -
I confirm that Debugging in Qt Creator lldb with XCode 6 works only if "Run in terminal" checkbox checked.
So I think solution is not so far. -
Will the Qt 5.4 package and its bundled Qt Creator support Xcode6 out-of-the box, or will we still need to perform these 1 or 2 hacks (change the qdevice.pri file and update lldbridge.py manually)?
I tried looking in Qt JIRA to find out, but wasn't able to find the pertinent issues. (I did see this bug https://bugreports.qt-project.org/browse/QTBUG-41838 but it was not addressed and perhaps it was a duplicate or entered in the wrong category.)
-
[quote author="VStevenP" date="1413498920"]Will the Qt 5.4 package and its bundled Qt Creator support Xcode6 out-of-the box, or will we still need to perform these 1 or 2 hacks (change the qdevice.pri file and update lldbridge.py manually)?
I tried looking in Qt JIRA to find out, but wasn't able to find the pertinent issues. (I did see this bug https://bugreports.qt-project.org/browse/QTBUG-41838 but it was not addressed and perhaps it was a duplicate or entered in the wrong category.)
[/quote]Qt Creator 3.2.2 works fine without hacks.
-
Do you know what version of QtCreator will be bundled in the Qt 5.4 package? Is it 3.2.2 or some change list after that?
It's important that I understand whether the Qt Creator that is bundled with Qt 5.4 will suffice.
-
[quote author="VStevenP" date="1413499813"]Do you know what version of QtCreator will be bundled in the Qt 5.4 package? Is it 3.2.2 or some change list after that?
It's important that I understand whether the Qt Creator that is bundled with Qt 5.4 will suffice.[/quote]
As I remamber they always include Qt Creator latest version.
Maybe it will be 3.2.2 or maybe newer, but I think it will not be deprecated version. -
It's also important for me to understand whether Qt 5.4 package will not have this problem at all
-
Thank you for your info.
-
[quote author="VStevenP" date="1413500037"]It's also important for me to understand whether Qt 5.4 package will not have this problem at all[/quote]
I think you don't need to worry about it. They do the best.
Just interesting, why it so important for you? Any way, it is not so hard to edit txt file to fix this. -
When you work in a company with a bunch people wanting to use a tool, it's easier to manage things if you upgrade tools together, such as Qt. Some people who use the tool are less technical and not good at hacking things. Some are very good, but don't want to work with experimental debugger code.
Apple released XCode6 and it reminds everybody everyday that it's available. Everybody wants to upgrade to it due to the constant annoying reminders. But that's not a good enough reason to upgrade a tool. One should upgrade to Xcode6 when one's toolset is ready to handle it without hacks, to make it easy for managing the rollout in the organization.
This is why.
-
[quote author="VStevenP" date="1413500583"]When you work in a company with a bunch people wanting to use a tool, it's easier to manage things if you upgrade tools together, such as Qt. Some people who use the tool are less technical and not good at hacking things. Some are very good, but don't want to work with experimental debugger code.
Apple released XCode6 and it reminds everybody everyday that it's available. Everybody wants to upgrade to it due to the constant annoying reminders. But that's not a good enough reason to upgrade a tool. One should upgrade to Xcode6 when one's toolset is ready to handle it without hacks, to make it easy for managing the rollout in the organization.
This is why.[/quote]
XCode 6.1 beta + Qt 5.3.2 + Qt Creator 3.2.2 works good for me and no more bugs found.
It was not big problem in Qt Creator, debugger worked fine even in 3.2.1 (only in terminal mode), there was problem in Qt Creator config files only.
So I think there is no reason to worry about next update.
