The dependency-tracking winds up creating issues with
wanting to run a "make install" after a "make release" -
since the Makefile was calling "mkdir -p" to auto-create object
and dependency folders, timestamps would (maybe) be updated and cause
a rebuild using default CFLAGS/CXXFLAGS. "maybe" because it differed
based on what operating system was in use.
This simplifies things a bit - a user can just run their own "make
clean" if they need a rebuild with different flags, now object file
timestamps will only be compared against their source file timestamps
and not trigger unnecessary rebuilds. The dependency-tracking for Make
doesn't seem to make a big difference with regard to build times.
This also auto-sets default CFLAGS/CXXFLAGS if not given (a user
running "make demo" with no other flags would trigger this).
The dependency-tracking winds up creating issues with wanting to run a "make install" after a "make release" - since the Makefile was calling "mkdir -p" to auto-create object and dependency folders, timestamps would (maybe) be updated and cause a rebuild using default CFLAGS/CXXFLAGS. "maybe" because it differed based on what operating system was in use.
This simplifies things a bit - a user can just run their own "make clean" if they need a rebuild with different flags, now object file timestamps will only be compared against their source file timestamps and not trigger unnecessary rebuilds. The dependency-tracking for Make doesn't seem to make a big difference with regard to build times.
This also auto-sets default CFLAGS/CXXFLAGS if not given (a user running "make demo" with no other flags would trigger this).