I’ve been doing a bit of fiddling with using Qt for developing mobile apps. When I installed the Qt SDK I installed it to /opt. This means the user running the IDE does not have write access to the IDE which has caused a number of problems.
- Updating the SDK: If you run the SDK as the normal user, the “Help > Start Updater” menu option still exists and appears to work. It seemed to detect that I had sudo access and asked for my password but then hung using 100% CPU. Instead of using that menu option, I ran /opt/QtSDK/SDKMaintenanceTool as root which works.
- Running the QEMU phone emulator: This failed with “Qemu finished with error: Exit code was 1”. To fix this, I ran QEMU manually:
/opt/QtSDK/Madde/bin/mad remote -r dfl61-harmattan_2.2011.39-5 poweron -fg
This showed I needed write access to the qemu disk images. As I’m the only user on the system*, I gave all users access:
chmod a+w /opt/QtSDK/Madde/runtimes/dfl61-harmattan_2.2011.39-5/arm-qemu-rm680-*
Hope this helps someone stumbling across this via Google
* = Yeah. There was no need to install Qt into /opt – it just seemed tidier than putting it in my home directory