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.

A lot of issues installing CCS on 'G:' drive Please advice

Other Parts Discussed in Thread: EK-TM4C1294XL

Had to install CCS on 'G:' drive. (Actually the EK-TM4C1294XL-CCS-786 install package for connected launchpad)

Part of make used ${CCE_INSTALL_ROOT}, so this worked, but I had to go through a lot to change hardcoded 'C:' directory strings

Still,  Drivers, utils, and third party folders are hardcoded to 'C:', so gmake fails. Where do I fix this????

Example: build qs_iot gives 14 errors, all of the type

gmake: *** No rule to make target `C:/ti/TivaWare_C_Series-2.1.0.12573/examples/boards/ek-tm4c1294xl/drivers/buttons.c', needed by `drivers/buttons.obj'. qs_iot Unknown C/C++ Problem

The files are of course on the G drive, not the C drive....

Ended up creating a symlink, solving the issue temporarily.

Even if I do find the error, I hate to fix all this up, and as a result, upgrades will mess it all up again.

Please advice how to fix this in a way that is supported with upgrades.

  • Hello Viking

    Normally I install everything on C: to avoid such issues. However if it need be changed then On right-click to the project, you can use Show Build Settings to go to the following menu to change the settings.

    Regards

    Amit

  • As described in original posting, after changing all settings with 'C:" in them, the issue is still not resolved. For example, the files in the projects are still hardcoded to be found on 'C:'. 

    Even before any build or make, the files listed shows up as missing from each and every project, so no BUILD setting will resolve this.

    TI, please record this as a defect in CCS or the package, and address in next release.

    Thanks

  • Make sure you do not have any non-English characters on the installation & project location. I had my windows username with a character that does not exist in English keyboard.

    Finally I had to create a new user with pure English letters.

  • Viking said:
    the files in the projects are still hardcoded to be found on 'C:'. 

    Now that's disturbing - one wonders if you've found/imported very old or improper source code?

    None of the includes w/in multiple of our current projects employ anything other than, "relative" references to the source files. 

    Agree with your dislike for having to "massage" each subsequent "source/library file update" - but I'd bet that there's some "missing hook" w/in your IDE which should be able to resolve/manage...

    @Caner - yours is a very neat point - we had just that issue w/one of our overseas interns - thanks for advising...

  • Viking said:
    The files are of course on the G drive, not the C drive....

     Hi Viking, I am Linux user so finally I am proudly using CCS on this platform.

     When I started evaluating CCS at early revision 5, Linux version was unstable and pretty unusable, so I checked the windows version... More and more worst. That time I stopped using and temporary licence voided.

     Now revision 6.0 is more usable but this wasn't a pain free installation, if you search on CCS dedicated forum a very long thread exists on how to solve troubles and get it installed, if you are still reading ok your version is Windows ;)

     In Linux I get C:\ errors too and this is a non sense, this is signalled and very bad programming practice common to most unskilled windows programmers...

     The worst things continue, I abandoned temporary usage of windows version due to the errors are you experiencing:

     If CCS installation and project drives are not the same CCS fails! My project is on a secure backed up external fast storage and I NEVER wish reside on a pc hdd nor windows hosted. So mapping an external drive render impossible to build under windoze...

     I stop there and believe me list is very long, before to do ping pong beta testing CCS 6.0 I wasn't GURU level but I raised in a short time  ;)

  • Caner Cuhac said:
    Make sure you do not have any non-English characters on the installation & project location. I had my windows username with a character that does not exist in English keyboard

     Hi, Also take great care about special letter and symbol on english keyboard too ;)

     This is a windoze bug than CCS, if you use "&" character on a folder, on some release of NT series and close descendant parent you can also lose all your files on subfolders and if you are particularly unfortunate all HDD content....

     Ask M$ to solve, is present from NT rev 4.0 like the Floppy not readable bug.....

     We own a super mainframe on the wrist clock but Technology appear as stop, Software & Hardware nowaday are no more reliable than it was in the 60-80.....

  • Is there any way to actually report a defect in CCS, and get a response that it was entered in the defect database. I dont even care to get a promise that anything will be done. Just a response that someone is listening.

    Thanks

  • Hello Viking

    For logging a defect go to CCS Forum Link

    http://e2e.ti.com/support/development_tools/code_composer_studio/f/81.aspx

    On the left side of the page is a Resource Section where you can see Bug Tracking

    Regards

    Amit

  • Viking said:

    Just a response that someone is listening.

     Hi Viking, all bug are submitted, your are known but still work in progress. Maybe next release address a lot of them and remove some annoying error when you copy a project from one partition ( or just directory on Linux) to another.

     CCS Forum has some great developer, so  please post some request helping not to remove software simulator too.

     P.S: Amit addressed a lot of your issue, marking yourself for answered is not so fine. ;)

     

  • Roberto Romano said:
    marking yourself for answered is not so fine. ;)

    Here, here!   And - pardon but what is being Verified?  Poster asks a fair question - but there's no hint of any answer!

    Poster's point/thrust is very valid - but marking it as, "Verified Answer" is just wrong!