3 ms·
Ah, now I understand the problem, thanks! Indeed I've stayed away from -j because it's very hard to figure out how recipes may interact when you have a complex
by gumby 7y ago
Ah, now I understand the problem, thanks!
Indeed I've stayed away from -j because it's very hard to figure out how recipes may interact when you have a complex Makefile (and with a simple one -j rarely helps much).
I like your fix; even without -j, if some-tool is expensive to run you don't want it run redundantly.
- aidenn0 7y agoI use make (or redo) with -j for parallelizing tasks all the time. It's a really great tool for that. If you specify your dependencies correctly, then -j will not break anything (other than out-of-memory when parallelizing beyond your memory resources). Many implementations of redo have an option that will randomize the order of building dependencies; it's a useful way for testing if you have your dependencies fully specified or not. For non one-off tasks where incremental builds are desired, I've been really liking tup. It will automatically catch many mistakes with dependencies for you up-front, saving much hair-pulling down the road. [edit] An example of what I use make/redo parallelization for in one-off scripts is bulk conversion of images or sound files; it's usually 1 file in 1 file out and rarely are the tools already heavily parallel.