This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CODECOMPOSER: When copying project to another PC, if we Export → Import, the creation time of all files will change

Part Number: CODECOMPOSER

Hi experts,

When copying project to another PC, if we Export → Import, the creation time of all files will change.
(including .c and .h files, the update time of the file will be updated to the time of import).

Is there a way to prevent the file creation time from changing?

Best regards,
O.H

  • Is there a way to prevent the file creation time from changing?

    I doubt it.

    Why are you forced to use the Export/Import feature, is there something complex about your project? Why not just copy the project folder to the destination and import the .cproject? That shouldn't change any source code timestamps.

  • Hello,

    If you are selecting the option "Copy project to workspace" when you import the project, then CCS is making a copy of the files and creating them in the workspace. Hence the file creation date would be when the files are copied/created. This is expected.

    The file creation time should not change if you are not selecting that option during the import.

    Is this what you are observing?

    Thanks

    ki

  • Hi Kier,

    Thank you for the reply.

    As a result of additional investigation, it appears that if we check "copy projects into workspace" when importing, the update time of the file changes.
    If we copy and paste within Workspace after importing, the update time will not change.

    The customer was new to CCS and recommended the Export->Import procedure.
    If they do not want to work on the original project, I instruct uncheck copy when importing, and then copy and paste within Workspace.

    Best regards,
    O.H

  • Thanks for confirming the solution.