I have an application that depends on a newer version of a library than is present in the archives, so I can't use stage-packages to pull it in. I have created a new part that will build this library from upstream source, and that part builds without problem. However, the application part that needs it is unable to find it, with pkg-config failing
This is the snapcraft.yaml that reproduced the problem.
https://github.com/ubuntu/snappy-playpen/blob/f58d396bff2503cf942d2afad65adbc4b6575192/pantheon-mail/snapcraft.yaml
Granite 0.4 is the dependency that is needed by Pantheon Mail.
This is the output from snapcraft cleanbuild:
http://paste.ubuntu.com/17662567/
This is the location and content of the granite.pc produced by the dependency part:
http://paste.ubuntu.com/17662693/
I even tried forcing all of the other -dev packages to be installed to the same location, here is the full list of .pc files:
http://paste.ubuntu.com/17665800/
Still pkg-config is unable to find the granite dependency when building the mail part.
Similar situation, but I don't have the technical know-how to understand exactly what number of things are not working correctly in the build-environment.
My snapcraft.yaml:
https:/
This is the snapcraft cleanbuild output (mostly `libtool` and `pkg-config` errors which are relevant):
http://
These are the two .pc files of the libraries which are built, and not being found, along with a list of all .pc files on the build container:
http://