Jump to content


Some warnings when building executable


  • You cannot reply to this topic
2 replies to this topic

#1 The.Soloist

    Member

  • Members
  • PipPip
  • 7 posts

Posted 15 March 2009 - 09:45 PM

Hi all,
I'm new to Impulse C so this could be beginner-level questions:
Sometime when I build the program for simulation executables, it gives me this kind of warning:

make: Warning: File `C:\Documents and Settings\hxdai\My Documents\blast_getstring\_Makefile' has modification time 0.56 s in the future

And this time varies, and sometime I don't get this warning. I am confused by this. Based on my knowledge(which is little), this may have something to do with the streams' format(INT_TYPE(n), CHAR_TYPE, etc), but I checked this and still get this warning... Any thoughts or suggestions? Thanks in advance.

#2 RalphBodenner

    Advanced Member

  • Admin
  • PipPipPip
  • 348 posts

Posted 16 March 2009 - 08:34 PM

Hi,

Are your CoDeveloper installation and working files on separate machines, perhaps using a network share? You can safely ignore this warning in many cases, but I would suggest doing a Project > Clean Project command between builds to make sure that any code changes get recompiled.

I notice that your project files are in a directory with spaces in the path; this is not a problem with CoDeveloper, but some third-party hardware tools you may use after generating HDL may not work with such pathnames.

Regards,
Ralph
Ralph Bodenner
Impulse Accelerated Technologies, Inc.

#3 The.Soloist

    Member

  • Members
  • PipPip
  • 7 posts

Posted 19 March 2009 - 05:53 PM

QUOTE (RalphBodenner @ Mar 17 2009, 12:34 AM) <{POST_SNAPBACK}>
Hi,

Are your CoDeveloper installation and working files on separate machines, perhaps using a network share? You can safely ignore this warning in many cases, but I would suggest doing a Project > Clean Project command between builds to make sure that any code changes get recompiled.

I notice that your project files are in a directory with spaces in the path; this is not a problem with CoDeveloper, but some third-party hardware tools you may use after generating HDL may not work with such pathnames.

Regards,
Ralph

Thanks for the reply. I didn't notice the space thing in the path, but my codeveloper installation and workfiles are on the same machine's same drive, so that won't be a problem.





1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users