Important: Please read the Qt Code of Conduct -

Re-install Qt Creator and save kits, settings, etc.

  • Hello,
    I used the maintenance tool to update creator on my VM. During update I received an error that my VM needed more disk space. I expanded the disk space and tried again. After it completed Qt Creator wouldn't even launch. Found the fix in the forums and updated (sudo apt-get install libxcb-xinerama0) and it now launches. However, code that used to compile is giving me errors and I feel like I'm chasing my tail.
    I would like to re-install Qt Creator, but as a new user I am afraid I will lose the kits I have enabled for embedded targets. And other settings I don't know I need. Is there a way to do so and safely keep my "settings" ?

    Thank you,

  • Lifetime Qt Champion

    @AndreiS said in Re-install Qt Creator and save kits, settings, etc.:

    is giving me errors

    What errors?
    Did you also install Qt?

    On Linux QtCreator stores its configuration in HOME/.config/QtProject/
    But it is not enough, you also have to install all needed parts (like compiler and Qt).

  • @jsulm
    Hi, thanks,
    All sorts of strange errors. I'll mention two:

    m_modBusRTUInterface = new ModBus(this);

    Gives me this error:
    interfacemanager.cpp:33:28: error: incompatible pointer types assigning to 'ModBusInterface *' from 'ModBus *'


    Q_LOGGING_CATEGORY(hmiDeviceLog, "reelex.hmiDevice")

    Gives me this error:
    hmidevicelog.cpp:3:1: error: variable has incomplete type 'const QLoggingCategory'
    qloggingcategory.h:119:39: note: expanded from macro 'Q_LOGGING_CATEGORY'
    qlogging.h:84:7: note: forward declaration of 'QLoggingCategory'

    This is all stuff that was compiling before the update.

    I'm embarrassed to say I didn't pay attention to what was being updated and just let the maintenance tool do its thing. Looks like Creator was updated from 4.9 to 4.13 and Qt remained at 5.12.3. That a problem? Thank you.

  • Lifetime Qt Champion

    @AndreiS Do a complete rebuild: delete build folder, run qmake and build If you again get errors post the very first one.

  • @jsulm Ok, did as you asked. Lots of new errors highlighted red in the editor and so I assume it didn't build. Close all open files because I had many open. Do it again and it seems to have built with only several warnings and an exe file present in buildFolder\deploy\usr\bin with the proper timestamp. What the...

    This is an example, but editor is suggesting many, many red semantic issues. Almost like there was an issue parsing the files.
    alt text

    Any further suggestions are greatly appreciated.

  • @AndreiS Qt example code has the same behavior... Errors in the editor, but it builds.

  • Lifetime Qt Champion

    @AndreiS said in Re-install Qt Creator and save kits, settings, etc.:

    Lots of new errors highlighted red in the editor and so I assume it didn't build

    This comes from the Clang code model. Important is whether it builds.

  • @jsulm Thank you for the help! Can you think of a way to fix that (Clang code model) without reinstalling the whole environment? Again, thank you for taking the time.

  • Lifetime Qt Champion

    @AndreiS Quick and dirty solution is to disable Clang code model plug-in.
    In general the code model often generates false warnings/errors for various reasons.

  • @jsulm That totally got rid of the "false" issues and everything looks like it did prior to the upgrade. Thank you! I read a bit about the "old code model" versus the clang code model and it appears to me that the clang is optional. I'll work like this, I guess, until I hear otherwise. Unless restoring the clang plugin is straightforward. Much appreciated.

Log in to reply