Remodel unlike make, it will use MD5 hashes to detect new content and provide, dependency build.
Remodel uses a different grammar than make. Dependencies can appear in any order. If you execute remodel with no arguments, it should start with the pseudo-target DEFAULT. Otherwise, the root is the argument to remodel, as in remodel foo.o.
program ::= production*
production ::= target '<-' dependency (':' '"' command '"")
dependency ::= filename (',' filename)*
target ::= filename (',' filename)*
Here's an example that builds the program baz from two source files, foo.cpp and bar.cpp.
DEFAULT <- baz
baz <- foo.o, bar.o: "g++ foo.o bar.o -o baz"
foo.o <- foo.cpp : "g++ -c foo.cpp -o foo.o"
bar.o <- bar.cpp: "g++ -c bar.cpp -o bar.o"
The dependencies are stored on disk in a special directory called .remodel/, so that remodel will not re-execute any commands unless a dependency has been violated.
Remodel is pretty simple to use. Have all the build dependencies writted to config file named "config" (without the quotes ofcourse :) . If no parameters are passed to it, default will be choosen as root.
$ go build main.go
$ ./main <optional_root_name>The following the go version
$ go version
go version go1Note: The program assumes all the files are present in the same directory as main.go Currently, it does not support files present in sub-directories :( .
- Check for 1st time Scan
- Check Intermediate Builds
- Builds based on Checkpoints
- Check For Cyclic Dependencies
- Handling of Missing source files / Intermediate object files