Subversion Repositories Programming Utils

Compare Revisions

Ignore whitespace Rev 83 → Rev 84

/trunk/C-CPP-utils/supermakemake/MakefileObject.cpp
199,11 → 199,13
}
if( memcmp( buffer, "CC =", 4 ) == 0 ){
(*configuration)["c_compiler"] = parseList( buffer );
string parsed = parseList( buffer );
(*configuration)["c_compiler"] = trim( parsed );
}
 
if( memcmp( buffer, "CXX =", 5 ) == 0 ){
(*configuration)["cpp_compiler"] = parseList( buffer );
string parsed = parseList( buffer );
(*configuration)["cpp_compiler"] = trim( parsed );
}
 
/trunk/C-CPP-utils/supermakemake/makemake.1
1,14 → 1,47
.TH MAKEMAKE 1 "JULY 2011"
.TH MAKEMAKE 1 "DECEMBER 2013"
.SH NAME
makemake, gmakemake \- automatically create and update makefiles
.SH SYNOPSIS
.B makemake [options]
.LP
.B gmakemake [options]
 
 
.SH DESCRIPTION
.B makemake
.I makemake
or
.I gmakemake
will automatically create makefiles for use with the make command.
makemake goes this by making certain assumptions about the files to be compiled,
and the environment that it is compiling in. Therefore, it is not a
general-purpose build system, but an easy to use and more specialized build
system.
.LP
The only difference between
.I gmakemake
and
.I makemake
is the makefiles that are generated.
.I gmakemake
will generate makefiles for use with GCC, whereas
.I makemake
assumes that you are creating makefiles for use with Sun's compiler. This
is due to historical reasons.
 
.SH OPTIONS
.sp 1
.TP 0.5i
.BR --update
Update the makefile in the current directory
 
.SH ABOUT
.I makemake
was originally written by Professor Sidney Marshall of the Rochester Institute
of Technology, Computer Science Department. At the time it was written, Sun Solaris
machines were the predominant computer in use in the Computer Science department,
so both GCC and Sun's compiler were installed.
 
.SH BUGS
Please report bugs @ programming.rm5248.com
 
.SH AUTHOR
rm5248