I adore the simplicity of make as a declarative build tool, but for a build system whose operative principle is a close correspondence with the filesystem, the placement of additional, subtle restrictions on valid filenames are ridiculous. I’d happily trade away most of make’s features for a core that didn’t choke on spaces.
(If anybody knows of such an alternative, please share!)
To try to making workingwith JavaScript more tolerable I wrap up everything with the C Preprocessor, seems I am not alone on this either. This gives me #include and #define, plus I am overly keen on NDEBUG (so using make NDEBUG=1 for non-debug builds).
I adore the simplicity of
makeas a declarative build tool, but for a build system whose operative principle is a close correspondence with the filesystem, the placement of additional, subtle restrictions on valid filenames are ridiculous. I’d happily trade away most ofmake’s features for a core that didn’t choke on spaces.(If anybody knows of such an alternative, please share!)
I think it’s pretty common on UNIX platforms to avoid spaces where possible. Finding spaces in filenames is peculiar, and generally not a good sign.
This page does not render well at all on Android’s Chrome or Firefox for Android.
Should be better now. Thank you for reporting.
To try to making workingwith JavaScript more tolerable I wrap up everything with the C Preprocessor, seems I am not alone on this either. This gives me
#includeand#define, plus I am overly keen onNDEBUG(so usingmake NDEBUG=1for non-debug builds).Anyway, the runes I use are:
Of course, like in the article, you can then have minified targets or anything else you like too.
Suggestion: add
Gemfileas a prerequisite tobundle.