An old program I wrote in the 90's that generates for you Makefiles from your C or C++ sources. This page is only a copy/past of the documentation present in source code's header.

It exists more recent (and probably more powerful) tools, but LFMakeMaker continues to suite my needs and does its job great.

I wrote this little code for automaticaly creating MakeFile for GCC (but may be used with others compilers).
It was developped on the Amiga in a portable way. No Amiga specific function is used... see ports notes.

    LFMakeMaker [option] source_files

Invoque 'LFMakeMaker' without any argument to get the list of available options.

LFMakeMaker 1.1 (Mar 27 2011 14:06:24)
	(c) LFSoft 1997.

LFMakeMaker [options] sources_file
options are:
options for local headers (#include "xxx")
+l or --local : Looks for local headers (default)
-l or --no-local : Doesn't look for local headers
+lr or --recurse-local : Looks recursively into local headers (default)
-lr or --no-recurse-local : Doesn't look recursively into local headers

options for global headers (#include <xxx>)
+g or --global : Looks for global headers
-g or --no-global : Doesn't look for global headers (default)
+gr or --recurse-global : Looks recursively into global headers
-gr or --no-recurse-global : Doesn't look recursively into global headers (default)

Target's options:
-e="filename" or --exec="filename" : Generate executable file
-o or --object : Generate objects file (default)
-t{="filename"} or --target{="filename"} : Links all objects files to the given
	executable. If no "filename" is given, all precedent objects are
	only forgotten.
-so="filename" or --shared="filename" : Links all objects files to the given shared object.
-po{="xxxx"} or --prefix{="xxxx"} : Specify a prefix for object files.

misceanlous options:
+c="filename" or --check="filename" : Add "filename" to dependancies lists
	if present in source file (overwrite '--no-local' and '--no-global')
-c="filename" or --no-check="filename" : Remove "filename" from the list of
	files to checks.
+f="filename" or --force="filename" : Unconditionnaly add "filename" to
	 dependancies lists.
-f="filename" or --no-force="filename" : Remove "filename" form the list of
	files to forces.
+i="filename" or --ignore="filename" : Always ignore "filename".
-i="filename" or --no-ignore="filename" : Remove "filename" from the list
	of files to ignore.
-I"directory" : Add "directory" to the list of include directories.
	Notes: Don't forget trailing separator ('/' on UNIX and AmigaDOS).
	Searches are made in reverse order (last -I searched first).
+cs or --case-sensitif : Be case sensitive.
-cs or --no-case-sensitif : Be case insensitive.
+nc or --nested : Allow nested comments (default).
-nc or --no-nested : Forbid nested comments.
	The default is accorded with your architecture file-system
	(-cs on the Amiga or +cs on Unix).
-cc="cmd" or --compiler="cmd" : Use 'cmd' as compiler command,
	default is 'cc'.
--line="number" : Set the limite of a line length in generated makefile.
--tab="number": Set the number of space for a TAB.
--fatal : Abort if an include file can't be opened
	or when a target is generated twice.
--no-fatal : Warn if an include file can't be opened (default).
-v or --verbose : Display all processed file.
--debug : Display currently active options.

Never forget that a source is affected only by options before it.
E.g.:

LFMakeMaker file1.c +c=truc.h file2.c -c=truc.h file3.c

'truc.h' is only checked in file2.c.

Before reading arguments, LFMakeMaker looks for "LFMakeMaker" environnemental variable that may contains always used options. Its best use is to define path to your include directories tree (-I option).
Look at your compiler's documentation about where includes are located. Some compilers like Gcc may display all include directories at run time but adding '-v' argument (or --verbose) to the command line.

This is an example of LFMakeMaker variable content i use with GCC 2.7.0 on my Amigas:

  setenv LFMakeMaker "-I/gnu/lib/gcc-lib/m68k-cbm-amigados/2.7.0/g++-include/
    -I/gnu/lib/g++-include/ -I/gnu/local/include/
    -I/gnu/m68k-cbm-amigados/include/
    -I/gnu/lib/gcc-lib/m68k-cbm-amigados/2.7.0/include/ -I/gnu/os-include/
    -I/gnu/include/"

• If an #include "" can't be found in the current directory, it'll be searched AS A GLOBAL #include (so --global, ... apply to it).
• LFMakeMaker understand C and C++ source code. In all cases, C++ comments  '//' are allowed. Remember, it looks only for '#include' statement, custom commands like GNU's '#includenext' are IGNORED...
• This tool tries to interpret C's syntax in source files, so commented out includes are ignored (as your compiler does). On the other hand, it does nothing with preprocessor's #if.
• Because it's not a real compiler, it is somewhat easy to trouble syntax parsing of LFMakeMaker. In other words: Intended use of this tool is for "civilized" source code; if your source have syntax error, then LFMakeMaker may generate wrong makefile.
• Because of preprocessor's #if are ignored, be carefull about '{}' paires. For example:

      ..
#ifdef DEBUG
    if(ok && test){ // }
#else
     if(ok){
#endif

Notez-bien : One of the opening '{' is paired by a commented-out '}'. The second is paired (as usual) at the block-ending.

• again because of #if, be carefull with the "--fatal" option as include file may be searched even if it's not applied to your system.
• Remember to indicate include directories (-I) if you want global includes.
• #include macro (where 'macro' is the name of a previous #define) can't be treated.
• On the Amiga, it is safer to use always Unix-like directories notations (as  ':' has an special meaning in Makefiles).

• This source code is in a pure C language. No GNUisme or system specifics are used. It may be compiled by any decent C compiler on much system.
• On the other hand, include files aren't all standardised . Especially, 'unistd.h' and 'sys/syslimits.h' may not exit on your system. access()'s prototype may reside in another file (i.e. 'fcntl.h' for some compilers like DICE on the Amiga). PATH_MAX may have another name or is defined in another file ('dir.h' on ms-dog system).
• Multiple assignations aren't used on bits fields as this may trouble some compilers...
• LFMakeMaker doesn't try to interpret syntax of pathname. So, it may run on other systems with different path syntax like VMS (sorry but, unfortunatly, I don't have the licence to run the VMS-C compiler on my VAX).
• CAUTION : As readsource() may be recursively called, have a look on your stack's size (for fixed stack system only). On my Amiga, a 4K stack looks like to be suffisant (but 8K or more is safer).

Gcc 2.7.0 produces no warnings when compiling with -Wall (all warning enabled). On all systems, following options may be added:

• -O (optimise object code, see your compiler documentation),
• -DDEBUG (Add some run-time messages),
• -DDEBUGALL (Add full run-time messages -- For debugging only --),

On the Amiga, you may add following options to GCC :

• -s (discard symbol and debug hunks, smaller executable),
• -resident (if you want a pure command).
• -noixemul (don't use ixemul.librairy so no external library is needed -- Unrecommended because you loose UNIX syntax for pathname, or you may use  external commodities to patch system's syntax parsing-- ).

Even this tool is FREEWARE, gifts are welcome ( 68060 board, Multi-Sync monitor (ha ha), chocolates, ... or only a post card ). Drop me a mail using the link at the bottom of this page.

LFMakeMaker was developped and tested on

• Amiga 1000 (68010, 8Mb, HD 52Mb, WB 2.1),
• Amiga 4000 (68040, 14 Mb, HD 120 Mb, CD-ROMx4 IDE, WB 3.0),
• MicroVAX II (16Mb, 2x RD54, Ultrix 4.2).

All under GCC 2.7.0 from Amiga's CD-ROM Fresh Fish 10.
Some part of this source code was inspired by my very own LFLocalize 0.5ß.

MungWall & Enforcer are CopyRighted Commodore - Amiga.

• Since version 1.1, LFMakeMaker was tested by MungWall 37.21 (memories allocated/freed tests) and Enforcer 37.55 (illegal memory access). This prevent from memory corruption caused by LFMakeMaker (but not by the code  generated by your C compiler).
• if '--global' isn't set, no warning is displayed if a local include  didn't exist, because, it will be treated like a global one. As search  for global include are disabled, LFMakeMaker doesn't test if the file  exits or not. This is a side effect, not a bug. Maybe fixed in a future  version.

Until now, following bugs had been found in the Amiga version of LFMakeMaker, may not appli to others architectures...

• On 16 bits powered Amigas (with 68000 or 68010 CPU), LFMakeMaker will crash if you break (by CTRL-C or by using Break command) while it runs. Those craches are caused by ixemul.library (version 41.2). I can't fix anything but I hope that future versions of this library will run correctly on 16 bits systems. Such crashes aren't found on 32 bits systems (tested on an Amiga 1200/68020 and on my Amiga 4000/68040).
• Startup code generated by GCC 2.7.0 (and, I think, with many others versions) doesn't like international characters and considers any ASCII > 128 as a separator.

• 22-01-1997 : Start of development.
• 09-02-1997 :
  
  • BF: Its seems that white-spaces may be inserted after '#' for a preprocessor command. fixed now...
  • A: new option : "--compiler"

• 12-02-1997
  
  • A: 'ltarget' store all generated targets. so
    • an object file (and as all other targets) is checked to be generated only one time (if many executables use a same file),
    • the 'all :' target may be generated
  • BF : Many enforcer hits removed (reading at NULL).

• 30-05-2015 (yes, 12 years after !)
• SB : EOF is casted to a char (otherwise it may be ignored when compiled using recent GCC)
• SB : incorrect free() in freelsta(). I duno how I can have miss this one !

• 13-04-2016
• A : Add --shared target aiming to create shared object (.so) target. Works with GCC on Linux.

Aminet orginial files :

• LHA archive (24ko) : contains orgininal source code and Amiga binary
• Aminet's readme

Updated source code :

• Have a look on my Git hub.