Date: Fri, 15 Mar 2024 08:27:31 +0900 From: Tatsuki Makino <tatsuki_makino@hotmail.com> To: Miroslav Lachman <000.fbsd@quip.cz>, "freebsd-ports@FreeBSD.org" <freebsd-ports@freebsd.org> Subject: Re: how to see order of make targets steps in ports tree? Message-ID: <SI2PR01MB503686DCF5200BB327162128FA292@SI2PR01MB5036.apcprd01.prod.exchangelabs.com> In-Reply-To: <df9dcc91-699b-41ff-8957-65df58607e30@quip.cz> References: <610f900f-658f-474d-885a-abbe709a00f7@quip.cz> <SI2PR01MB503607D1E9AC65A888CB2892FA292@SI2PR01MB5036.apcprd01.prod.exchangelabs.com> <df9dcc91-699b-41ff-8957-65df58607e30@quip.cz>
next in thread | previous in thread | raw e-mail | index | archive | help
Miroslav Lachman wrote on 2024/03/15 07:24:
> 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}
Regarding this, the use of :U out of the blue without a variable name doesn't make sense to me :)
Does this mean that this is how the value is handled internally when expanded by .for?
Because the following command is valid
make -C /tmp -V :Usomevalue
I see that the order of execution is determined by specifying the sorted target name in .ORDER target source.
After sorting in numerical order with the left side filled with zeros, the numbers and splitters are shaved off.
Regards.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?SI2PR01MB503686DCF5200BB327162128FA292>