next topic »

[Reply #30 on:]

This feature works by comparing timestamps on the files.

Maybe the files in your arduino directory have timestamps in the future?  Perhaps if you extracted the zip file, then set your clock back?  For example, take a look at the file:

C:\Program Files\arduino-1.0.1\hardware\arduino\cores\arduino\wiring.c

If it's timestamp is in the future, then it will still be considered newer than the .o file.

The easiest solution might be to extract a fresh copy of Arduino 1.0.1.

[Reply #31 on:]

Thanks again for the input.

I checked the dates on my core folder, dated 5/21/2012.  My machine date is current at 03-Jun-2012.

I'll keep digging.  Thanks for the input.

George

[Reply #32 on:]

When you compile, all the  generated files are placed in a temporary directory.  With the verbose info, you can see the full pathname.  If you look in that directory, are there .o and .d files for each source?  Are the timestamps ok?

Could you please post one of the .d files, perhaps wiring_digital.d ?

[Reply #33 on:]

Here are temp folder window captures from 1st and 2nd build of BareMinimum.ino example sketch, along with wiring_digital.d of 2nd build:

I notice the paths listed in wiring_digital.d look a bit strange.  Under windows with a typical install located in "C:\Program Files\..." the path has a space.  I wonder if this could this be confusing the compare parsing algorithm?

Code:

\
 C:\DOCUME~1\gsmall\LOCALS~1\Temp\build8448203176909195487.tmp\wiring_digital.c.o:  \
 C:\Program\ Files\arduino-1.0.1\hardware\arduino\cores\arduino\wiring_digital.c \
  C:\Program\ Files\arduino-1.0.1\hardware\arduino\cores\arduino\/wiring_private.h \
  C:\Program\ Files\arduino-1.0.1\hardware\arduino\cores\arduino\/Arduino.h \
  C:\Program\ Files\arduino-1.0.1\hardware\arduino\cores\arduino\/binary.h \
  C:\Program\ Files\arduino-1.0.1\hardware\arduino\variants\standard/pins_arduino.h

Thanks for your help.

George

[Reply #34 on:]

1st and 2nd run of wiring_digital.c.d from temp build folder attached below.

All,

Has anyone else had this new for release 1.0.1 feature work properly?  If so, could you share your .d file.

Thanks,
George

[Reply #35 on:]

I have the git version of arduino, and the feature has worked properly for me for quite some time (months). Here's wiring.c.d after hitting verify twice

[Reply #36 on:]

Thanks for posting.  Dependencies look similar to mine.  Looks like they are not supposed to change 1st run to subsequent runs.  Guess that makes sense.  The messed up path showns in the .d files on my Win 7 machine looks like a clue.  Hmmm...

Code:

\
 C:\DOCUME~1\gsmall\LOCALS~1\Temp\build3787739127124592615.tmp\wiring_digital.c.o:  \
 C:\Program\ Files\arduino-1.0.1\hardware\arduino\cores\arduino\wiring_digital.c \
  C:\Program\ Files\arduino-1.0.1\hardware\arduino\cores\arduino\/wiring_private.h \
  C:\Program\ Files\arduino-1.0.1\hardware\arduino\cores\arduino\/Arduino.h \
  C:\Program\ Files\arduino-1.0.1\hardware\arduino\cores\arduino\/binary.h \
  C:\Program\ Files\arduino-1.0.1\hardware\arduino\variants\standard/pins_arduino.h

[Reply #37 on:]

If you move your arduino-1.0.1 from C:\Program Files to just C:\ (at least temporarily for the sake of testing), does that make this magically start working?

FYI: lately I haven't had any time for Arduino hacking... 2 huge project deadlines, one recently passed, the other is a huge interactive fire art installation that shows next weekend.  I plan to look into this issue in early July.  If you could confirm (or refute) that moving the just C:\ fixes the problem before then, please do.