1. 22
  1.  

  2. 3

    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!)

    1. 2

      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.

    2. 3

      This page does not render well at all on Android’s Chrome or Firefox for Android.

      1. 5

        Should be better now. Thank you for reporting.

      2. 3

        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).

        Anyway, the runes I use are:

        CPPFLAGS := -x assembler-with-cpp -P -undef -Wundef -nostdinc -Wtrigraphs -fdollars-in-identifiers -CC
        
        ifdef NDEBUG
            CPPFLAGS += -DNDEBUG=1
        endif
        
        whatever.js: whatever.jscpp
            $(CPP) $(CPPFLAGS) -o $@ $<
        

        Of course, like in the article, you can then have minified targets or anything else you like too.

        1. 2

          Suggestion: add Gemfile as a prerequisite to bundle.