• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 54 subscribers
  • Views 676 views
  • Users 0 members are here
Support feedback
Options
Options

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.

Disable clean-only build in CCS

Marco Burgener
Prodigy 30 points
Other Parts Discussed in Thread: MSP430FR5994

Dear all,

I'm using CCS version 11.2 to develop code for the MSP430FR5994. I'm using different build targets which are calling a self-made build script. Under project properties/Build/Builder I modified the Build command to be "bash ${ProjDirPath}/scripts/build.sh", where the build.sh is a self-made script which is also used by the a build server for automatic building and continuous integration. This script supports different commands, like "build.sh clean", "build.sh cmake", "build.sh application" and several others, where each command executes a specific task only. So the clean command obviously cleans the project output folder by just deleting everything. The cmake command generates all the makefiles using CMake and a CmakeLists.txt. The application command then builds the application using the generated makefiles. So far so good.

Then I created some "Build Targets" within CCS. They appear in the project explorer and can be used to build different targets, namely to run the script with the specific commands like cmake or application. But when I run one of those build targets CCS automatically runs the clean command first for each build target and I don't know why. So when I run the application build target, everything gets deleted just before including the generated makefiles that I created previously using the cmake command end the application can't be built. The console output would look like this:

**** Clean-only build of configuration Debug for project Prj ****

bash D:/Projects/Prj /SW/Prj/scripts/build.sh clean
 
Script path: /cygdrive/d/Projects/Prj/SW/Prj/scripts
==== Project path: /cygdrive/d/Projects/Prj/SW/Prj
 
==== Building Project - Server; Wed Sep 28 13:16:17 WEDT 2022 =======================================
 
==== Cleaning up and delete /cygdrive/d/Projects/Prj/SW/Prj/build/Debug/test
 
==== Cleaning up and delete /cygdrive/d/Projects/Prj/SW/Prj/build/Debug/main/DevKit
 
==== Cleaning up /cygdrive/d/Projects/Prj/SW/Prj/reports
 

**** Build Finished ****

**** Build of configuration Debug for project Prj ****

bash D:/Projects/Prj/SW/Prj/scripts/build.sh application

I want CCS to only call the second command line "bash D:/Projects/Prj /SW/Prj/scripts/build.sh application", but it automatically runs the first line "bash D:/Projects/Prj /SW//Prj/scripts/build.sh clean" as well and everything gets erased just before the build starts. Then there is an error because there are no makefiles. Is there a way to disable this? Why does CCS do that?

Thanks and best regards,

Marco

  • 0
    Guru 92251 points

    I haven't tried to re-create your issue, but found How to prevent systematic cleans before builds? which might be related. The referenced message from Amenel Voglozin mentions there is a "Refresh Policy" which might help to avoid the issue. 

  • 0
    TI__Guru**** 450031 points
    Marco Burgener said:
    I want CCS to only call the second command line "bash D:/Projects/Prj /SW/Prj/scripts/build.sh application", but it automatically runs the first line "bash D:/Projects/Prj /SW//Prj/scripts/build.sh clean" as well and everything gets erased just before the build starts. Then there is an error because there are no makefiles. Is there a way to disable this? Why does CCS do that?

    This project build behavior is something inherited from Eclispe CDT. Please refer to the thread Chester referenced above to see if it works for your case.

    ki