Qt newcomer setup is a joke.



  • Why is Qt so bad.. the installer for it is pretty crap and never gets anything setup right
    The QT tools for VS2017 are still not working properly

    As someone new to QT I think its pretty shitty, like where is professionalism in any of it.. the uninstaller for QT doesn't even remove most of its crap

    Error while building/deploying project calculator-qml (kit: Desktop Qt 5.8.0 MSVC2015_64bit)
    When executing step "qmake"

    Can't even get an installer that gets all the required files and sets up the relevant toolchains properly... just a mess

    Maybe in another year it will be less rubbish probably not.

    [Moved to Tools ~kshegunov]



  • @NatK Well, "works for me". I don't know about VS2017 (I don't think it's supposed to be supported yet) but otherwise the things you mention have worked for me, as long as I have followed the documentation.



  • MIght be your rubbish OS. Installs great on linux.



  • @NatK I've installed on linux, osx, and windows using the installer, works great every time.

    I've also built it from source many times and had that work, although that one can be really tough in windows. That's not Qt's fault but windows compilers that are the issue though.

    Sounds like your configuration is wrong since it looks like it's using the wrong toolchain.

    As for the negative comments about Qt's professionalism .. Qt has been professional level software for about 20 years now. I have personally used it almost 16 at my company. I have worked with many large corporations (multi-billion dollar companies) and never heard any complaints on it being hard to set up or non-professional. I would guess you are pretty new to programming or at least configuring build environments if you are having that much trouble. No shame in that, but don't blame the tool. Just practice, ask for help (nicely), and get better. Then you'll see how really well put together Qt is. :)



  • "Sounds like your configuration is wrong since it looks like it's using the wrong toolchain."

    Well I haven't done anything with the toolchain.. simply installed Qt using the online installer.. this is all the stuff it had selected by default.. must have amounted to a few gigs to download ~9gb..
    http://i.imgur.com/rqJyHhp.png
    http://i.imgur.com/NXb43Eu.png

    a bunch of msvc versions at 1gb a piece going as far back as 5.6 to a 5.9beta.. .. I obviously just wanted to use 5.8 which I assume to not be too old or a buggy mess.

    but even after installing all that, and using qt creator, and trying out a few example projects.. it fails to compile any due to the useless error as posted already, so shit just ain't setup properly even with the installer, which is complete rubbish.. and why isn't vs2017 supported, the built in ide with qt creator is pos I just wouldn't want to use given a choice to use vs instead.. and vs2017 has been out for testing for ages now, obviously I have no interest to install vs2015 and the qt addon (probably also has stupid setup issues), now when qt installer can't even set up its shit for basic trying out of things.

    "Qt has been professional level software for about 20 years now"
    Well its amazing its lasted this long, and I don't get that impression of professionalism from the documentation. I get the impression people here just stick to a old versions because they already know how janky the releases are to setup everytime.

    "MIght be your rubbish OS. Installs great on linux."

    That's funny because I'm installing it on windows to make a start on working on multiplatform software so that the software I build does work on other platforms besides windows.. because well linux software eco system is a pile of fking shit that feels and works about as well as WinXP did over a decade ago.. and even then its buggy and has piss poor ux.. that I still have no reason to want to actually use it as a default OS, so best I could do is at least build my own software on platforms and frameworks where they will be able to work on linux in the future.. but hey good start on encouraging that buddy .. no wonder your favorite os is a desolate wasteland of mediocre crap.

    "but otherwise the things you mention have worked for me, as long as I have followed the documentation"

    perhaps the installer should provide a link at the end of installing, under the check box that says Launch Qt creator.. where you expect its example stuff to.. to actually fucking work.. but perhaps the documentation will reveal some arcane bullshit to do still. Which sadly its professional software installer couldn't have achieved..20years of professional level software design my ass.



  • @NatK said in Qt newcomer setup is a joke.:

    Well its amazing its lasted this long, and I don't get that impression of professionalism from the documentation. I get the impression people here just stick to a old versions because they already know how janky the releases are to setup everytime.

    Well I'm always cutting edge. And like I said my company contracts to major corporations. This isn't piddly stuff from newbies that just started into the cross platform world. It's major embedded applications and cross platform guis. One of the projects I've worked on has a 2GB source base.

    If Qt wasn't the best for the job people like me wouldn't use it. Companies like the ones I contract to wouldn't use it. You'd be hard pressed to push a license that cost a large company 500K to use Qt if it wasn't awesome at what it does. But in the grand scheme of things 500k isn't much when you consider the developers working on the project cost at least 120k each.

    I'm sorry you had a tough time installing it. It doesn't go like that for most people. Since you didn't configure it, it sounds like it picked up multiple visual studio's installed on your system and got confused. That is the toolchain part. I know you said you didn't set up the toolchain but that is part of the problem. There's only so much guessing an installer can do based on your environment. If you had a clean environment things would work right out of the box. I've installed it many many times and don't ever have issues. Sometimes the toolchain guessing gets messed up (windows only) and you have to correct it. And for the record the toolchain has nothing to do with Qt. That is whatever compiler you choose. If you have it configured poorly on your system there's only so much that can be done to guess correctly. Hence the reasons Creator allows for setting up custom toolchains and changing the default one.

    no wonder your favorite os is a desolate wasteland of mediocre crap

    I've had a pretty distinguished career so far. I guarantee you've used my software in your day to day life. I've written more for linux in the last 10 years than I have for windows. If you swiped a credit card or bought gas somewhere you've hit on something I wrote at some point. All for embedded linux systems. So wasteland probably isn't the right word there. If you're talking about mediocre not-so-useful desktop applications then yes windows has a lot more apps out there than linux does. But the real stuff all runs on non-windows oses. Unless you somehow run a windows phone when the rest of the world uses android or iphones. Or you use credit card terminals in your purchases that run on windows ce... oh wait, there aren't any. You get the point.

    Assuming you're just starting out in learning to code, so here's some advice:

    1. concentrate on cross platform right from the start... trust me you'll make a lot more money and be a lot more valuable to a company. I won't even hire windows only developers any more, it's a waste of a resource and they tend to do things wrong.

    2. learn to be more polite. You're supposed to be professional and your posts are full of profanity and lack rhetoric. Software engineering jobs will get rid of someone that acts like that in a heartbeat. I've seen it happen. We're a polite, friendly, and educated group of people.

    3. when you get frustrated with something not working, the best thing you can do is learn why. Understanding the underneath is what will make you a good engineer. Bad ones are a dime a dozen and unemployed.

    Oh and finally, you don't have to use Qt Creator. I've never used it a single time and I've written Qt apps for many years. Use whatever IDE you prefer. CLion, slickedit, gvim, visual studio, eclipse. Qt works with all of them very easily.


  • Moderators

    @NatK said in Qt newcomer setup is a joke.:

    Error while building/deploying project calculator-qml (kit: Desktop Qt 5.8.0 MSVC2015_64bit)
    When executing step "qmake"

    That's only part of the error message. Can you please post the full error message?

    Also, you've installed the MSVC 2015 version of the libraries. Do you have MSVC 2015 installed?



  • @JKSH

    Error while building/deploying project calculator (kit: Desktop Qt 5.8.0 MSVC2015_64bit)
    When executing step "qmake"

    "Could not find qmake spec 'default'.
    Error while parsing file C:\Qt\Examples\Qt-5.8\widgets\widgets\calculator\calculator.pro. Giving up."

    That's what it says..

    Anyway the installer I would expect by default to have predefined setup where things needed are all put in place and setup with a working kit for that platform qt is installed onto. So at least the qtcreator example projects actually work and compile.. where getting started with a working environment for a newbie isn't just some precursor to the level bat shit crazy setups and trawling of the internet to find solutions to what shouldn't be problems in first place, if this was really that professional.. ... and maybe an advanced installer.. where it can try do guess work on my system setup and generally lead users onto doing searches over errors and see tons of stackoverflow posts from other users who have qt installer issues because its really not that great.

    " Hence the reasons Creator allows for setting up custom toolchains and changing the default one."

    I'm all for that and doing custom things and going advanced later, just not right after installing it, where the expectation from a newbie standpoint is it should by default be setup to where things generally work especially for example content. And not just left in a mess because somehow its a really good idea to be base an installer on assuming a system configuration instead without even checking if the user wants extra things downloading and installing to guarantee it does work for the installed platform, where it doesn't have to rely on assuming other things are already installed and will work for it.

    http://i.imgur.com/EN9XIso.png
    "qmake no compiler can produce code for this version"
    http://i.imgur.com/dmSiILM.png
    http://i.imgur.com/b7FWgAX.png

    " Since you didn't configure it, it sounds like it picked up multiple visual studio's installed on your system and got confused. " Vs2015 was installed previously and uninstalled before Vs2017.

    "your posts are full of profanity and lack rhetoric"

    :) you mean lack 'dialectic'? nah man when dealing with responses like this one... "MIght be your rubbish OS. Installs great on linux." going full on rhetoric trash mode works just fine for me :) and yes I was strictly talking about linux desktop, if only it wasn't so bad and it continues to be that way because well whatever that could be one big topic to talk about. Interestingly I'm doubting it just works great for everyone on linux either, because it sure hasn't looked that way in the searches I've gone through trying to find out what's wrong with this install on windows.


  • Qt Champions 2016

    @NatK said in Qt newcomer setup is a joke.:

    if only it wasn't so bad and it continues to be that way

    It isn't and it doesn't, but Bill Gates and his company of heroes are thankful for your support.

    Vs2015 was installed previously and uninstalled before Vs2017.

    Then you can't use a Qt precompiled for VS2015 with VS2017, you can thank for this the folks at Microsoft. They succeed gloriously in ensuring binary incompatibility between compiler versions. Also the VS installers leave behind stuff so auto-detection might or might not work properly, take your beef with your OS's vendor.



  • @kshegunov doesn't solve the problem.. the question is what does it take to make this actually work... installing vs2015 again? because vs2017 still isn't supported? even though its been out for months including beta/rc.... it seems you send blame over to MS for things that they have nothing to do with.. "They succeed gloriously in ensuring binary incompatibility between compiler versions" why would they

    more importantly wtf doesn't this glorious qt installer not notice that problem and notify the user is no compatible compiler.. really whole thing just looks like poor excuses at every level, blame blame blame zero accountability...

    its funny how a game engine company like Unity can make an installer and offer buildpackages for other platforms from osx, linux, android etc etc etc etc.. and allow anyone on osx,linux and windows develop a game for a chosen desktop version with only target platform differences to be aware of when programming things, and then just as easily compile that game to another platform without this much fking hassle in toolchain setups to get right... its almost like its made by professional people. Oh hangon it is, but qt on the otherhand what with its huge ass licensing costs.. can't even get the damn basics right and provide ease of use.. and you defend that.. what a joke.. I guess charging 120k salary to work with this multiplatform mess isn't a bad gig.


  • Qt Champions 2016

    @NatK said in Qt newcomer setup is a joke.:

    doesn't solve the problem..

    Oh, I couldn't tell by your demeanor you're after solving the problem, sounded more like blowing off steam.

    installing vs2015 again?

    Installing a matching compiler, be it vs2013, vs2015, mingw, intel C++ etc. The Qt version you install has to be compiled with the same compiler as the one you're going to use for development.

    because vs2017 still isn't supported?

    Apparently it isn't, or at least there are no precompiled binaries. You can compile Qt by yourself to get a vs2017 compatible binary if you're feeling adventurous.

    it seems you send blame over to MS for things that they have nothing to do with..

    It's their compiler, so it's their responsibility to provide binary compatibility. If the compilers don't generate a compatible ABI between versions then a new library build is required for each one of them, thus you get a proliferation of binaries. Qt's source is publicly available, so you can compile with whatever supported compiler you want, the fact that you have few precompiled binaries is just to make the developer's life easier. If you don't like it, then build the library yourself.

    why would they

    So we wouldn't have this discussion, or rather what appears more like a row. If they had done it, then you could have used the binaries for msvc2015, and since they haven't ... well, you get my point.

    not notice that problem and notify the user is no compatible compiler..

    Two reasons.
    For one it doesn't assume you have a compiler at all at the time of installation, and it shouldn't. Well designed tools don't depend on order of appearance. If it weren't like this you'd be here whining that you need to abide by a specific installation order.
    Secondly, it does notify you. When you open the kits tab in the configuration you have the fat red exclamation mark which should've grabbed the attention of a blind man.

    really whole thing just looks like poor excuses at every level, blame blame blame zero accountability...

    I'm not affiliated with the Qt company, so I have no reasons to make excuses for anything. I'm calling it as I see it. There's a documentation that comes with Creator and one that is for qmake. To reply in kind: RTFM!



  • @NatK said in Qt newcomer setup is a joke.:

    :) you mean lack 'dialectic'?

    No I meant rhetoric.. Here's the definition for you: the art of speaking or writing effectively.

    If your writing is full of profanity and aggressive statements it isn't really communicating effectively, thus it lacks rhetoric.

    Also since you very obviously don't want help but instead want to complain I'm out of this topic. Good luck learning Qt or whatever you choose.



  • I have to be honest I had a bad time installing QT, and I think it was because I had multiple visual studio installs from different versions. In the end I installed QT and mingw and everything is working now.

    However I didn't come on here ranting about it. I came here and asked for help and I got it.
    It is impossible for an installer to know everything about every system.



  • @Asimov Yea Qt with visual studio can be a pain. It's my least favorite compiler by far. Like @kshegunov said Microsoft is really bad about breaking the ABI.

    I'm sure Qt's installer could be better at autodetection but I find that it's more than adequate. But if you use a non-supported compiler then you should at least expect to have to change your toolchain setting. This guy just expected it to work magically. I wish all my software did that but that's just not how the world works. Well not until we get AIs at least. ;)

    I never even used the installer for Qt until probably 5.7 or so. I always built my Qt from source and installed it myself. And since I didn't use Qt Creator I didn't have IDE issues. I started using the installer lately out of laziness and it's always worked well for me but maybe that's because I know how to build it from source and install it on all OSes. Makes it a lot easier if you run into a minor setup issue. I definitely agree that windows is the hardest platform to install though. That is just the nature of windows in my opinion though. Nothing ever seems easy in windows once you've tried a posix OS.



  • I am mainly a windows user, but I am wondering if I will have any trouble installing QT on a Raspberry Pi. I play with linux on occasion, but I don't think I could be a 100% linux user as most of my software is windows only eg 3ds Max which is my main modelling software.

    Unfortunately I have to use visual studio for some stuff, but it is bloated to hell. The unity game engine and the atomic engine require visual studio. Qt for the most part installs pretty quick which is great.



  • @Asimov I spent 90% of my time in OSX or Linux. I have to build my software and test in windows but outside of that I try not to be in it.

    Yes everything in windows is super bloated, lol.

    And yes, you will have a very tough time installing for the Pi. It is a complicated install with an ARM cross compiler. It's doable even for beginners though.

    If you check my history you'll see I help people get it going all the time. So when you tackle that just post in the forums for the Pi here or ping me and I'll help you get it running.


  • Moderators

    @NatK said in Qt newcomer setup is a joke.:

    Error while building/deploying project calculator (kit: Desktop Qt 5.8.0 MSVC2015_64bit)
    When executing step "qmake"

    "Could not find qmake spec 'default'.
    Error while parsing file C:\Qt\Examples\Qt-5.8\widgets\widgets\calculator\calculator.pro. Giving up."

    That's what it says..

    ...

    http://i.imgur.com/EN9XIso.png
    "qmake no compiler can produce code for this version"
    http://i.imgur.com/dmSiILM.png
    http://i.imgur.com/b7FWgAX.png

    This means your system does not have a compiler that is compatible with the versions of Qt that you installed.

    Vs2015 was installed previously and uninstalled before Vs2017.

    As mentioned before, you have installed the MSVC 2015 versions of Qt.

    MSVC 2015 is not compatible with MSVC 2017.

    @NatK said in Qt newcomer setup is a joke.:

    the question is what does it take to make this actually work... installing vs2015 again?

    That is the most straightforward solution, if you want to get up and running quickly. You don't need to install the whole Visual Studio, just the Visual C++ 2015 Build Tools.

    If you do not want to install MSVC 2015 or its Build Tools, your options are:

    • Install the MinGW version of Qt along with the MinGW compiler (all from the saselectable from the Qt installer)
    • Wait for Qt 5.9 to be released (scheduled for 31 May). This will support MSVC 2017.
    • Build Qt from source, using MSVC 2017 (I don't recommend this option).

    because vs2017 still isn't supported? even though its been out for months including beta/rc....

    Qt 5.8 was released before MSVC 2017, which is why it does not provide precompiled binaries for MSVC 2017.

    The upcoming Qt 5.9 will provide precompiled binaries for MSVC 2017.

    more importantly wtf doesn't this glorious qt installer not notice that problem and notify the user is no compatible compiler..

    Qt is, in essence, a C++ library. As far as I know, C++ libraries usually depend on the programmer to have the relevant compiler in place.

    I agree that it would be very nice if library installers helped out the user more, but so far it has not been done.


  • Moderators

    The subject is pretty exhausted now but I thought I'd chip in, because there's a lot of FUD, misconceptions, dated info and simple prejudice about OSes, companies etc. here, and I'd like to clear at least some of it up (repeating some of the points already mentioned). A disclaimer - I'm not affiliated with any of the companies in question.

    • "Qt installer doesn't set up all the stuff when using Visual Studio" - The only thing it doesn't set up is, well, Visual Studio itself, and that's mostly due to legal reasons. Besides, the fact that it does set up other compilers is just a convenience step. You usually don't expect a c++ library (like wxWidgets, zLib or OpenCV) to set up your development environment for you, so the fact that Qt does in some configurations is actually more than others do.

    • "I expect the installer to set everything for the platform and generally do the right thing always" - That's the thing - on Windows there's more than one "platform" or "toolchain" that can be set up. There's even more than one variations of these toolchains, eg. source of MSVC compiler, Windows and DirectX SDKs, debugers, UWP, WinRT, device simulators etc. Some are automatic (the MinGW one), some are semi-automatic (the MSVC one) and some are manual(like mix and match VS2015 and 2017). If you're a programmer you know how it is and you know you can't support all possible configurations out there to the same extent.

    • "Qt with Visual Studio is a pain" - Depends on what you define as a pain. From my experience - install Visual Studio, (optionally) install Qt plugin, install matching Qt. Done. If you consider that hard, well... nothing anyone can do about it.

    • "Qt doesn't support VS2017" - Qt has supported VS2017 for a long time, most of it's beta and rc release cycle. I know because I used it all that time. The source of confusion is that "support" doesn't mean providing precompiled binaries. Qt doesn't provide precompiled binaries for beta (or rc) compilers. That's just a sane policy that reduces the amount of work on the release side. For Visual Studio the precompiled binaries were always provided for the latest finished VS version available at the time. This is true for the latest Qt too (5.8). At the time of its release the latest VS available was still VS2015. The next version of Qt (5.9) will continue this trend and provide binaries for VS2017. This doesn't mean Qt 5.8 doesn't support VS2017. It does, but it doesn't provide you with the convenient prebuilt binaries. You need to build them yourself.

    • "Qt creator is bad compared to Visual Studio" - That's a highly personal opinion that mostly depends on your needs. I use both on daily basis and find them both very useful - Qt Creator has a superior support for Qt itself, and when I need a quick project set up to test stuff it's invaluable. VS has, on the other hand, a better support from 3rd parties I use, like NVidia Nsight and the likes. These are all very personal scenarios and I think both IDEs have their usages. Let's not start a holy war about it. There's room for two (or more) and it's good to have options.

    • "MSVC 2015 is not compatible with MSVC 2017" - Well that's either true or false, depending on what you mean. Up to VS2015 MSVC compiler produced code binary incompatible with previous versions. So when choosing Qt's precompiled package you had to choose version built with exactly the same VS version you're using. That is no longer the case with VS2017. It's the first release officially binary compatible (binaries, crt and even STL) with previous one, and from what MS guys say, that's starting a new trend at MS that they intend to continue. There are "will see about that" kinds of voices so let me provide a data point for consideration - I've been using VS2017 executables linked to VS2015 Qt libraries for a couple of months now and I haven't had a problem with such setup yet.
      Entirely different subject is support of these scenarios in QtCreator. I hope it's obvious that it won't support all the scenarios you can think of right off the bat. The simple path is to install matching Qt and VS versions. That is as easy as it can get (couple of "next" buttons in the installers). If you want to mix and match Qt, MSVC and other libraries compiled with VS 2015 and 2017, then it's entirely doable but might require some manual steps in the IDE to set appropriate kits.

    • "since there are no Qt binaries for VS2017 do I have to install 2015?" - If you're fine with using VS2015's compiler then there are couple of ways you can obtain it - get VS2015(obviously) or get VS Build Tools 2015 (this includes only the toolchain and no IDE), or, and that's again a new one, if you already have VS2017 you can get the 2015 toolchain right from VS2017's installer. If you go with the last option you can use VS2015's Qt binaries and either a VS2015 or VS2017 toolchain right from the VS2017 IDE. Mix and match is fully supported now!

    • "Unity does it better, why can't Qt?." - Unity has a selected, very focused usecase and as a result a predefined toolchains for all the platforms it supports. QtCreator is a general purpose IDE that you can rig with toolchains modified to the extreme or even completely new ones. That's just comparing apples to oranges.

    • "Using Qt on Windows is hard, just use Linux" - that's just unreasonable. I can set up a Windows development environment with my eyes closed but I'm a child lost in a fog when sat down with Linux or Mac. I imagine it's the same for Linux folks when looking at Windows. The thing you already know will always look simpler. Don't give in to this way of thinking or you'll just spread FUD.

    • "Bill this, MS that..." - Let's be objective about this. For whatever beef one can have with MS it's plain unfair not to acknowledge the efforts they put in the last couple of years to take themselves out of their box and play nicer with the rest of the world (and by that I mean Linux, Apple, other toolchains, build systems, libraries and standard support). Take a look at the VC++ blog over the years. Yes, it takes time and old habits die hard, but the amount of demands, accusations, angry comments and just plain cold hate these guys had to endure and how they handled it and adapted is a sole reason I think twice before laughing at Windows jokes. Oh, and we're two CEOs past Gates now, catch up :)


  • Moderators

    Thank you for your thorough and objective comments, @Chris-Kawa.

    @Chris-Kawa said in Qt newcomer setup is a joke.:

    • "MSVC 2015 is not compatible with MSVC 2017" - Well that's either true or false, depending on what you mean. Up to VS2015 MSVC compiler produced code binary incompatible with previous versions. So when choosing Qt's precompiled package you had to choose version built with exactly the same VS version you're using. That is no longer the case with VS2017. It's the first release officially binary compatible (binaries, crt and even STL) with previous one, and from what MS guys say, that's starting a new trend at MS that they intend to continue. There are "will see about that" kinds of voices so let me provide a data point for consideration - I've been using VS2017 executables linked to VS2015 Qt libraries for a couple of months now and I haven't had a problem with such setup yet.

    I didn't realize that. That's very good news indeed!



  • @Chris-Kawa said in Qt newcomer setup is a joke.:

    "Bill this, MS that..." - Let's be objective about this. For whatever beef one can have with MS it's plain unfair not to acknowledge the efforts they put in the last couple of years

    I agree with everything you said, but just wanted to specially acknowledge this. As much as I've been a microsoft hater since about Windows XP due to the draconian activation evilness, they really have put forth a lot of effort to get better in the last few years.

    Making a lot of their software cross platform (finally) and generally acknowledging that linux exists and is only getting stronger was a very HUGE step for them. Kudos to Microsoft for that.

    I don't think I'll ever go back as a full time user. I still use it for testing my software and games though. I just like posix OSes too much to ever go back to MS. I mean they could surprise me with something amazing that changes my mind, but once you've used linux or osx it's really hard to go back. That being said I don't have the same issue with MS that I used to. In fact Apple is now starting to go down the evil corporation path since Jobs died. They are being worse than MS lately. Hopefully they flip that around before it's too late. They don't have the user base to survive through stupid decisions like MS did.



  • @ambershark
    I know you where you are coming from. I used to use an Amiga 1200 tower for years, and I swore I would never use windows(I learnt C and AmosBasic on the Amiga). I was one of the last Amiga users to change to windows. However the Amiga started to get left behind and I had to eventually succumb to the evil empire.

    I do actually like windows now, but I can agree there is a lot of bloat in a lot of applications.

    If for some reason I had to leave windows it would be linux and not a mac though.

    Will let you know when I get around to installing QT on the PI.
    Still trying to learn stuff at the moment.



  • I probably should just uninstall the mess and try out 5.9 at end of next month seeing as that's how long it takes to support the compiler vs2017 at an installer level which will probably still be crap by then aswel.

    However I get things compiling with qt5.8 via the qt shit installer, just had to install (stripped wouldn't want this thread to be useful to anyone else seeing all the great help, when they are also finding the qt installer a pile of shit and having similar problems because of it.) if only it was selected before ....it wasn't because obviously the shit installer thought an incompatible version of vs2017 compiler tools would work just fine.. yea sure,.. but then you still have to go setup that shit in the crapcreator options.. honestly guys thanks so fking much for helping and for spotting that in the pictures provided by a newbie, I'm sure you were well aware of that obvious thing not selected by default in the qt crap installer...if only that could have been pointed out sooner by you smart people.

    And I'd do the source compiled version but navigating qt website is just awful.. oversized fonts (actually OVERSIZED FONTS EVERYWHERE (except the forum weird that) , INCLUDING IN THE QT CREATOR HELP/EXAMPLE PROJECT INFO.. IT IS FUCKING SHIT, DO YOU NEED A 4K MONITOR JUST TO SEE EVERYTHING ON THE SCREEN >> FONT SIZES DON'T NEED TO BE FUCKING HUGE UNLESS YOUR DOC TEAM JUST DO IT TO MAKE UP FOR THE LACK OF ACTUAL WRITTEN CONTENT
    http://i.imgur.com/zHcpjCx.png
    http://i.imgur.com/nbvi40T.png

    HUGE FONTS, WHY QT? IT LOOKS CRAP, NOT PROFESSIONAL AT ALL!

    so yeh piss poor layouts and stupid amount of bad design.. no thanks, just trying to find the actual download location for the source files. Let alone trying to find actual help and guides that aren't either out of date, on some other site or styled in giant oversized fonts that look totally retarded like the qt document site, or on the qt forum where help is talked about a lot by professionals without actually fking helping at all.

    Not really my thing and quite frankly I don't trust it to actually have all the proper and update information, probably get half way through and find they changed some minor thing and forgot to update the setup guide info... considering they can't even be bothered to improve the installer for a decent experience for new users.

    @Chris-Kawa probably the most useful reply in this thread, though I disagree that Qt couldn't make it alot easier in toolchain pre setup for building to other platforms.

    "If your writing is full of profanity and aggressive statements it isn't really communicating effectively, thus it lacks rhetoric."

    You don't understand what rhetoric swearing is then, if you think profanity and colorful language can detract from something said in rhetorical form being anything less than rhetoric (if it is rhetoric at all), then you should go look up the differences between the dialectic and rhetoric. And what do you mean it isn't really communicating effectively .. I think you will find it communicates very effectively alot of the time, if it gets anyone to improve an issue is a whole nuther matter and not one I particularly care about either way here, it can stay shit its obviously intended to be that way by poor design.



  • @NatK
    Do you work for microsoft by any chance?

    PS. Saying shit multiple times eventually loses it's impact.
    I am not saying there are no problems with QT. I have found a few, but generally swearing is not going to solve anything.
    It just shows us the level you are at, and you will never get a constructive reply if you can't communicate without uttering a barrage of expletives.



  • @Asimov said in Qt newcomer setup is a joke.:

    if you can't communicate without uttering a barrage of expletives

    Yep. I swear a ton IRL but it seems just silly to take the extra time to write them down in a post online. If nothing else it's just more typing and it makes the person sound stupid. Kind of like typing in all caps. Plus you're actively swearing at people who you are asking for help. Seems counterproductive.

    Do you work for microsoft by any chance?

    Lol, I'm pretty sure if you can't configure visual studio as a toolchain it's pretty unlikely you work for microsoft.



  • @ambershark
    I have sworn when I have dropped a hammer on my toe and it aptly portrays my rage, but I find swearing in a professional forum does not have the same effect, when people need to communicate their information LOL

    Lol, I'm pretty sure if you can't configure visual studio as a toolchain it's pretty unlikely you work for microsoft.

    I suspect Microsoft and Cyberdyne Systems sent him here from the future to remove QT from global domination LOL.

    PS. It wouldn't happen on stack overflow ahem


  • Moderators

    and try out 5.9 at end of next month seeing as that's how long it takes to support the compiler vs2017

    You're just repeating what we already established is not true. The support for VS2017 is there and was there for a long time. There are precompiled binaries for the latest VS version available at release. In case of VS2017 that will be the Qt 5.9 release. Microsoft and Qt Company have different release cycles that don't usually sync. You can't realistically expect any of them to wait for the other with their product shipment. Qt releases about 2 major versions a year and a couple of minor versions every few months. I think that's quite a pace considering the size and scope of the library.

    which will probably still be crap by then aswel.

    Now that's just rude without any reason. As far as I can tell you're a new Qt user so I'm not sure what you're basing that on. With every new VS version in the past the next Qt release had provided binaries for it, available through the installer. That's also the plan now so what do you mean exactly by "still be crap"? It's not crap now. There are no binaries because there was no VS2017 released at the time. I hope I don't need to repeat that anymore.

    However (...) if only that could have been pointed out sooner by you smart people

    You're blaming people that out of their kindness spend their free time on a user's forum helping others that you didn't get a solution to your problem sooner. You're doing it in a sarcastic and childish way. Before you respond - please stop for a moment and think about that. How would you feel if this kind of behavior was presented towards you? Have you considered that maybe the way you behave detracted people from the actual problem you had?

    And I'd do the source compiled version but navigating qt website is just awful (...) yeh piss poor layouts and stupid amount of bad design..

    Please note that the usability of the website was indeed questioned a couple of times by various people. I'd consider changing your tone, because whatever useful feedback you might provide will not be heard this way. Again - try to imagine you're on the other side of this discussion - a "new guy" comes and behaves like you do. You're just pissing people off. If that's your goal you'll just cross the line eventually and get banned. All you achieve is make yourself look silly and anything useful you have to say won't get through. That's not what we want to do here.

    though I disagree that Qt couldn't make it alot easier in toolchain pre setup for building to other platforms

    That's fine. Could you provide some constructive feedback? And I don't mean statements like "piss poor" or "shit". I mean actual things to improve.
    Btw. I mentioned it already but you might not be aware - this is user's forum. We don't make design decisions here. If you want to provide feedback or have improvements ideas you can contact the devs on the mailing list. I'll warn you though, so you don't make the same mistake second time - this way of talking will get you absolutely nowhere in Qt community and will most likely just be ignored. Try to operate on less emotional and more technical level.

    You don't understand what rhetoric swearing is then (...)

    You need to understand that you're not among close friends that know you or everyday colleagues here. You've entered a worldwide community with established rules and types of behavior. Usually when you do that you're expected to at least respect and adhere to their conduct. Anything else is just disrespectful and bad manners. You're more than welcome to have an opinion. As evidenced in this thread users here do have different backgrounds and wildly different views on stuff, but please let your points across without offending people just because you can. We don't really censor stuff here (apart from spammers and obvious trolls) but we do have rules that we want you to follow. One of them is being respectful. This has worked for this forum for years and you're in no position to impose your bad manners on others.

    if it gets anyone to improve an issue is a whole nuther matter and not one I particularly care about either way here it can stay shit its obviously intended to be that way by poor design.

    If you don't care please just leave. There's nothing to be gained from venting off like you do. Philosophical debates about effectiveness of swearing in technical discussions in not really the topic of this forum (unless you want to start a new topic in the Lounge section).


Log in to reply
 

Looks like your connection to Qt Forum was lost, please wait while we try to reconnect.