That’s important information, it explains why I can’t see ‘/app’. I had noticed that when I built it locally there was a directory for the Flatpak, but when installed from Flathub only a couple of bits and pieces. I stopped worrying about that because there were more important problems to deal with…
The example command is unknown and I can’t see a likely command with ‘flatpak --help’. It would be very useful to be able to see exactly how things are set up.
The OS obviously needs to find the desktop file outside the container to be able to start it, and it does, it shows on the menu with its correct icon. Presumably installing Flatpak informs the OS where to find it. It’s in:
So it is odd that Plank does not find it, I have found a similar situation with other applications.
No, but the Meson variables seem to mostly do the right thing as the application works.
meson_version: '>= 0.46.0'
bindir = get_option('bindir')
datadir = get_option('datadir')
pkgdatadir = join_paths(get_option('prefix'), get_option('datadir'), 'myapp')
conf = configuration_data()
data_files = [
foreach file : data_files
install_data(file, install_dir: pkgdatadir)
install_dir: join_paths(datadir, 'applications')
'myapp.png', rename : 'com.github.mysoftware.myapp.png',
install_dir: join_paths(datadir, 'icons', 'hicolor', '128x128', 'apps')
'myapp64x64.png', rename : 'com.github.mysoftware.myapp.png',
install_dir: join_paths(datadir, 'icons', 'hicolor', '64x64', 'apps')
install_dir: join_paths(datadir, 'metainfo')