Conversation
|
I don't think it helps: the meson build does not look easier to use/maintain than the rather simple Makefile we have. I also appreciate that the current Makefile makes it clear with what flags we run gcc. In general, I don't think we should maintain configuration for two build systems as it's an unnecessary burden to keep them synchronized. I don't object to switching to another build system altogether, but only if it brings some benefits. |
That's definitely subjective, yes. I would personally take a meson build file almost every day over a
Running
The motivation was that the current I feel that meson provides a more "familiar" interface, while every makefile tends to have its quirks and differences. For example, it provides a Naturally I understand this ultimately comes down to personal preference, so I am awaiting your questions or decision. |
|
I know that I can ask meson to list the commands. But it lists them for the current machine, while I want to understand what is used in general. I prefer to keep using make for the time being. |
|
Okay, I will keep this working for the foreseeable future, but feel free to close the PR. |
I would like to propose adding meson build system support to isolate. Many projects use it, it has a python-like syntax, and in my opinion much easier to grasp than makefiles. It also has a lot of convenience functions related to dependency lookups, etc.
Thoughts? This is not entirely completely, but I have been using this without issues.