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 builds unnecessary files

Other Parts Discussed in Thread: SYSBIOS, CCSTUDIO

Hi,

I'm using CCS 6.1 on Ubuntu 14.04.

When I go to build, there are files that always get built even though they don't need to be.  I can build everything, then do another build and there are always several files that get built again.

I had the same problem with CCS 5.4 on Ubuntu 12.04 and 14.04.

Thanks,

Mike

  • Mike,

    Are you seeing this happen with dependent projects? If so, I recently filed the bug number SDSCM00052017 (check its status in my signature SDOWP below)

    If it is in the same project (or a SYSBIOS project) it's been a while since I have seen this (perhaps since CCSv5.4 days), therefore would you mind testing building the same project in a fresh workspace? Or perhaps issuing ccstudio -clean to see if this behavior goes away?

    Regards,
    Rafael
  • I have libraries in my project that the application depends on, but my symptoms are not the same.  Here are the steps I take:

    1) Build project; everything seems to build as requires where changes were made, except some files in the main application are compiled that have not changed.

    2) Rebuild project; libraries are checked, but nothing is rebuilt as expected.  But files in the main applications are recompiled, though no changes were made.

    3) Rebuild project; no files have changed.  Same thing.  Libraries are checked, but not rebuilt.  Files in main project are rebuilt, even though no changes were made.

    4) Repeat 3 indefinitely

    My project is not a SYSBIOS project

    Thanks,

    Mike

  • Mike,

    I was discussing this internally and we just had another idea: are you using version control? In the past Clearcase was guilty of constantly syncing source files and the .project, .ccsproject, .cproject files when using dynamic views.

    Another thing we faced in the past was a setup where source files were in networked servers and a timestamp difference between them and the .obj files on the local machine would cause gmake to pick those up for rebuild.

    wikipedia said:

    (extracted from: en.wikipedia.org/.../Make_%28software%29)

    Conversely, if a source file's modification time is in the future, it triggers unnecessary rebuilding, which may inconvenience users.


    BTW, did you try the suggestions about workspace change and -clean? If all else fails, these tend to be proven handy to overcome similar undesirable scenarios.

    Hope this helps,
    Rafael
  • Hi,

    Version control is Mecurial.  

    Not building from a network.

    Have in the past started with a fresh repository.

    Have cleaned all libs and main app, doesn't help.

    Mike