I think the best practice (at least my usual practice these days) is
to make a package.
Say the top of your tree is /path/to/project.
Once:
raco pkg install /path/to/project
Thereafter your "make" is:
raco setup --pkgs project
This also works fine for c:\path\to\project.
(Making it a
On 3/11/2019 3:00 PM, Brian Adkins wrote:
I looked over the documentation for raco make, and I didn't see
anything about how to recursively make all *.rkt files in a directory
tree. I suppose I could use something like: find . -name \*.rkt |
xargs raco make, but I like being able to use all
I looked over the documentation for raco make, and I didn't see anything
about how to recursively make all *.rkt files in a directory tree. I
suppose I could use something like: find . -name \*.rkt | xargs raco make,
but I like being able to use all 8 "cores" with -j 8, and I *think* I'd
lose
3 matches
Mail list logo