• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Subscribers 56 subscribers
  • Views 2956 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.

"ERROR: no source files, nothing to do"

Flamingo
Expert 2290 points

I completed my CCS3.3 project build for "Debug", and just changed my configuration to "Release". I would like to build it to make sure that I've got the build flags correct. When I do a Build Clean followed by a Build, each .c file compile line is followed by "ERROR: no source files, nothing to do".

This is new. The Release builds of other projects do not show this same symptom. When I switch back to Debug, the build works.

What might be wrong that would cause these errors? (Note that each .c file has one of the error messages, so it does know about the .c files.)

  • 0
    TI__Mastermind 24340 points

    Can you send you .pjt file? You can attach it to your profile so I can get it...

  • 0 in reply to Mariana
    Expert 2290 points

    It is no longer necessary. I figured it out. There was a trailing quote at the end of the build flags.

  • 0 in reply to Flamingo
    TI__Mastermind 24340 points

    Glad to hear that!

  • 0 in reply to Mariana
    Intellectual 310 points

    Could someone explain what the *(&^ is going on here? I ran into exactly the same problem with CCS 4.2.0. It appears to have self-resolved by multiple rebuilds, clearly demonstrating again that CCS is simply a non-determinisitic MESS.

  • 0
    Prodigy 20 points

    I use CCS for the first time ,and there is a mistake  just like yours.  (Note that each .c file has one of the error messages, so it does know about the .c files.)   could you tell me how to solve it ?

  • 0 in reply to ze zhang
    Intellectual 310 points

    CCS is not deterministic; if you try to do the same thing several times, the results may be DIFFERENT each time. The problem is likely to be something related to Java threads out of sync, but is not something you can fix - and TI is unlikely to fix it either.

    Try doing a COMPLETE clean and rebuild of the project (sorry, I do not have CCS on this computer, so I cannot describe the exact menu steps required). If that does not help, try closing and restarting CCS.

    I have found that the only way to keep track of CCS errors - and specific CCS commands - is to use screen captures to document them, and give the capture files names that help you to find them for future reference.

    I have posted a number of capture files here on e2e, but I don't think TI has ever resolved any of the problems. The problems just come and go, because of the unstable behavior of CCS.

     

    Steve

     

  • 0 in reply to Steve Kranish
    Expert 2290 points

    As I said in my post, my problem was that there was a trailing quote in the build flags. I went to the editable text block for the build parameters and repaired the string. The tool seems to move the -D parameters around, leaving some with one quote or quotes in the wrong place. It is not tolerant of moving the focus from one window to another during the edit process. One thing to try is to cut and paste the string into an editor and "fix" it there and then copy and paste it back into the editable text block.

  • 0 in reply to Flamingo
    TI__Genius 15660 points

    Hi Steve, 

    There seem to be duplicate posts related to this issue, see my response to the other post 

    http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/105826/373024.aspx#373024

    4.2.2 has quite a few fixes related to unnecessary re-builds of projects. Also,  I know of one issue where building a project would fail when it was imported for the first time. It would succeed when an explicit clean was done first and then a build. 

    Martin