Ticket #3946 (closed task: wontfix)
Switching on meson build system
| Reported by: | vit1251 | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | |
| Component: | mc-core | Version: | master |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | ||
| Branch state: | no branch | Votes for changeset: |
Description
Right now modern build system meson increase support project count and I want ask you about do u want to continue support bash hell scenarios or may be you consider ability to switch on meson?
I can assist you with migration.
How do you look at such a proposal?
Change History
comment:1 Changed 6 years ago by andrew_b
- Status changed from new to closed
- Resolution set to wontfix
comment:2 Changed 6 years ago by ossi
a reason would be "less ugly, thus easier to maintain".
that isn't a particularly relevant consideration when the build system is stagnant anyway, as the investment isn't likely to pay off any time soon.
another reason would be quicker builds, or quicker and/or more reliable re-builds. depends on how well the current system performs.
comment:3 Changed 6 years ago by vit1251
meson build system keywords are simple to be understood and eazy to new members (low entry barier). the second idea is to speed up the build and re-build process (increase recompile).
but my initiative bases on simplicity to understanding of build keys and dependencies, which of course is not so easy for autotools.
I would like to exclude / include some features in custom mc assembly, which now takes time to research in autotools scripts and add/remove some abilities
Apparently no.
I can't see any reason for that.