• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 54 subscribers
  • Views 476 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/CC2640R2F: CCStudio SW dependencies de-bundle

A. Hutanu
Prodigy 110 points

Part Number: CC2640R2F

Tool/software: Code Composer Studio

In the future will Code Composer Studio will include only the TI part from the long list of CCS dependencies?

Currently now everything is bundled with the installer but that is not really needed because there are Windows package managers for example Chocolatey which can handle the dependencies part.

--> https://chocolatey.org/about

This could greatly improve how CCS is installed and also make sure that CCS does not spend time on download/reinstall what is already installed on the system.

The list of available packages is located here:

--> https://chocolatey.org/packages

For example, some of CCS9 dependencies could be installed with the following command line:

choco install vcredist2008 vcredist2012 vcredist2015 jre8

Feedback is appreciated.

  • 0
    TI__Guru**** 163035 points

    In a web installer scenario (where components are downloaded as needed) a package manager like chocolatey could be used in place of our own package manager.  

    For CCS today we only provide an off-line installer.  The off-line installer needs to be able to operate in situations where there is no internet connection.  In this case all of the dependencies need to be present in the installer as you will not be able to fetch them from the internet.  Thus today something like chocolatey would not help.

    The truth is that we do handle this differently on Linux.  On Linux we bundle fewer items (JRE is bundled) and only check for missing dependencies. We then require users to install them using the package manager of their choice (apt-get, yum...).  This is mainly because the packages that contain the dependencies will vary by distribution and managing those packages is typically something a Linux user wants to do themselves.

    I will pass on the information to our installer team.  Thank you for the feedback.

    Regards,

    John