They grow up so quickly...

@talkless please clean the build dir when switching between versions.

@rondarius that is so cool!

@talkless the latest version of Pure Maps is UT 20.04 only. If you run 16.04, you can go back to Pure Maps 3.1.1 which is still made for 16.04.

@talkless you might need to build clean once, looks like an outdated build cache.

@chester could you please paste the exact error message you are referring to? Btw, if you struggle pushing the SSH key via ADB, you can use other means like MTP or sharing it via a messenger.

OSM Scout Server 3.0.0 is on its way to the Open Store, still waiting for manual review, because it is unconfined. After updating to version 3.0.0 it is required to restart the system once and let the app update its maps. The apps have already been made available for download as the app update was rolled out on other platforms yesterday.

To my understanding, the old version of the app should not have downloaded the new maps. Apparently it did. Sorry for the inconvenience.

The problem is make: 'install' is up to date. when this isn't true. You can avoid it by always building picotts clean. Or by touching the binary as in https://github.com/rinigus/pure-maps/pull/646. Just be aware that the master branch of Pure Maps is already configured to build for UT 20.04.

What is also missing is updating the app armor policy to 20.04 and renaming the X-Ubuntu keys in the desktop file to X-Lomiri.

@kugiigi Clickable does not consider the manifest when deciding to use a xenial/focal docker image. It considers the framework in the project config or the env var. Otherwise it uses its default, which still is xenial. For a QML only app (after testing it really works in focal), one could keep the 16.04 framework for now and just upload the same click for focal.

Note that clickable log and clickable logs use journalctl for focal (if the framework is specified as focal).

The instructions above should be updated with what you suggest.

@remark I would suggest to use the CLICKABLE_FRAMEWORK env var only when building for xenial and focal from the exact same code base, using the QML compat layer. As the instructions suggest to replace Ubuntu imports by Lomiri, I'd rather suggest to set framework: ubuntu-sdk-20.04 in the clickable.yaml.

@talkless Can you try building it again with verbose output (clickable build --libs picotts --arch arm64 --verbose)?

@talkless looks like it is correct. How does tree build/aarch64-linux-gnu/picotts/install look like?

Are you sure you have picotts built? It makes sense for it to be in the full build, because it offers more languages than mimic.

I just found another bug in the latest version of Clickable related to installing QML modules. Until it is released, you find the fix here: https://gitlab.com/clickable/clickable/-/merge_requests/553

@talkless You can run the gdbserver command with --verbose to see the command line parameters. I suspected the --desktop_file_hint which is necessary for the display server. Adding that one as an allowed parameter to the parser doesn't help though. So no idea, to be honest.

Commenting out the CmdLineParser lines allows you to debug Pure Maps btw.

@talkless Could you please try to add libc6-dbg to the dependencies_target before running the gdb command?

You can set a break point at main and step through it. This way you will find that it exits because the parser fails to parse command line arguments. it returns at line 112:

109	  // command line
110	  CmdLineParser *parser = CmdLineParser::instance();
111	  if (!parser->parse(app->arguments()))
112	    return 0;

All I can say so far is that I can reproduce the issue with Pure Maps, but not with the CMake app template from Clickable.

@talkless the host OS doesn't play a role. You can use any Linux distro that supports docker and python and even Mac and WSL have some limited support.

As build and release builds are not separate, clickable install will just install whatever has been built before, may it be a debug build or not.

I just stumbled upon this line:

bind [127.0.0.1]:3333: Address already in use

Are you using that port for something already? Could you try to choose another one (on both, gdb and gdbserver)?