RE: [cdt-patch] Managed make, supplemental makefiles

[Sean Evoy <sevoy@xxxxxxxxxx>]

Jeremiah,
I was thinking out loud on the filename
issue, specifically about the best way for users to edit their custom build
steps. Obviously, the makefile editor would be one place to start, but
since it only recognizes files called 'makefile' as makefiles .... Anyway,
that's a problem for another day. Your proposed solution is a great start.
Thanks for submitting it.

I am working your refactor patch into
the code now. I had my own work that conflicted with it, but now it's in
I can resolve those conflicts. 

Sean Evoy
Rational Software - IBM Software Group
Ottawa, Ontario, Canada

"Lott, Jeremiah" <jeremiah.lott@xxxxxxxxxxx>
Sent by: cdt-patch-admin@xxxxxxxxxxx

02/26/2004 03:06 PM

Please respond to
cdt-patch

To	<cdt-patch@xxxxxxxxxxx>
cc
Subject	RE: [cdt-patch] Managed make, supplemental makefiles

We can also change the names of
the supplemental makefiles to whatever you want.  However recognizing
different extensions is a feature all on its own.
 
By the way, did my ToolReference
refactor patch integrate into your stuff OK?  Just checking if I'll
be seeing it in one of your upcoming commits. :)
 
  Jeremiah
-----Original Message-----
From: Sean Evoy [mailto:sevoy@xxxxxxxxxx] 
Sent: Thursday, February 26, 2004 2:47 PM
To: cdt-patch@xxxxxxxxxxx
Subject: Re: [cdt-patch] Managed make, supplemental makefiles


Thanks Jeremiah, 
As soon as I get my stuff in, I will take a look at this. I guess we are
going to have to update the makefile editor to pay attention to files with
different extensions so users can easily edit the one we want them too.

Sean Evoy
Rational Software - IBM Software Group
Ottawa, Ontario, Canada

"Lott, Jeremiah" <jeremiah.lott@xxxxxxxxxxx>
Sent by: cdt-patch-admin@xxxxxxxxxxx

02/26/2004 01:06 PM

Please respond to
cdt-patch

To	<cdt-patch@xxxxxxxxxxx>
cc
Subject	[cdt-patch] Managed make, supplemental makefiles

The patch adds some -include statements to the top-level makefile.  The
intent is the user can provide these files to cusotmize the makefiles
behavior.

Makefile.init - included at start of file
Makefile.defs - included after macro definitions, but before target
definitions Makefile.targets - included after target definitions (i.e.
at end of file)

We've found this is an easy way to allow customers to customize managed
make, without getting into internal details.  They can add extra
dependencies to files, or even define targets for otherwise unknown
types (such as .idl, etc.).  They can also specify flags in the "Other
flags" field in the UI like so: $(VERBOSE), and then put VERBOSE =
-Wall
in Makefile.init, for example.

Since these files are included using -include, if the user does not
provide them, the makefile works as normal.

This patch also adds a "auto-generated file do not edit" banner
to the
top of all generated makefiles.  Minimizes confusion, as people
sometimes try to edit these files and are confounded by the fact that
their changes keep disappearing.

 Jeremiah Lott
 TimeSys Corporation