Moving efl to meson,
feature branch : feature/meson
Moving efl to meson,
feature branch : feature/meson
I'm redoing some of the evas module stuff to have somewhat better option naming as well as matching the existing default enable states.
There's a number of places where .so is hardcoded as a shared library/module extension. Is that accurate for all platforms?
I propose the following:
This should provide a more workable system for managing individual patches and determining what is going on in each branch/commit.
We can do that.
Any commit, not related to meson, should land in master before that anyways. Which is the case for D6795.
I would prefer to get the meson work into master as soon as its running on linux, across distributions.
I agree, though I think it should only be merged once it is complete (i.e., all parts of tree are building and running).