Snapping with scons
spencertparkin at gmail.com
Tue Jan 17 07:35:13 UTC 2017
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.
By the way, the documentation at...
...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.
The worst snapcrafter on the list.
On Mon, Jan 16, 2017 at 12:07 AM, Spencer <spencertparkin at gmail.com> wrote:
> Hi. I have a project with 2 dependencies so I need 3 parts in my yaml
> file. The dependencies install correctly during snapping, but when my
> program starts to compile, it can't locate the header files for the library
> dependencies. There is no mystery here as to why that is the case. My
> question, however, is: what do I put in my scons file so that I can locate
> the header files during snapping? I've been looking at the snapcraft
> python code, but I can't seem to find out what, if any, additional
> environment variables there may be setup for me to use in my scons file so
> that I can locate headers and libraries. Is there a different way to go
> about it?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Snapcraft