Date: Sat, 15 Oct 2016 01:43:52 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 213446] Configurable verbose build output Message-ID: <bug-213446-13-d6Izm8IXjT@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-213446-13@https.bugs.freebsd.org/bugzilla/> References: <bug-213446-13@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213446 --- Comment #14 from lightside <lightside@gmx.com> --- (In reply to comment #5) > Any build that chains make/gmake supports > $ make -s I may confirm, that this works for multimedia/assimp. (In reply to comment #5) > ninja/waf may need a hack e.g., >=20 > -MAKE_ARGS+=3D -v > +MAKE_ARGS+=3D ${ECHO:Ntrue:S/echo/-v/} but not for ports-mgmt/pkg and devel/llvm39, for example. And what I proposed is not a hacks, which solve the consequences, but solution(s) to solve a causes of it, i.e. concrete build flags used to enab= le verbose build output, instead of less verbose. Possible to encapsulate other MAKE_ARGS+=3DV=3D1 or MAKE_ENV+=3DV=3D1 cases= , used in some ports, to some Mk/Uses file (verbose.mk? USES+=3Dverbose; USES+=3Dverbose:env). This way, verbose build output may be isolated to Mk directory and there may be no need to use ".ifndef NO_VERBOSE_BUILD" check = for actual ports, but some Mk/Uses file. --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-213446-13-d6Izm8IXjT>