On Tue, 17 Jan 2017 00:35:13 -0700, Spencer Parkin wrote: > Okay, maybe no one knew what I was taking about. In any case, for the > record, I've resolved the issue by using relative paths in my SConstruct > file that would only work during snapping. This doesn't cause an issue > with normal development, because I also include relative paths (include > paths and lib paths) that would only work in that context. Extraneous > paths in either context is fine. > > What I figured is that, like the "DESTDIR" variable provided by the scons > plugin, there would be similar environment variables setup that SConstruct > and other make-type files could use to be able to locate dependency parts > that have already been built during the snapping process. But maybe my > solution is above reasonable? It doesn't seem all that clean to me.
There are, I'll make those more discoverable. > By the way, the documentation at... > > http://snapcraft.io/docs/reference/plugins/scons Recommendations in the form of a bug on what you are missing would be a nice way to get the documentation improved. https://bugs.launchpad.net/snapcraft/+filebug > ...is pretty bad. If someone pointed me in the right direction, I could at > least add what I know from looking at the plugin's Python code. Hop on to https://rocket.ubuntu.com/channel/snapcraft and we can go over your issues in more details. -- Sent using Dekko from my Ubuntu device -- Snapcraft mailing list Snapcraft@lists.snapcraft.io Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/snapcraft
