I am in the process of creating a build tool too (for a different language: Java)
I noticed that you have some magic variables (%f), like make ($<, etc..). I am trying to avoid that, but I cannot come up with a clean way without 'magic' variables (e.g. When using wildcards, one would need to know the set of files that have changed. Mine is something similar to
classes/**/*.class -> src/**/*.java:
javac [WHAT TO USE IF NOT A 'Maigc var'?]
Also:
1. Will fez support different dir for target and recipes? (like above example I gave) ?
2. What about targets that do not have a file dependency (e.g. .PHONY in make)? How does fez deal with it?
What I am trying to avoid is a big learning curve (or have a user need to read a book) :-)
Comments
I am in the process of creating a build tool too (for a different language: Java) I noticed that you have some magic variables (%f), like make ($<, etc..). I am trying to avoid that, but I cannot come up with a clean way without 'magic' variables (e.g. When using wildcards, one would need to know the set of files that have changed. Mine is something similar to
Also:1. Will fez support different dir for target and recipes? (like above example I gave) ?
2. What about targets that do not have a file dependency (e.g. .PHONY in make)? How does fez deal with it?
What I am trying to avoid is a big learning curve (or have a user need to read a book) :-)
Thank you and success in your project!