• State Resolved
  • Locked Locked
  • Replies 10 replies
  • Subscribers 54 subscribers
  • Views 2179 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.

CCSv6 compile Problems window not in sync with build results

Eddie3909
Guru 10385 points
Other Parts Discussed in Thread: MSP430F5528

CCSv6.0.0.00190

I've build my project successfully as shown in the console window (its created a .out file), but the Problems window thinks the .out file was not built. I've checked to make sure the proper project is active in the project window.

But the problems window thinks there is an error

  • 0
    TI__Guru**** 463421 points

    When you do a build, does the problems view get cleared first? I'm curious if that is a left over message from a previous build (I've seen that happen from time to time where the view doesn't clear).

    I also see that CCS has detected an error in the Colorflow.cluster folder. Is there a particular file it is complaining about?

  • 0 in reply to Ki
    Guru 10385 points

    Hi Ki-Soo

    Ki-Soo Lee said:
    When you do a build, does the problems view get cleared first?

    Sorry Ki-Soo. I've re-started CCS and the problem window now reflects the fact there are no error, just warnings.

    Ki-Soo Lee said:
    I also see that CCS has detected an error in the Colorflow.cluster folder. Is there a particular file it is complaining about?

    All files compiled OK (as shown in the console window output of the first snapshot). I can't remember when I fixed the colorflow compile bug, but it was awhile ago.

    Thanks for your help

    Cheers

  • 0 in reply to Eddie3909
    Guru 10385 points

    Hi Ki-Soo

    Its just happened to me with a different project.

    Here's a theory on how this is happening. 

    1) Compile project that has an error. Error will show up in problems.

    2) Close project. 

    3) Open project

    4) fix error

    5) compile -> there will be no error on the console, but "problems" still has a problem, it shows the error at step 1).

    Closing and opening the problems window does not solve the problem. Hmmm, and closing and opening CCS didn't solve it either. Wow. Its just not updating period.

    Deleting the project and importing again solved the problem, well kinda - if you don't mind importing each time you want to update the problems window.

    Cheers

  • 0 in reply to Eddie3909
    TI__Guru**** 463421 points

    Thanks for the suggested test case. Unfortunately it did not reproduce the issue for me. The problems view gets cleared after the successful compiler.


    This issue is maddening to me because it has been reported various times with various versions of CCS but we've never been able to reproduce.

    Have you seen this with other projects? or just this one?

  • 0 in reply to Ki
    Prodigy 120 points

    Hi!


    I have upgraded to CCSv6 recently and have the same problem: after successful build, the problem window shows a lot of errors (hundreds). Easy to find out that some include files should be missing to have this result. Therefore I think the problem should reside somewhere in precompiled header/makefile generation/processing.

    Another point of view is that it would be nice to have a clear button/possibility for the Problems view. If I "clean" the project, the Problems window did not get clean. This is a clear bug.

    I have no reliable workaround found yet. Close/Open/Exit/Start does not solve the problem. Repeated clean/rebuild/change active build configuration solved the problem somehow. I think delete and reimport should be an acceptable solution.

    Best regards,

    Tamas

  • 0 in reply to Tamas Nagy
    Guru 10385 points

    Hi 

    Perhaps its directory structures?

    Mine is setup as

    c:\ti   -> CCS and build tools

    c:\Work\  -> several workspaces for different projects

    d:\vws\  -> Code  where each build has an App project that is dependent on a particular platform project.

    What is yours setup as Tamas?

    Cheers

  • 0 in reply to Eddie3909
    Guru 10385 points

    Hi Tamas

    My colleague showed me how he deals with it in CCSv5. He highlights the errors and then right clicks and selected delete. Wouldn't it be nice if you could fix the errors that way too?  :o)

    I can't check CCSv6 for the delete because I've uninstalled CCSv6. Because of several tools issues, the team lead decided we're sticking with CCSv5.5  :o(

    Cheers

  • 0 in reply to Eddie3909
    Prodigy 120 points

    Hi Eddie!


    Right click and delete on errors simply does work in CCSv6 :-)

    Thank you for this easy solution.

    Best regards,

    Tamas

    (I was simply stupid enough to forgot using context menu....)

  • 0 in reply to Tamas Nagy
    Guru 10385 points

    Hi Lisa TI

    I deleted your indication that this thread's issue has been answered because having to right click on the items in the Problems tab is not a solution. Its a work-around.

    Cheers
    Eddie

  • 0 in reply to Eddie3909
    Prodigy 120 points

    Dear All!

    I know a little bit more about this issue. It is definitely a BUG in CCS/Eclipse near to the preprocessing of include files. It is not able to follow the preprocessor directives (#ifdef ... etc.).

    New issue: using MSPGCC causes the same symptom:

    After compilation the OUT file has been successully built but the Problem window is full with errors.

    1st workaround:

    clear the Problem windows's content. Occassionally works, but after compilation problems could come back.

    2nd workaround:

    include the standard header of the actual MCU (ex.: #include <msp430f5528.h>)
    AND
    clear the Problem windows's content. In this case the errors are finally eliminated.

    Happy coding!

    Tamás Nagy