Yes. It is indeed doing the trick. Probably better yet, I should add a "vapidir" variable to the *.pc file of my Vala libraries and use it in dependent projects. That is, in configure.ac: PKG_CHECK_VAR([LIBX_VAPIDIR], [mylib-x], [vapidir]) and in VALAFLAGS of Makefile.am: --vapidir $(LIBX_VAPIDIR)
On Thu, Feb 2, 2017 at 6:52 PM, Luca Dionisi <[email protected]> wrote: > On Thu, Feb 2, 2017 at 4:55 PM, Sergio Schvezov > <[email protected]> wrote: >> Does your configure have something like >> >> ./configure --with-extra-vapi-dir >> >> ? >> >> If so, try doing >> >> parts: >> my-part: >> source: ... >> plugin: autotools >> configflags: >> - --with-extra-vapi-dir=$SNAPCRAFT_STAGE/usr/share/vala/vapi >> > > No it doesn't. > > I was thinking to try adding this in configure.ac of mylib-y: > PKG_CHECK_VAR([LIBX_PREFIX], [mylib-x], [prefix]) > > Then adding this in Makefile.am of mylib-y to mylib_y_VALAFLAGS: > --vapidir $(LIBX_PREFIX)/share/vala/vapi > > Then my guess is that snapcraft will find its way without the aid of > particular configflags. -- Snapcraft mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/snapcraft
