On 31/01/2017 18:21, Olivier Tilloy wrote: > This is a bit tricky: when packaging a Qt application that uses the > platform snap, snapcraft will use ldd to crawl the app’s binaries and > will automagically add the libraries that it depends on to the > resulting snap (those libs are taken from the host system). > > There is a way around that, but it’s rather counter-intuitive and > error-prone: add the packages containing those libs to the list of > stage-packages, then explicitly exclude them from the resulting snap > using the prime/snap keyword. You won’t be able to exclude them if you > didn’t include them through the stage packages first.
Actually, I found a simpler solution (not sure if it would work in all cases): just explicitly list the files you need to be primed. https://gitlab.com/mardy/snapcraft-webapp-helper/blob/master/snapcraft.yaml This works for our webapps, which consist only of the webapp-container binary (and therefore are only about 600KB in size). Ciao, Alberto -- Snapcraft mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/snapcraft
