search

rainwoodman / libyaml-glib

Building GObjects with YAML
10 stars 5 forks source link

Switch build system to Meson #22

Closed arteymix closed 5 years ago

arteymix commented 8 years ago

This is all we need to build the project with Meson.

With the coming 0.36, we'll be able to generate a specific header name (e.g. yaml-glib-1.0/yaml-glib.h).

I had to copy the whole yaml-0.1.vapi to keep autotools working. I'll push more commits for a full switch if it's convincing enough.

rainwoodman commented 8 years ago

Looks neat. What do you mean by the specific header file? It looks like you can put any Python in a meson script?

arteymix commented 8 years ago

It uses a DSL that is specifically not Turing complete to keep build sane and explicit.

Right now, the header name is based on the target (e.g. yaml-glib-1.0.h), but we probably want to have a package directory containing yaml-glib.h instead. I submitted a PR for that in https://github.com/mesonbuild/meson/pull/912.

It adds the vala_header and vala_vapi options to customize the output file names.

albfan commented 5 years ago

opps, just see this, let me review and add here. What are the actual stoppers?

arteymix commented 5 years ago

Back then, we did not have the facilities in Meson to specify development files output and installation destination.

We'll use your PR for now on.