Hi Britton,
As it is it easily creates a bunch of circular dependencies that require the user to manually specify target-local .EXTRA_PREREQS for a bunch of targets to avoid.
please bear in mind that .EXTRA_PREREQS where initially "invented" to be used as target-specific variable: Consider the use-case given in the related section of the manual. Its natural extension as a global variable may not be of much use.
Maybe a reasonable solution is obvious to somebody?
I think the very first step for a decent solution of that issue would be to come up with a compelling use-case for global .EXTRA_PREREQS. Having such a use-case would set the base to discuss measures to make this use-case more usable. Without such a use-case, the best I could thing of up until now would simply be to surpress the related warning. Hope this helps, Chris
