[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

$(TARGET)::$$(@F) vs. $(notdir $(TARGET))

From: Gerrit Bruchhäuser
Subject: $(TARGET)::$$(@F) vs. $(notdir $(TARGET))
Date: Thu, 22 May 2003 09:59:33 +0200
User-agent: Mozilla/5.0 (X11; U; Linux i686; de-AT; rv:1.3) Gecko/20030312

Berkeley 'make' understands '$$(@F)' in a double-colon rule:

        echo "$(INST) $(@D) $(@F)"; \
        $(INST) $(@D) $(@F);

GMake doesn't but offers an equivalent feature:

$(TARGET)::$(notdir $(TARGET))
        echo "$(INST) $(@D) $(@F)"; \
        $(INST) $(@D) $(@F);

but this breaks compatibility with berkeley's make since '$(nodir ...)' is an unknown operation to it.

How can I workaround this problem so that the rule is working with both of the make implementations? Is it eventually possible to teach 'gmake' what '$$(@F)' means in a double-colon context?

- Gerrit

reply via email to

[Prev in Thread] Current Thread [Next in Thread]