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 local package like this doesn't mean you must publish it to pkgs.r-l.org.) On Mon, Mar 11, 2019 at 3:00 PM Brian Adkins <lojicdot...@gmail.com> 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 8 "cores" with -j 8, and I *think* I'd lose that > with xargs. > > What is the best practice for making a tree of Racket code? > > Thanks, > Brian > > -- > You received this message because you are subscribed to the Google Groups > "Racket Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to racket-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
