diff options
Diffstat (limited to 'readme.md')
| -rw-r--r-- | readme.md | 12 |
1 files changed, 6 insertions, 6 deletions
@@ -135,7 +135,7 @@ sbt bin/test:assembly bin/target/mill devAssembly # Build Mill executable using the Mill executable generated by Mill itself -out/devAssembly devAssembly +out/devAssembly/dest devAssembly ``` Eventually, as Mill stabilizes, we will get rid of the SBT build entirely and @@ -188,7 +188,7 @@ run something via `mill Core.cross[a].printIt` while from code you use ### Caching by default Every `Target` in a build, defined by `def foo = T{...}`, is cached by default. -Currently this is done using a `foo.mill.json` file in the `out/` folder. The +Currently this is done using a `foo/meta.json` file in the `out/` folder. The `Target` is also provided a `foo/` path on the filesystem dedicated to it, for it to store output files etc. @@ -209,10 +209,10 @@ structures where a previous process left off, in order to continue the build. Re-construction is done via the hierarchical nature of the build: each `Target` `Foo.bar.baz` has a fixed position in the build hierarchy, and thus a fixed -position on disk `out/foo/bar/baz.mill.json`. When the old process dies and a +position on disk `out/foo/bar/baz/meta.json`. When the old process dies and a new process starts, there will be a new instance of `Target` with the same implementation code and same position in the build hierarchy: this new `Target` -can then load the `out/foo/bar/baz.mill.json` file and pick up where the +can then load the `out/foo/bar/baz/meta.json` file and pick up where the previous process left off. Minimizing startup time means aggressive caching, as well as minimizing the @@ -328,9 +328,9 @@ the `Target`s you can run. A `Target`'s position in the module hierarchy tells you many things. For example, a `Target` at position `Core.test.compile` would: -- Cache output metadata at `out/Core/test/compile.mill.json` +- Cache output metadata at `out/Core/test/compile/meta.json` -- Output files to the folder `out/Core/test/compile/` +- Output files to the folder `out/Core/test/compile/dest/` - Be runnable from the command-line via `mill Core.test.compile` |