"compiler family" is a perfectly fine term.
Pelles C used to be supported, try `cc=pcc`:
# Pelles C Compiler
compiler pcc:
# Pelles C
result = (
name: "pcc",
objExt: "obj",
optSpeed: " -Ox ",
optSize: " -Os ",
compilerExe: "cc",
cppCompiler: "",
compileTmpl: "-c $options $include -Fo$objfile $file",
buildGui: " -SUBSYSTEM:WINDOWS",
buildDll: " -DLL",
buildLib: "", # XXX: not supported yet
linkerExe: "cc",
linkTmpl: "$options $buildgui $builddll -OUT:$exefile $objfiles",
includeCmd: " -I",
linkDirCmd: "", # XXX: not supported yet
linkLibCmd: "", # XXX: not supported yet
debug: " -Zi ",
pic: "",
asmStmtFrmt: "__asm{$n$1$n}$n",
structStmtFmt: "$1 $2",
packedPragma: "", # XXX: not supported yet
props: {})
That said, Pelles C (and Borland C and Digital Mars C) had just too many bugs
to support them. I don't think bootstrapping ever worked with Pelles C. As of
2016, there are really only 3 widely used C(++) compilers left: Clang, GCC and
Visual C, so there is hardly a need to make the configuration system even more
generic.
