{"id":209,"date":"2011-11-20T01:48:56","date_gmt":"2011-11-20T01:48:56","guid":{"rendered":"http:\/\/www.coralbark.net\/blog\/?p=209"},"modified":"2011-11-20T01:48:56","modified_gmt":"2011-11-20T01:48:56","slug":"problems-with-qt-creator-installed-in-opt","status":"publish","type":"post","link":"https:\/\/www.coralbark.net\/blog\/life\/2011\/11\/problems-with-qt-creator-installed-in-opt\/","title":{"rendered":"Problems with Qt Creator installed in \/opt"},"content":{"rendered":"<p>I&#8217;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.<\/p>\n<ul>\n<li><b>Updating the SDK:<\/b> If you run the SDK as the normal user, the &#8220;Help > Start Updater&#8221; 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.<\/li>\n<li><b>Running the QEMU phone emulator:<\/b> This failed with &#8220;Qemu finished with error: Exit code was 1&#8221;. To fix this, I ran QEMU manually:<br \/>\n<code>\/opt\/QtSDK\/Madde\/bin\/mad remote -r dfl61-harmattan_2.2011.39-5 poweron -fg<\/code><br \/>\nThis showed I needed write access to the qemu disk images. As I&#8217;m the only user on the system*, I gave all users access:<br \/>\n<code>chmod a+w \/opt\/QtSDK\/Madde\/runtimes\/dfl61-harmattan_2.2011.39-5\/arm-qemu-rm680-*<\/code><\/li>\n<\/ul>\n<p>Hope this helps someone stumbling across this via Google<\/p>\n<p>* = Yeah. There was no need to install Qt into \/opt &#8211; it just seemed tidier than putting it in my home directory<\/p>\n","protected":false},"excerpt":{"rendered":"<p>I&#8217;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 [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[1],"tags":[],"_links":{"self":[{"href":"https:\/\/www.coralbark.net\/blog\/wp-json\/wp\/v2\/posts\/209"}],"collection":[{"href":"https:\/\/www.coralbark.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.coralbark.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.coralbark.net\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.coralbark.net\/blog\/wp-json\/wp\/v2\/comments?post=209"}],"version-history":[{"count":11,"href":"https:\/\/www.coralbark.net\/blog\/wp-json\/wp\/v2\/posts\/209\/revisions"}],"predecessor-version":[{"id":220,"href":"https:\/\/www.coralbark.net\/blog\/wp-json\/wp\/v2\/posts\/209\/revisions\/220"}],"wp:attachment":[{"href":"https:\/\/www.coralbark.net\/blog\/wp-json\/wp\/v2\/media?parent=209"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.coralbark.net\/blog\/wp-json\/wp\/v2\/categories?post=209"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.coralbark.net\/blog\/wp-json\/wp\/v2\/tags?post=209"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}