eobrain/bajel

A build system modeled on make.

bajel's Issues

Variables definitions cannot contain built-in variables $@, $+, or $+

Allow uppercase naming of build file: BUILD.toml, BUILD.yaml, ... and document these as preferred

Allow glob wildcard filename expansion for dependencies

I would like to be able to write:

SOURCE: "**/index.md"

and then use SOURCE as a dependency (as per #26) and in commands:

output.html:
  deps:
  - $(SOURCE)
  exec: "transmogrify output.html $(SOURCE)"

Allow variables defined as arrays to be referenced as strings (blank separated)

Allow deps to be specified as blank-separated string.

Allow a dependency to be a URL.

• Download if newer than target.
• Download to a temporary file, which is what $< and $+ will refer to.

So instead of ...

some_target:
  deps:
  - downloaded_file.csv"
  - other_dep
  exec: do_something $< >$@

downloaded_file.csv:
  exec: wget --output-document=$@ https://foo.com/some-url.csv

... you could just have ...

some_target:
  deps:
  - https://foo.com/some-url.csv
  - other_dep
  exec: do_something $< >$@

Bajel does not echo the executed commands when used in Node versions >= 14.0.0

Time-stamp up-to-date checking does not work when target has a variable reference.

abc_test is flaky

If all the sets are run with npx ava then sometimes abc_test failes as shown below. It never seems to fail when running just npx ava test/abc_test.js.

  abc_test › abc generated var

  test/abc_test.js:135

   134:     const out = stdout + stderr          
   135:     t.regex(out, /^echo "Aaa" > .*\/a$/m)
   136:     t.regex(out, /^echo "Bbb" > .*\/b$/m)

  Value must match expression:

  `Problem expanding percents: Error: ENOENT: no such file or directory, stat 'test-REvEdH'␊
  `

  Regular expression:

  /^echo "Aaa" > .*\/a$/m

  › test/abc_test.js:135:7

Interoperability with package.json

1. Allow JSON version of build spec to be embedded in package.json
2. Incorporate standard scripts property actions as Bajel actions.

variables in TOML, Markdown, etc. formats?

Hi,

The README says:

the following examples [...] each of which specify the same thing

but the examples don't look the same, since the JavaScript ones use variables like CC, CFLAGS, etc.
You might want to make that clearer.

"if you want to use variables for complex builds":
I like things clean and readable, but makefile-style variables seem hard to do without, even for simple builds...
So I tried doing a build.mjs but I get Error: Not supported and a stack trace ending with 'Error reading file': '/home/kai/fooproject/build.mjs'

But anyway I bet that, for a project like this to work, it needs its own custom language.
Using a standard format for programming is tempting, but I suspect, a dead-end.
That's why we have so many programming languages, and why we don't program (much) in XML or whatever.

Nice idea for a project, anyway.

Though it seems quite new to be referenced in Wikipedia, which is how I came across it...
https://en.wikipedia.org/wiki/List_of_build_automation_software#Make-incompatible

Allow 'build.yml' as well as 'build.yaml'

House style is .yml rather than .yaml (though we do use .json - go figure...)