Re: [Geary] geary .012? FAILED: src/engine/geary-engine-internal.vapi

[Holiday <eholiday gmail com>]

`find build -name \*.vapi` returns empty b ut the make works.  I had to
install  gnome-doc-utils for xml2po.

I tried to run with my existing .config/geary files in place but geary
crashed. Once I moved those out of the way, geary ran clean. I will try now
to see if the issues I was having with the build from the debian
repositories have been resolved with this build.

Thank you for your help.


----

On Thu, Apr 26, 2018 at 5:32 PM Michael Gratton <mike vee net> wrote:


> On Fri, Apr 27, 2018 at 3:08 AM, EHoliday <eholiday gmail com> wrote:
> > From github this morning April 26 2018.
> > /bin/cp geary-engine.h geary-engine-internal.h
> > src/engine/geary-engine@sta/geary-engine-internal.vapi src/engine
> > /bin/cp: cannot stat
> > 'src/engine/geary-engine@sta/geary-engine-internal.vapi': No such
> > file or directory

> Does geary-engine-internal.vapi exist anywhere in your build dir? What
> does `find build -name \*.vapi` report?


> > meson build included these questionable messages (excerpted) :
> >
> > [snip]
> > WARNING: GLib compiled dependencies do not work reliably with
> > the current version of GLib. See the following upstream issue:
> > https://bugzilla.gnome.org/show_bug.cgi?id=774368

> This is the only thing that's unexpected, but it shouldn't be causing
> the error above.

> > Something I'm missing or not doing correctly?

> Not from the looks of it. While the version of valac in stable is
> pretty old, it should in theory be supported. But to be honest I
> haven't tried building master there with meson, so there may be some
> bumps to iron out.

> The CMake build still exists in the source tree for the moment
> (although it will go sometime before 0.13), can you try using that and
> see if that succeeds? Try the following:

> rm -rf build && mkdir build
> cd build && cmake .. && make

> //Mike

> --
> ⊨ Michael Gratton, Percept Wrangler.
> ⚙ <http://mjog.vee.net/>