> On May 11, 2019, at 02:33, Xi Ruoyao via blfs-dev > <[email protected]> wrote: > > On 2019-05-11 08:04 +0100, Ken Moffat via blfs-dev wrote: >> On Sat, May 11, 2019 at 11:56:29AM +0800, Xi Ruoyao via blfs-dev wrote: >>> On 2019-05-10 20:28 +0100, Ken Moffat via blfs-dev wrote: >>>> On Fri, May 10, 2019 at 06:35:15PM -0000, xry111--- via blfs-book wrote: >>>>> Author: xry111 >>>>> Date: Fri May 10 11:35:15 2019 >>>>> New Revision: 21576 >>>>> >>>>> Log: >>>>> Use autotools to build c-ares, instead of cmake >>>>> >>>> >>>> Why, please ? >>> >>> Cmake is not listed as c-ares dependency so we should either add it, or use >>> autotools. I decided to remove the extra dependency. >> >> Where there are alternatives, I would prefer to discuss changing the >> build method. In this case, adding a link to cmake seems a lot easier >> than rewriting the instructions. > > Then we'll get > > c-ares depends on cmake (required) > cmake depends on curl (recommended) > curl depends on c-ares (optional) > > I think we should always use autotools/make or meson/ninja if one of them are > avaliable, rather than cmake. Autotools/make and meson/ninja are avaliable on > a > fresh LFS system. But to use cmake we have to install 4 packages: libuv, curl, > libarchive, cmake. >
Greetings, Is it possible that someone will go directly to netlibs and filter back to a previous package? How about if they want a program that isn't in BLFS that needs cmake and the deps. I don't understand the idea that cmake isn't needed. Seems like it should be as a recommended or optional dep when going thru BLFS. Name a distro that doesn't have cmake. Sincerely, William Harrington -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
