Re: Switching from Autotools to CMake for core evolution products
On Wed, 2016-10-05 at 17:29 +0100, Javier Jardón wrote: > Sure, just ping me (jjardon) or any of the release team members > Hi, thanks a lot, I'll do that once the changes will be merged in the git master. Bye, Milan ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Switching from Autotools to CMake for core evolution products
Hi, On Wed, 2016-10-05 at 19:13 +0530, Nirbheek Chauhan wrote: > Meson supports Ninja, MSVC 2010, MSVC 2015, and XCode. Support for > make was omitted on purpose. Ah, nice, I misread the list of available backends. My fault. I'm sorry for that. Bye, Milan ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Switching from Autotools to CMake for core evolution products
On 5 October 2016 at 14:25, Milan Crhawrote: > On Wed, 2016-10-05 at 07:54 -0500, Michael Catanzaro wrote: >> This is fine from a release team perspective, as we're already set up >> to handle CMake modules. Just make sure to update the JHbuild >> moduselets and Continuous manifest at the same time you make the >> change. There are already examples of how to handle CMake projects >> (e.g. WebKitGTK+). >> > Hi, > I never touched any of the two, neither I use any of the two, thus it's > pretty likely I'd more break than fix. Would there be anyone willing to > do it properly on the first shot "for me", please? Sure, just ping me (jjardon) or any of the release team members Cheers, Javier Jardón ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Switching from Autotools to CMake for core evolution products
2016-10-05 14:54 GMT+02:00 Michael Catanzaro: > I'm a little surprised at the use of CMake instead of meson, but that's > your choice to make. As much as I hate autotools and its arcane syntax, it does bring uniformity and consistency. Atm I'm counting waf (for some non-core modules), autotools, cmake and some are discussing to use meson/ninja. So while I'm not tied to autotools, I would hate to see if every modules maintainer chooses his/her own build system of choice. This makes it really cumbersome as downstream/integrator. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Switching from Autotools to CMake for core evolution products
On Wed, 2016-10-05 at 07:54 -0500, Michael Catanzaro wrote: > This is fine from a release team perspective, as we're already set up > to handle CMake modules. Just make sure to update the JHbuild > moduselets and Continuous manifest at the same time you make the > change. There are already examples of how to handle CMake projects > (e.g. WebKitGTK+). > Hi, I never touched any of the two, neither I use any of the two, thus it's pretty likely I'd more break than fix. Would there be anyone willing to do it properly on the first shot "for me", please? Bye, Milan ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Switching from Autotools to CMake for core evolution products
On Wed, 2016-10-05 at 13:39 +0200, Bastien Nocera wrote: > Why? Is it faster, smaller, or better in other ways? Hi, seems to be better than autotools, gives more freedom and easily allows the sources to be built much faster than with autotools (it builds here in ~1/3 of the time which uses autotools, still using "Unix Makefiles"). I know it's caused mostly by not having one giant Makefile.am, but this way it's easier (at least for me). With the "gives more freedom" I think of different generators, which CMake offers quite many [1]. > Were other alternatives considered (Meson,seems to be the preferred > non-autotools build system for GNOME projects)? Right, Meson. I do not want to dive into such discussion, Meson simply didn't fit my needs and preferences. Its syntax is weird to me and if you compare what Meson offers (ninja and msvc2010) and what CMake offers [1], then it's just "more freedom" from CMake than from Meson. Bye, Milan [1] https://cmake.org/cmake/help/v3.6/manual/cmake-generators.7.html Note it's for version 3.6, while the required CMake version is 3.0 ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Switching from Autotools to CMake for core evolution products
On Wed, 2016-10-05 at 09:33 +0200, Milan Crha wrote: > Hello, > this is a heads up that the evolution-data-server, evolution, > evolution-ews and evolution-mapi products will switch from Autotools > to > CMake for the 3.23.1 release. The email doesn't explain the most important part though. Why? Is it faster, smaller, or better in other ways? Were other alternatives considered (Meson,seems to be the preferred non-autotools build system for GNOME projects)? Cheers ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list