CCSv5 Corrupts imported project file's timestamp

Hi John,

Is the StellarisWare example project folder you are building inside the StellarisWare install default directory? Basically when you imported your project, did you leave the project in the original directory instead of copying the files into the workspace folder?

Thanks

ki

Ki-Soo Lee said:

Is the StellarisWare example project folder you are building inside the StellarisWare install default directory? Basically when you imported your project, did you leave the project in the original directory instead of copying the files into the workspace folder?

Hi Ki,

A bot of both. Initially I imported a project into a new workspace which is located outside of the Stellarisware directory tree.

Then I deleted the links to the files that I would be modifying and dropped a copy of them into the new workspace project directory.

So now the project contains links to ThirdParty software etc. and I copied the "root folder" files into the project in the new workspace.

Regards

John

John - I asked because I recall some old issue regarding a similar error message about the timestamp being out of range when building a StellarisWare example. The cause was apparently that StellarisWare examples are dependent on the directory structure that it comes in and projects (and source files) need to remain in the original location on import. How this has anything to do with altering timestamps I do not know. But I was wondering if you could try importing the project but leaving it in the original location and see if the issue goes away.

Another thing to check is if you have multiple versions of gmake installed. When you run gmake from the DOS command line, which one is used?

Thanks

ki

Hi Ki,

I imported the Blinky project into my Workspace. I had no option but to import the files as the option to copy the files was ticked but greyed out i.e. I couldn't deselect it. So the imported project has copies of the source files in the project root and the sub-folders are 'links'

The project builds but there is a timestamp issue the first time I build it.

Subsequent builds also show the following...

**** Build of configuration Debug for project blinky ****

Z:\Texas Instruments\ccsv5\utils\bin\gmake -k all 

gmake: ../blinky.c: Timestamp out of range; substituting 1970-01-01 01:00:00

gmake: ../startup_ccs.c: Timestamp out of range; substituting 1970-01-01 01:00:00

gmake: ../blinky_ccs.cmd: Timestamp out of range; substituting 1970-01-01 01:00:00

gmake: Nothing to be done for `all'.

**** Build Finished ****

So I had a look at the file timestamps when I imported the project and they are all dated 1 January 1904. 

If I run 'gmake -version' from the command line it reports as V3.81. At this stage I don't think that this is the issue.

BTW: I have also tried this on CCSv4.2 and this version allows me to select whether I want to copy files into the Workspace for the project and also the files are timestamped at today's date rather than 1904 when they are imported into the project. Of course this is from the version of Stellarisware associated with version of CCS.

Hope this helps!

Best Regards

John

John Anderson1 said:

I had no option but to import the files as the option to copy the files was ticked but greyed out i.e. I couldn't deselect it.

I see this too and I think it is a bug. As far as i know, StellarisWare projects should not be copied into your workspace. Investigation ongoing...

Ki-Soo Lee said:

I had no option but to import the files as the option to copy the files was ticked but greyed out i.e. I couldn't deselect it.

I see this too and I think it is a bug. As far as i know, StellarisWare projects should not be copied into your workspace. Investigation ongoing...

[/quote]

Scratch that. StellarisWare projects can be copied to the workspace folder and the box being ticked and greyed out is intentional to prevent users from modifying the original copies of the project.

Now back to your original issue. Your gmake version looks fine. I noticed that you have CCS installed on a 'Z' drive. Is that some sort of network drive? Do you have CCS in source control in a ClearCase VOB?

Thanks

ki

Hi Ki,

Good to rule out how projects are imported being an issue in CCS.  

I am running CCS in a Windows 7 guest OS on Parallels running on OSX Lion. CCS does not handle UNC directory paths and I also wanted it installed in a directory that is backed up by Time Machine even when the guest OS is not running. So Z: is mapped to a folder in my Documents space. My Workspace is also on this mapped drive. This has worked successfully on previous versions of CCS. 

Best regards

John