Date: Thu, 14 Mar 2024 23:24:27 +0100 From: Miroslav Lachman <000.fbsd@quip.cz> To: ports@freebsd.org Subject: Re: how to see order of make targets steps in ports tree? Message-ID: <df9dcc91-699b-41ff-8957-65df58607e30@quip.cz> In-Reply-To: <SI2PR01MB503607D1E9AC65A888CB2892FA292@SI2PR01MB5036.apcprd01.prod.exchangelabs.com> References: <610f900f-658f-474d-885a-abbe709a00f7@quip.cz> <SI2PR01MB503607D1E9AC65A888CB2892FA292@SI2PR01MB5036.apcprd01.prod.exchangelabs.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 14/03/2024 22:03, Tatsuki Makino wrote:
> Hello.
>
> Various answers have already been given, however, here is a command that can produce interesting values on this.
>
> make -C /usr/ports/ports-mgmt/pkg -V _TARGETS_STAGES
> make -C /usr/ports/ports-mgmt/pkg -V _SANITY_SEQ -V _PKG_SEQ -V _FETCH_SEQ -V _EXTRACT_SEQ -V OMITTED_HEREAFTER:P
>
> The -d option of make also displays some rather interesting things.
>
> make -C /usr/ports/ports-mgmt/pkg -n -d g1
>
> In addition, variables such as _USES_target can be used to add interesting behavior.
> For example, in the patch phase, rewriting by replace_cmd may be performed in addition to normal patching.
> It makes make makepatch not smart to use.
> It can be stopped by defining the following targets. ...I think I wrote that somewhere before :)
>
> _USES_patch+= 501:stop-patch
> stop-patch: .NOTMAIN .PHONY
> false
>
> I just don't know if it helps :)
Thank you. I find these commands useful. Really interesting output.
And this line should explain the order of patch and fix-shebang
_PATCH_REAL_SEQ = ${:Uask-license} ${:Upatch-message}
${:Upatch-depends} ${:Ufix-shebang} ${:Udo-patch}
Thanks again.
Kind regards
Miroslav Lachman
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?df9dcc91-699b-41ff-8957-65df58607e30>