Entering Debug mode rebuilds all projects

Hi David,

yes you should be able to rebuild a single project.  CCS actually should really only rebuild on changes.

What OS and CCS version and target are you using?   What exactly are you attempting and experiencing?

Have you tried from the Project menu?  You should see options like Build Project, Build All, Clean etc which might help save some build steps.

Best Regards,
Lisa

Hi Lisa, 

I usually right-click the project and select "Build Project" which builds it fine. Sometimes it rebuilds the selected project and libraries listed as dependencies. When I press Debug button however it rebuilds everything again no matter if there was a change or not or if I already used "Build Project". I have CCS 5.2.1.00018 running on Windows 7 Professional.

Could it be related to the fact that "Problems" window still shows errors from a previous failed build and even after cleaning the projects they are still not deleted and not even manually cannot be deleted? Can we disable that window since I only use the console output anyway?

Best regards,

David.

Hi David,

I have not heard of this.  The debug button should build (if necessary) the active (highlighted) project and load the target.   Are you simply pressing the debug button?  Can you send a screenshot or something so that we can see and try to reproduce the behaviour?

Best Regards,
Lisa

Hi Lisa, 

It is all I'm doing, right-click, Build Project, press Debug button and still rebuilds. What should I capture in the screenshot?

I attached the project files, maybe you can spot something.2086.ccs.zip

Best regards,

David.

Hi David,

so which is correct

- is the project being rebuild every time, or do you realy believe all projects are? Can you send anything that shows exactly what you are experiencing?  There is a big difference in these two cases.

- can you zip and send (even if ofline through a friend or conversation request) the actual project?

Best Regards,

Lisa

in CCS 4.1.3 When the CCS is not normally shut down , it will rebuild the project and any related project the next time , no matter what action you choose(debug, build ,rebuild all...).

but  i have heard that it is not the story  in CCS5 any more, I was wondering if one of your CCS configuration file is changed.

I think it rebuilds every time when there are errors listed in Problems windows, after a few days of using CCS those errors cannot be deleted even after clean or manually delete. Had to create another workspace. Haven't seen a consistent behavior but it happens and it's annoying as another 2-3 minutes are wasted for rebuild.

Hi David,

would you be able to send the project/test case to us offline?  Have you tried clearing the metadata?

Best Regards,
Lisa

Hi Lisa, 

Unfortunately I cannot send the project, but I did attach in a previous post on this thread the project settings file. I assume removing .metadata folder in workspace?

Best regards,

David.

Hi David,

this is likely going to be exteremely difficult to track if we are unable to reproduce it.  Even a stripped down test case offline would help. 

But yes, please try removing the .metadata folder.  It sounds like you have tried recreating the project so to speak?

Best Regards,
Lisa

Hi Lisa, 

So the problem is repeatable, but takes a while. I build the project, start debug session. After loading firmware, making changes to source code and building, the environment detects when .out file has been changed and asks to reload it. But in the mean time if there were any compiler errors, they add up in the Problems window. Next day when I restart CCS and debugging session, if the problems couldn't be deleted (even if project was successfully built a day before), rebuilds everything successfully and I'm still being asked "Errors exist in required project(s). Proceed with launch?". That's why I was asking if there's a way to disable the "Problems" window, I don't need it since I use console output. Deleting .metadata fixed the rebuilding and errors are now gone in Problems window, so I'll do this every day and import preferences from now on.

Best regards,

David.

Hi David,

ok, thanks for your patience and for the update.  Glad at least we got you a work around.

All the best with development.

Best Regards,
Lisa

Hello,

Anyone else seen this behaviour? I've upgraded to CCSv5.3 and now CCSv5.4 and still rebuilds dependent libraries every time I press Debug buton and it's very slow and annoying development process. I deleted workspace, no problems reported in Problems window.

Best regards,

David.

Actually, yes, I see the same behavior. I have a workspace with some 20 projects in it. One of those is the main project, the others are dependencies. Now regardless whether or not the main projects is already built, every time I click Run->Debug, CCS runs a build step (which does not really recompile anything, but it calls make for each dependency, and that alone takes a while). This is really annoying if you want to say power off your device and restart debugging.

I also see the same behavior. Is there a way to just turn off building before debugging like there is in vanilla Eclipse? I'd rather just manually build if I want to update the binary because having the editor decide eats up 2-3 minutes between debug sessions, which today has added up to probably an hour or two of dead time.

I'm having the same problem as are many others. Deleting the .metadata for every build and re-importing every project is not a viable solution. At best that is a painful work-around. Please fix the bug. If a test case is needed, just use one of the many TivaWare samples.

It is unbelievable this issue still hasn't been resolved.

We have 3 major products in development (2 DSP, 1 Tiva) and this issue is stealing a big part of the day from all developers in our shop.

Hi Paulo,

I've seen the same issue but a workaround is pretty simple. Right click on each project, "Properties", "Build" then uncheck the "Generate Makefiles automatically". This prevents that project from generating new Makefiles and rebuilding the whole project every time you launch debugging. Has worked well for me and speeds-up launching debug.