[Interest] Deploying Qt to MacOs still...errr, sucks?

[Michael Jackson]

On Feb 11, 2015, at 1:43 PM, René J.V. Bertin <rjvbertin at gmail.com> wrote:

> On Wednesday February 11 2015 13:27:37 Michael Jackson wrote:
> 
>> I was also the one that reported the MacPort dependency. And I am not really comfortable just changing the install_name to point towards another library of the same name but unknown as to how it was compiled or with what options. I'll count that as another obvious bug and not put in a bug report.
> 
> This is a bit of a delicate matter. If Digia indeed use MacPorts to provide certain dependencies, it will not be that easy to avoid generic libraries like those reported, because it is MacPorts' principle to provide those libraries itself, but compiled with the default system compiler.
> This is of no consequence as long as those in MacPorts are not so far ahead of the ones Apple ship that they become ABI incompatible. Nothing stops Digia from setting up (or having set up) a MacPorts environment that uses the same versions as Apple, and "simply" mark these ports as held, to borrow a Debian term.
> 
>> Now. if QtCreator could just better understand CMake projects I think I could have a decent experience coding with Qt.
> 
> Do you use a lot of ObjC code? If not, you could have a look at KDevelop. I actually prefer it over Creator in most aspects. You'd still need Creator or Xcode for debugging, though, because KDevelop doesn't support lldb yet.
> 
> R.
> 

Generally, because LLDB is still "new" when compared to gdb, *every body's* support for LLDB is very much sub-par at best for OS X. If you switch to Linux and use QtCreator to debug then the experience is enjoyable. Same thing for Visual Studio on Windows. Enjoyable. Debugger does not lockup, crash, I can see actual values in Qt Variables. You, know, stuff I would expect from debugging any modern C++ program. But the combination of OS X, with LLDB, CMake and QtCreator is just a non-starter at this point. Maybe someday. But not now.

I have had wonderful and enlightening conversations with a some of the Qt developers who kindly explained the issues as to why things are in the state they are in. I thank those that have enlightened me. I now have the proper perspective to make decisions for my company's development environment that allow us to be the most productive.

Cheers
Mike Jackson