How to do a clean uninstall and reinstall of qt sdk

From Qt Wiki
Jump to: navigation, search
This article may require cleanup to meet the Qt Wiki's quality standards. Reason: Auto-imported from ExpressionEngine.
Please improve this article if you can. Remove the {{cleanup}} tag and add this page to Updated pages list after it's clean.

English Български

How to do a clean uninstall and reinstall of Qt SDK

I successfully reinstalled Qt SDK with the following simple steps:

  1. Start SDKMaintenanceTool
    $ sudo QtSDK/SDKMaintenanceTool.app/Contents/MacOS/SDKMaintenanceTool<code>
    

# '''Remove all components'''   The tool’s dialog window will show up. In the dialog window select '''Remove all components''', continue and uninstall the SDK (on other OS just start the SDKMaintenanceTool).   By comparing the filesystem before and after the uninstall, this uninstallation only removed the QtSDK directory.   When reinstall, make sure to check the box '''remove the old Qt Creator’s setting''' in the installation interface.   == Note on the reinstall issue - bug #QTSDK-834 ==   After uninstalling the previouQt 4.7.3 (or older versions) with the option to '''remove all the previous settings''' and resintalling a new one '''Qt 4.7.4''' some components are not found and some part of the build reports a ''qmake error'' due to the ''mingw-g++'' not found. Note that in most of the other cases mingws is working, as is, in the standard installation folder ../mingw/bin so the application usually runs in the simulator and on the device too.   Focusing the issue - some wrong path and/or folder in the Qt path environment - I have found the reason in the bug '''#QTSDK-834''' ( https://bugreports.qt.nokia.com/browse/QTSDK-834 ) ''Bad configuration of the QtCreator after the QtSDK installation'' .   The workaround requires a hand-made work searching in all the configuration settings from the ''Tools/Option'' menu window for paths (the older installation path) correcting them to the new root folder. After this long job and some tests also the debug libraris are compiled and works.   === Alternate (simple) solution ===  

An alternative solution if you have read this note before the resinstallation :) is to ''install the new version exactly in the same drive and path where were the previous one''.