This is what I did once for a project where we were building separate libraries but all them with the same rules.
You may have a MASTER makefile just defining the rules and procedures to build targets, and then every makefile in each subdirectory just defines the files for that particular set, and the target name to generate. In my case the target was the library name and the files to include in that library archive.
Where to have the MASTER makefile with the rules it is up to you. In our case, we had that in the root directory and it was also released to application developers for their applications.
Hope that helps.
Nestor
On 9/30/05, Angel Tsankov <[EMAIL PROTECTED]> wrote:
I have a folder named "Projects" where all subfolders have (almost)
the same substructure (in terms of subsubfolders) and I would like to
avoid having multiple makefiles (in each subfolder of Projects) that
do alsmost the same thing - they are, not surprisingly, hard to
maintain. So I'm thinking of combining all makefiles into a single
file to be placed in a folder that will make it accessible from
anywhere (and in particular from any subfolder of Projects).
1. Do you think this is a good idea?
2. If so, where should I place the all-in-one makefile?
Angel Tsankov
[EMAIL PROTECTED]
_______________________________________________
Help-make mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/help-make
_______________________________________________ Help-make mailing list [email protected] http://lists.gnu.org/mailman/listinfo/help-make
