Build process is slow to start about pokeruby HOT 10 CLOSED

Specs?

time make -j16 from make clean results in:

real    2m17.331s
user    1m26.897s
sys     4m53.771s

I don't see a "minute delay" when updating pokeruby.

from pokeruby.

It takes around 4 seconds to run make if I haven't made any changes on my machine, after the first time I've run it. It's slower the first time, though.

If you want to modify the code but not any of the graphics, you could consider using a modified makefile that doesn't scan the asm files for dependencies.

from pokeruby.

This is on my old Pentium 4 desktop (Yeah, I refuse to let it go). Most of the time is dominated by disk activity from scaninc which seems to recursively scan the .s files every time make is invoked. I've put in a rule in my custom Makefile to build .s files from .c files, so I can type "make src/foo.s" and instantly have it compile foo.c into foo.s with no delay.

from pokeruby.

Good idea.

from pokeruby.

I've noticed that even when trying to compile a single C file, for example, make src/wallclock.o VERSION=RUBY, make runs scaninc on all of the .s files in data, even though wallclock.o should not depend on any of those files. Scaninc recursively scans the files, and on a slow hard disk, this can take up to 10 seconds, doing something totally pointless. I don't know enough about make to debug why it's pulling dependencies from there, but nothing in src should depend on anything in data at all.

from pokeruby.

make NODEP=1

from pokeruby.

NODEP solves this issue.

from pokeruby.

NODEP only solves it if you are making changes to just the assembly or programming and not changing any header files. If you are doing anything else, you still need to wait.

from pokeruby.

Not much can be done about that, except for caching the dependencies, possibly.

from pokeruby.

You still have to stat the files, which isn't exactly fast. Ideally you could listen for filesystem changes (eg linux inotify or windows System.IO.FileSystemWatcher) instead.

from pokeruby.