Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement more robust way of handling CCS installation paths #61

Closed
webbcam opened this issue Feb 7, 2019 · 1 comment
Closed

Implement more robust way of handling CCS installation paths #61

webbcam opened this issue Feb 7, 2019 · 1 comment
Assignees
Labels
feature New feature or request

Comments

@webbcam
Copy link
Owner

webbcam commented Feb 7, 2019

Make TIFlash handle CCS installation locations in a more robust manner.

Context

CCS is not always installed in the default install location. Many times users may have multiple versions of CCS installed and thus place them in a different directory structure.
e.g.
/Applications/ti/CCS7.4/ccsv7/...
/Applications/ti/CCS8.0/ccsv8/...
/Applications/ti/CCS8.1/ccsv8/...

Expected result

TIFlash should be able to find the proper CCS installation even when the CCS installation directories are not structured as the default.

Current result

TIFlash relies on a particular, hardcoded directory structure for CCS installations.
e.g.
/Applications/ti/ccsv7/...
/Applications/ti/ccsv8/...

Possible Fix

Replace hardcoded method with a searching algorithm that searches for the "ccs root" folder. The "ccs root" folder should always contain:

  1. An eclipse/ folder with ccs.properties file and ccstudio or eclipsec.exe executable
  2. A ccs_base/ folder

By searching for these requirements, TIFlash should be able to find a valid CCS installation given a CCS_PREFIX (e.g. /Applications/ti) without using a hardcoded path


@webbcam webbcam added the feature New feature or request label Feb 7, 2019
@webbcam webbcam self-assigned this Feb 7, 2019
@webbcam
Copy link
Owner Author

webbcam commented Feb 7, 2019

#60 related issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant