The way I have it, so far, Config_0_0 performs it's tasks, then deletes the objects so the next target can rebuild the files. This doesn't happen, becuase the dependencies must have already been checked and the files existed at that time. Config_0_1 attempts to build its target from the objects created by Config_0_0, but they are not there anymore.
That's right. GNU make does it's dependency checking before it starts to do any work. That's why it isn't working.
Is there a reason (other than disk space) that you need to use the same directory for all the object files for all the targets? Why not create a seperate directory for each configuration and then do the delete at the end of the build (or not at alland ask the user to do a make clean as is common practice.)? By doing it the way you're doing it, you're making it impossible for a developer to take advantage of make's ability to "build only what needs to be built".
Just my 2 cents.
Mike Gibson [EMAIL PROTECTED]
_______________________________________________ Help-make mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/help-make
