• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 53 subscribers
  • Views 1164 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/MSP-EXP432P401R: CCSv7 project will not stop Build Automatically

Lunatic911
Intellectual 820 points

Part Number: MSP-EXP432P401R

Tool/software: Code Composer Studio

Hi All,

I'm starting a new project with Code Composer 7 and I'm finding my code is constantly building after I stop typing. I want to stop this, and I went to un-check the box for Build Automatically in the Project drop-down in the toolbar. That didn't fix it, and I found another box that was checked in Window->Preferences->General->Workspace called "Build automatically" and I unchecked that, too. That didn't stop it either. I did a restart of the workspace and it didn't help either. 

Does anyone know what I might be missing?

Thanks,

  • 0
    TI__Guru**** 465431 points

    Hello

    Lunatic911 said:
    I'm starting a new project with Code Composer 7 and I'm finding my code is constantly building after I stop typing.


    It builds when you just "stop typing"? Or did you mean it build when you save the file? I've heard of the latter (if you enabled 'Project -> Build Automatically') but I have never the former

    ki

  • 0 in reply to Ki
    Intellectual 820 points
    I did mean "stop typing." Such as when I want to toggle P3.6, I stop typing at P3OUT ^= BIT6 without adding the semicolon and it starts to build and tells me there's a bunch of errors because i hadn't put in the semicolon yet.

    I'm going to start a new workspace and copy the contents into it and see if this is another "switch workspaces" error. Hopefully it is.

    Thanks,
  • 0 in reply to Lunatic911
    TI__Guru**** 465431 points
    Wow, ok... I've never heard of that issue before. Hopefully cleaning the workspace helps. Please let us know.

    Thanks
    ki
  • 0 in reply to Ki
    Intellectual 820 points

    Just to let you know, I did end up starting a new workspace and it did go away. I have no idea what happened, but that fixed it. Simple fix for a crazy thing.

    Thanks,

  • 0 in reply to Lunatic911
    TI__Guru**** 465431 points
    Thanks for the update. Sounds like it was corrupted cache data stored in the workspace. This tends to happen over time if you don't periodically clean out your workspace.