ISE build dependencies

The timestamp thing can be a problem for make-based dependency checking (which ISE uses).

But if all the design files are stored on the same computer, I would think that the timestamp would be consistent across all of them.

As a practical matter, would it be possible for you to simply check the time on all relevant computers? The first step to corrective action is to determine what the problem is. Inconsistent time is one hypothesis, now you should test it. If the time is consistent, then you will have to come up with a new hypothesis.

--Mac

Well, the files are stored on a remote computer. Looking at the file timestamps in an explorer window, I did notice that when I refreshed the window, some of the working files were later than the time displayed on the local computer (where the compilation takes place). I did bump up the local time by a couple of minutes in order to guess an approximate equal time for both computers, but I still experienced the same problem.

-Newman

If you want to solve this problem, here is what I suggest. First, devise a simple, repeatable test which identifies the problem.

Then, formulate a hypothesis about what is causing the problem, and take appropriate steps (according to the hypothesis) to make the problem go away. Then perform the simple repeatable test to see if the problem is fixed. If it is fixed, then, just to be sure, undo the fix, and perform the test again to make sure the problem comes back. Sometimes I go back and forth like this several times to really convince myself that I have solved the problem.

If the potential solution doesn't work, undo it, and try another potential solution. And so on.

In this case, the question you should ask yourself is, did you synchronize the clocks or not? Do you feel that you have ruled out clock differences as a potential cause of the behavior you are seeing or not? If you haven't ruled it out, then keep messing around until you can.

I would think the one thing you DON'T want to have, is files with modification times in the future, so if you can't sync the clocks exactly, at least try to make the clock on the system running the compiler slightly faster than the one storing the data.

Good luck.

--Mac

site(ie I

privileges).

green check

Sometimes

reruns

file had

like the

checking

would think

check the

action is to

hypothesis, now

to come

file

refreshed the

displayed on the

the local

time for

devise a

take

go

is

perform

back

have

potential

synchronize

can.

exactly,

slightly

There's another possible problem, if your systems are not set up for the same time zone. In this case if the computers have the same time the file system will think the dates are off by the time zone differential.

Also I know it's a pain but the simplest workaround is to right click on the report file in the process window and "open without updating". If you need to generate a new report or re-synthesize you can use the right-click "rerun" or "rerun all" to force a new build.

Good Luck Gabor