On Mon, 19 Mar 2018 18:38:42 +0100 Marcel Hollerbach <m...@bu5hm4n.de> wrote:
> If you find anything that breaks your meson build script, notify the > meson devs, they will fix things super fast, happened to me once for > external projects, and it was fixed within the next release. Same for > other issues. That also means you may always need the latest version of meson for some feature or another. Making that a requirement for all building EFL. You may have issues using latest version preventing such. https://github.com/Obsidian-StudiosInc/entrance/commit/db098127cdedd06a0f359859ccbe5a5df03368f3 Then you get to spend more time fixing things for your nifty build system. I have NEVER had any installation or pre-build issues with cmake. No time spent in setting up cmake for CI, etc. I never had to require a version of cmake, or avoid any. > And btw. after working with meson accross 3 different OSs and > multiple linux distros, i can tell you that using pip to install > things is making life soooo much easier :). I am not a fan of python, and that is providing python is installed etc. You can run into other issues with pip and dependencies... All failures in last week due to python pip issues... https://travis-ci.org/Obsidian-StudiosInc/os-xtoo/builds https://github.com/travis-ci/travis-ci/issues/9349 https://github.com/mrueg/repoman-travis/issues/29 > > There is already a base cmake build system for EFL. Meson would be > > starting from scratch entirely. The speed of meson comes from ninja. > > You can use Ninja with CMake. Which CMake + Ninja is just as fast as > > Meson + Ninja. Likely spend considerable time with making a meson > > build system for EFL. More than fixing cmake IMHO. > > > > There is meson in a feature branch (currently a bit outdated, sorry > for that) that state is much further than cmake, you can build up to > evas i think. Looking at a branch that i need to fix for iOS will > even bring elementary. Mostly looking to make optional support for elogind over systemd, to any EFL build system. > Comparing the bare speed of meson and cmake is > not very usefull, as most of the time will be spent in ninja. > However, meson takes ~2 min. for configuring complete EFL, cmake > (from old numbers about 2 years ago when i did the cmake stuff) ~4 > min. without evas (which is giant). > > > There is a module that generates rpm files for meson projects, i > think contributing deb and pkg to it will not be anything that will > be rejected IMO Only spec files, not a binary http://mesonbuild.com/RPM-module.html#rpm-module I recall in IRC the main author wanted to avoid such and recommended external spec and other stuff to generate rpm and deb. They did not want to bloat meson or make it like cmake, etc. Wanted to keep it simple, along with the meson concepts. Thus some contributions like that maybe rejected. -- William L. Thomson Jr.
pgprIXGnKMSnq.pgp
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
