From nobody Wed Sep 08 23:04:46 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id C79D517C2EFD for ; Wed, 8 Sep 2021 23:04:57 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from www121.sakura.ne.jp (www121.sakura.ne.jp [153.125.133.21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4H4d543sV9z3JsG for ; Wed, 8 Sep 2021 23:04:56 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from kalamity.joker.local (123-48-130-181.area1b.commufa.jp [123.48.130.181]) (authenticated bits=0) by www121.sakura.ne.jp (8.16.1/8.16.1/[SAKURA-WEB]/20201212) with ESMTPA id 188N4krh031495 for ; Thu, 9 Sep 2021 08:04:47 +0900 (JST) (envelope-from junchoon@dec.sakura.ne.jp) Date: Thu, 9 Sep 2021 08:04:46 +0900 From: Tomoaki AOKI To: freebsd-current@freebsd.org Subject: Re: -CURRENT compilation time Message-Id: <20210909080446.d223e9e16b90b5600f962757@dec.sakura.ne.jp> In-Reply-To: References: <2cfb912a-618b-9f06-9cef-d2fe1d78fe97@FreeBSD.org> <20210908105236.1abb8f9a@ernst.home> <746cf2d1-0192-a55d-c3f8-ac7fc7120b47@FreeBSD.org> Reply-To: junchoon@dec.sakura.ne.jp Organization: Junchoon corps X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; amd64-portbld-freebsd13.0) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4H4d543sV9z3JsG X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of junchoon@dec.sakura.ne.jp has no SPF policy when checking 153.125.133.21) smtp.mailfrom=junchoon@dec.sakura.ne.jp X-Spamd-Result: default: False [-1.35 / 15.00]; HAS_REPLYTO(0.00)[junchoon@dec.sakura.ne.jp]; RCVD_VIA_SMTP_AUTH(0.00)[]; MV_CASE(0.50)[]; REPLYTO_ADDR_EQ_FROM(0.00)[]; TO_DN_NONE(0.00)[]; HAS_ORG_HEADER(0.00)[]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; R_DKIM_NA(0.00)[]; ASN(0.00)[asn:7684, ipnet:153.125.128.0/18, country:JP]; MIME_TRACE(0.00)[0:+]; MID_RHS_MATCH_FROM(0.00)[]; RECEIVED_SPAMHAUS_PBL(0.00)[123.48.130.181:received]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.81)[-0.814]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-0.93)[-0.932]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; AUTH_NA(1.00)[]; RCPT_COUNT_ONE(0.00)[1]; DMARC_NA(0.00)[sakura.ne.jp]; R_SPF_NA(0.00)[no SPF record]; RCVD_COUNT_TWO(0.00)[2] X-ThisMailContainsUnwantedMimeParts: N On Wed, 8 Sep 2021 14:32:16 -0600 Warner Losh wrote: > On Wed, Sep 8, 2021, 6:33 AM David Chisnall wrote: > > > On 08/09/2021 11:52, Gary Jennejohn wrote: > > > Seems to me that there was an earlier mail about getting CMAKE to work > > > with FreeBSD builds. Could be worthwhile to look into getting ninja > > > to work also. But I could understand that there might be push-back, > > > since the project prefers to use utilities from the source tree. > > > > CMake is a build-system generator, Ninja is a build system. Usually the > > two are used together: CMake generates Ninja files, Ninja runs the > > build. Ninja is explicitly designed not to be written by hand. > > > > CMake can also emit other things, including POSIX Makefiles, but the > > Ninja build is usually the fastest. > > > > CMake and Ninja are both in package systems for Windows, macOS, *BSD, > > and all Linux distros that I've seen, unlike bmake, so universally easy > > to depend on for cross-builds. Cross compiling with bmake is much > > harder harder from anything that isn't FreeBSD. > > > > This may be true. I've never had a problem on mac or linux, but my windows > experience is thin. > > I got looking at the problem, btw, to see if ninja was faster than meta > mode. Ninja files aren't horrible to generate, but I never got past the > early proof of concept phase... it seemed possible to implement a make > ninja target... I'd wanted to use this day to day if it was better than > meta. > > Mason, however looked much harder to generate, but I didn't spend a lot of > time on it. I would think this sort of work would be more of a one shot. > Didn't look at cmake at all, but I imagine it would be similar... > > Warner > > > What about devel/samurai, ninja-compatible build tool written in C? devel/ninja/Makefile has USES= python in it, so it maybe require python to run or at least build. In addition, ports framework can use it instead of ninja. See {PORTSDIR}/Mk/Uses/ninja.mk. -- Tomoaki AOKI