On 10/01/2014 04:04 PM, [email protected] wrote: > Anyway - I've created a simple test case that uses GCC and mimics your > test. [...]
Using your files and Cygwin32 GCC it works as expected, no unnecessary rebuilds. tup saves the correct mtimes of the program and the map file on the first run. > There are no rebuilds after that. If I touch main.c to cause a rebuild, > the dates are updated to what stat gives. Same here. If I instead touch the generated program or map file, I get the same message as with my toolchain. But this time it is expected, because the generated file's mtime has really changed behind the back of tup. So it looks like the problem is specific to the tup / Tasking linker combination. Unfortunately I'm not able to test with Linux to rule out a Windows issue, as I do not have Linux binaries of the Tasking toolchain. Kind regards, Bernhard. -- -- tup-users mailing list email: [email protected] unsubscribe: [email protected] options: http://groups.google.com/group/tup-users?hl=en --- You received this message because you are subscribed to the Google Groups "tup-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
