%% Mike Shal <[EMAIL PROTECTED]> writes:
>> No fundamentally better way. You can be a bit more restrictive of what
>> you match on by using filter/filter-out for pattern matching instead of
>> findstring, but that's about it.
ms> One other possible solution is to remove the rule to gener
Mike Shal wrote:
> Unfortunately, what gcc actually does with the .d file (as in, which
> directory it gets stored, what it lists as the target, etc) has
> changed somewhat drastically between gcc versions (IIRC, between 3.0
> -> 3.3 is pretty wacky). So if you know what gcc version you're
> build
On 11/11/05, Paul D. Smith <[EMAIL PROTECTED]> wrote:
> %% "Marty Leisner" <[EMAIL PROTECTED]> writes:
>
> ml> ifneq (,$(findstring clean,$(MAKECMDGOALS)))
> ml> NO_DEPENDS=1
> ml> endif
>
> ml> ifndef NO_DEPENDS
> ml> -include $(DEPS)
> ml> endif
>
> ml> I've seen this annoying behav
%% "Marty Leisner" <[EMAIL PROTECTED]> writes:
ml> ifneq (,$(findstring clean,$(MAKECMDGOALS)))
ml> NO_DEPENDS=1
ml> endif
ml> ifndef NO_DEPENDS
ml> -include $(DEPS)
ml> endif
ml> I've seen this annoying behavior for years...is there a better
ml> wah t handle this?
No fundamenta
