-
Notifications
You must be signed in to change notification settings - Fork 0
Ultimate question #18
Comments
@antis81 Any opinion on that? I'm just about to compile Qt5.2 and see what happens :) |
@scunz Tried to compile Qt5.2 on OSX 10.6.8 - with no luck so far :(. The GCC version compiles (~3h) but doesn't want to install. The clang version breaks early (<1 min.) with some error on an assembler call. I'll send you the logs. Maybe you have an idea what to do about it ^^. Other than that, I think switching to the 5.2 version is the right direction and we should do it as soon everything's setup alright. |
@antis81 @fibrethil As for Mac OS X 10.6, they actually say that they don't "officially" support it. Hoever, I am at least expecting it to run on Mac OS X 10.6. First of all, I am disappointed by the fact that Yet - that's not all... Btw - at the same time, I was unable to compile a debug build of Qt 4.8.5. Again, had to change some really internal things in Qt and Qt Creator 3 on Qt 5.2 now runs somewhat smooth (contrary to the QTC3/QT52 compiled by Digia on my Mac at work). Did not test Windows, yet. But I am not really looking forward to do that, actually :-) |
@scunz With your tips via mail I managed to build the Qt 5.2 Version of MGV 👍 ❤️ Everything runs out of box (well, after some headaches on building qt5 itself). One thing I noticed is: The main menu is missing. Maybe HIC is not called correctly? I use the following line for cmake in QtCreator: I installed via Homebrew In addition, I added @claus007 FYI 😄 |
What you are seeing, is actually macgitver/libHeaven#20 So, we know now that it is not only related to Mac OS X 10.8. If 10.6 got the bug, 10.7 will probably, too. i've just finished the freaking 2,1GB X-Code download for 10.9. The "Smarter but still stupid" Qt5 configure tries to invoke I did not manage to get Qt 4.8.5 to compile WebKit on Mac OS X 10.9. It still needs all of the patches from macports. Let's see how the situation with Qt 5.2 is. |
Working on new abstractions right now. Got some ideas just 2 days ago; but all the stuff we're doing in mgv's |
Same here just with 10.6.8 😦 - also installed a full Xcode for that reason. |
I want the simplicity of Qt4 back and combined with the new features of Qt5. That would be really: 🚀 |
so.... Mac OS X 10.9 requires some stuff, but generally works. Qt5.2 did compile (almost) smoothly. It uses C++11 - which is natural, since OSX 10.9 demands XCode 5.0 and with it the latest version of clang. However, this also means that we have to enable C++11, too and link to stdc++ (I didn't find a way to solve this, but didn't look too hard either). As far as I know, Though, I know that the market share of 10.6 is still roughly at 33%. So, @antis81 since I also know that you're one of the users that don't upgrade their OS: I'd really like to have an understanding about why people don't upgrade to 10.7, 10.8 or even 10.9. Are there technical, philosophical, artistic or monetary reasons behind that? Or is it something I'm currently totally unable to think of? :) |
As we are using plain old world stuff made by normal people, there's nothing transcendental to think of here 😄. The reasons are a combination of the four you're stating.
Besides that, switching to linux as primary OS is also an option for me. |
Btw. just enhanced the qt5 package in homebrew being able to build the docs and without qt tests 😄. Currently |
Let's re-animate this one. I think, this is just the right time to do the switch to C++11. We already made the switch to Qt5. Advantages:
Disadvantages:
@scunz Btw. Digia released QtCreator 3.2.2 yesterday, that addresses the issues with Xcode6. Give it a chance. |
As long as you use GCC on Windows, it is more or less supported. According to Blogs / News, Microsoft might release a compiler (the one to follow MSVS 2013), that might support half of C++11... If you want to support old OS X, you have to do compiler detection and use lots of DEFINE and IFDEF in the code. Same applies if you want to support the Microsoft Compiler. Both is in my opinion a REQUIREMENT still. So, I cannot see how the code might get more readable :) As for cool features of C++11 - can you name one? Just one! :) To make any use of the speed improvements that can be achieved by a C++11 compiler vs a C++03 compiler, endless kilobytes of boiler plate code are required. The concepts for which have to be understood really good, to get them right. Also, you should really know all the time, if copy or move assignment is appropriate (which again requires deeper knowledge of the language). Otherwise there will be lots of problems... |
Yeah exactly. But I think it is really not worth it. So why should we stick on old compilers? I know I own one of these by myself (OSX 10.6 again). This is why I looked out for alternatives and found a very good one. Isn't this is just about development and not about the final results. I don't know of any projects compiled with C++11 yet, but aren't they still running on old machines as well? It would be crazy if they are not.
Depends on what you define as 🆒 😎. For me, the var initialization is an example for a cool feature. On one hand, this is less to write. Plus, it brings c++ syntax more close to c#/java syntax, which - for me - is a good thing. But, when taking this example together to be compatible with old compilers, you'd have to write:
So to me, it is basically just the decision to JUST DO IT! (copyright infringement completely unintended 😄) It is definitely easier this way. |
And ... forget about the speed improvement thing. It is never a real argument - we should more care about the efficiency of the diff viewer (it really sucks on large diffs with >100 files changed) than this one. |
When should we stop supporting Qt4? @antis81
Let me try to summarize some points here:
Pro Qt5-Only:
QFusionStyle
, which is what I actually want to base BlueSky upon.BlueSky
config from xml to easier to use json structures.Contra Qt5-Only:
QPixmap
and co. Will be solved with the upcomming Qt5.2.CMake
magic to get themodules.json
files to show up in QtCreator.qmake
invocation to determine correct Qt5 modules paths. The proposed way of initializing aCMake
cache is just too hard IMHO.The text was updated successfully, but these errors were encountered: