• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 55 subscribers
  • Views 366 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

CCS: CCS and product installation

Guy Mardiks
Genius 4135 points
Other Parts Discussed in Thread: SYSBIOS

Tool/software: Code Composer Studio

Hello,

Using CCS 8.1.

I have placed the tools and products we are using under GIT source control.

When configuring CCS to search fro the products in the repository folder, it find the products but when trying to install it issues an error:

"An Error Occurred While Collecting Items To Be Installed"

this happens both for the XDC and sysBios.

When trying to install from another local location it succeeded.

The difference when comparing the folders appears to be with line ending difference.

Git modifies line-endings only for files considered as text - why would such change on these kind of files cause an installation error?

Can you help explaining the problem - what is the root cause, how to solve it and if possible what would be the recommended git configuration that will allow proper commit and checkout of the product tools.

Thanks

Guy

  • 0
    Guru 26200 points
    Hello Guy,

    I would not resolve your issue.
    Microsoft standard use CR/LF, Linux/Unix uses LF.
    Probably under Ubuntu dealing with git would go smoothly.

    My question is why do you install TI products under control of git?
  • 0
    Guru 92251 points

    Guy Mardiks said:
    Git modifies line-endings only for files considered as text - why would such change on these kind of files cause an installation error?

    I don't know how the installation program processes the text files, but if there is any CRC / digest validation check on the files the installation could be considered invalid if the line endings change.

    I haven't tested it, but from looking at the GIT documentation creating a .gitattributes file in the root directory with the following should prevent GIT from converting line endings:

    * text=unset

    GIT normalizes line endings on check-in, and so I think you need to add the .gitattributes file on the first check-in (since otherwise the files in the repository could have already had line endings normalized to LF).

  • 0 in reply to Chester Gillon
    Genius 4135 points
    Hi,
    Since could not find an explanation as to which files cause the problem, i used .gitattributes with * -text