On Tue, Jan 31, 2017 at 4:56 PM, Leo Arias <leo.ar...@canonical.com> wrote: > On Tue, Jan 31, 2017 at 9:21 AM, Olivier Tilloy > <olivier.til...@canonical.com> 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. > > Isn't this what Kyle fixed by adding build-attributes: [no-system-libraries] ? > > http://snapcraft.io/docs/build-snaps/syntax#parts
Yes, that seems to be it, indeed. Thanks for the pointer Leo, I wasn’t aware of this new feature. With this, no need to artificially add stage packages. Neat! -- Snapcraft mailing list Snapcraft@lists.snapcraft.io Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/snapcraft
