@Bokkenn said in Clickable: C++ template does not work on Focal (20.04): I forgot to specify the architecture. Needless to say, adding --arch arm64 to the command fixed the problem. Sorry for taking your time for such a trivial issue. Glad you got it sorted, although it is odd, as since a few versions --arch arm64 has been the default for clickable. Very odd indeed. Do you have setup somewhere in some configuration that amd64 should be the default on your development machine? I believe it would be good to have some mechanism in place to warn me if I attempt to install a .click with the wrong architecture. It only said "failed to install" from the command line, and installing manually though the phone only gave an "incorrect package format" from the OpenStore. Well, the 'failed to install' bit on the command line and especially the 'incorrect package format' that the OpenStore throws are the mechanisms I guess. Now looking back at your original post, I see that the answer was staring us right in the face, in the name of the click: /home/phablet/appname.yourname_1.0.0_amd64.click. I guess now we know.

@wendor The issue was that clickable still defaults to ubuntu-sdk-framework-16.04, while your device is running 20.04. That was causing the error messages you were seeing.

Although, thinking about it, I am not sure if our API key can handle the additional load of data calls. We might need to implement an option for users of snap/appimages to use their own API codes. This should be solvable, but should be considered.

@povoq oh, I am sorry, I was trying to start developing with QML and python and thought clickable should be on the phone.

@applee There is this - https://github.com/ubports/utqemu. Didn't work for me on Ubuntu 18.04 though.

@doniks its just a .img file contained in a .gz just extract the .gz file and flash the resulting image onto a USB drive (or a harddrive depending on if you'd wanna install it as main os)

@tusharsaurabh Really? Strange, I still get the same error? where did you change the architecture field? In the manifest.json.in file?

@MarkG_108 you created the app correctly. After the talk clickable got updated and that template got better feedback. So: congratulations!

for reference : https://forums.ubports.com/topic/2178/c-and-sdl-with-clickable-a-little-help-please/19

Hi, for the people using "atom-clickable plugin" with clickable 5.0.0 the command "Clickable: Build and run [desktop]" from Atom doesn't work because it uses the old '- - desktop' option replaced by 'desktop'. To fix quickly this: open with an editor the file (enable 'show hidden files' to see 'atom' folder): <your-home-folder>/.atom/packages/atom-build-clickable/lib/clickable.json and remove the '- -' at line 114 after that should like this: args: [ 'desktop' ], Restart Atom to update the plugin. I have just made a Pull request at the author of "atom-clickable plugin" to include that fix, and to include the new '- - vivid' option (added with clickable 5.0.0) Tnx

@hummlbach said in How to Import Python library to clickable?: The question about Python Library is SOLVED, with apt-get install on get_libs.py maybe I need to open new thread, about "How to check Crash Log in Ubuntu Touch?" OR "Create VoIP application with PJSIP in Ubuntu Touch" the Strace log didn't show me exactly what make the system reboot. this show me the technique to see what happen before system crashed since I'm using SSH to my phone, I follow the SSH step Log into phone using clickable shell Open another tab. Run clickable shell in tab 2 run tail -f /var/log/syslog to see system log in realtime Reproduce the crash in tab 1 Watch any error messages in the tab 2 Now I need to move to another thread to discuss it, and close this Thread as Solved

@Emanuele-Sorce, finally I was able to actually reproduce all the required steps to setup build environment once again, so slightly updated guide is now on wiki