RE: included makefiles

[Reynolds, John]

Thanks Paul.

>If "help" is not a double-colon target, you'll have to get tricky.  For
>example you could do this:
>
>  my-help: help
>        @echo "add -Dproduction=1 after the target name to
>build a production version"
>
>  include ../appmake.make
>
>Now the default target is "my-help", not "help", and that
>target will be
>built if the user doesn't give any override.  Your version prints your
>message but depends on the original "help", so the original would be
>printed then your message.

This was the case for me. Your solution worked great!

>  rj> Ideally, I'd like to add some logic to the template makefile that
>  rj> I have control over so that I can intercept the target name, set
>  rj> the variable and then include ../appmake.make.
>
>I don't quite understand what you're getting at here.

I can make any changes I want to the template makefile. While I can also modify the lncluded makefile (../appmake.make), that file is overwritten by updates to the development kit. So, my best course is to only modify the template makefile.

- - - - - - - Appended by Scientific-Atlanta, Inc. - - - - - - -
This e-mail and any attachments may contain information which is confidential, proprietary, privileged or otherwise protected by law. The information is solely intended for the named addressee (or a person responsible for delivering it to the addressee). If you are not the intended recipient of this message, you are not authorized to read, print, retain, copy or disseminate this message or any part of it. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete it from your computer.