<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8"> <META NAME="GENERATOR" CONTENT="GtkHTML/4.8.5"> </HEAD> <BODY> On Tue, 2015-10-13 at 14:33 -0400, Darren Landoll wrote: <BLOCKQUOTE TYPE=CITE> <BLOCKQUOTE> So I'm assuming the Mir related things will be picked up on the mir-devel list, but just to cover some "fun" Qt and QML stuff. Basically you need a large number of environment variables. You can see the list in the QML Snapcraft plugin: <A HREF="http://bazaar.launchpad.net/~snappy-dev/snapcraft/core/view/head:/snapcraft/plugins/qml.py#L78">http://bazaar.launchpad.net/~snappy-dev/snapcraft/core/view/head:/snapcraft/plugins/qml.py#L78</A> What I'd recommend is actually using that plugin to build your snap, instead of using deb2snap, so then you'll get all of those environment variables for "free". There is an example of doing this in the snapcraft codebase here: <A HREF="http://bazaar.launchpad.net/~snappy-dev/snapcraft/core/view/head:/examples/qmldemo/snapcraft.yaml">http://bazaar.launchpad.net/~snappy-dev/snapcraft/core/view/head:/examples/qmldemo/snapcraft.yaml</A> Then you can just setup copy for your QML files. We also have CMake and other Snapcraft plugins depending on how your build works. </BLOCKQUOTE> </BLOCKQUOTE> <BLOCKQUOTE TYPE=CITE> Thanks for the info, I will definitely look at switching to snapcraft. Do you know if that would provide any benefits/fixes for the mir server snap also? </BLOCKQUOTE> Changing your app won't help Mir, but I have been talking with the Mir folks about switching their snap over to being built with Snapcraft as well. Hopefully that should clean it up a bit. Ted </BODY> </HTML>