Harish,

Maple is not simply a PIN tool. It contains several other components (e.g.
cmdline tools). The Makefile is responsible for compiling them too.
Therefore, I don't see a strong reason we should stick with the PIN
protocol.

Can you modify pin.mk instead? (Basically the same stuff you have done in
makefile).

Regarding PIN_ROOT, i think you can just do
PIN_ROOT := PIN_HOME

Let me know if this does not work.

- Jie


On Mon, Nov 25, 2013 at 4:16 AM, hgpatil <notifications@github.com> wrote:

> In makefile:
>
> > @@ -0,0 +1,17 @@
> > +##############################################################
>
> Hi Jie:
> The makefile + makefile.rules split is in accordance to (new) Pin's
> makefile Infrastructure<
> http://software.intel.com/sites/landingpage/pintool/docs/62141/Pin/html/index.html#MAKEFILES>
> . I can rename makefile-->Makefile but would rather retain the split so in
> case the Pin team changes the recommended ‘makefile’ we will be ok. What do
> you think? Regarding setting PIN_ROOT in the makefile, I tried this:
> PIN_ROOT := $(shell echo $$PIN_HOME) However, that is not having the
> desired effect. Do you see what is wrong with this? Thanks.
> -Harish From: Jie Yu [mailto:notifications@github.com] Sent: Monday,
> November 25, 2013 1:43 AM To: jieyu/maple Cc: Patil, Harish Subject: Re:
> [maple] PinPlay enabled Maple (#14<https://github.com/jieyu/maple/pull/14>)
> In makefile:
>  @@ -0,0 +1,17 @@
> +##############################################################
> Can we combine 'makefile' with 'makefile.rules'? Also, I would prefer
> 'Makefile':) — Reply to this email directly or view it on GitHub<
> https://github.com/jieyu/maple/pull/14/files#r7883709>.
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/jieyu/maple/pull/14/files#r7889095>
> .
>