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.

CCSv5 Version: 5.2.1.00018 add -k to build command with command line create

Other Parts Discussed in Thread: CCSTUDIO

It looks like very old bug has been re-introduced into CCSv5. When I import project using command line CCS add -k to build command. Any attempt to remove -k using CCS project properties is unsuccessful. It comes back next time. Below is the command that I used to create CCS projects:

-ccs.name Project
-ccs.device com.ti.ccstudio.deviceModel.TMS470.GenericCortexR4Device
-ccs.autoGenerateMakefiles false
-ccs.outputFormat ELF
-ccs.endianness be32
-ccs.cgtVersion 4.9.1
-ccs.rts <none>
-ccs.buildCommandFlags ""
-ccs.outputType executable
-ccs.configurations Build
-ccs.overwrite keep
-ccs.buildLocation "C:\Projects\Project"
-ccs.buildCommand "C:\Projects\Project\Project_build.bat"
-ccs.buildTarget ""
-ccs.cleanTarget "cleanall"

  • Hi Eugene,

    Sorry about the delayed reply. This post seems to have fallen through the cracks.

    Could you please provide a few more details to help us reproduce the issue? So you create a project using the above provided command line? Then how do you add the -k build option and how do you try removing it?

    In the above command line, is C:\Projects the name of your workspace?

    Was this a previously reported or known issue?

  • Aarti,

    I do not add -k option. It is added by CCS when I create project using command line. I remove it by opening project properties. It is under build settings for build command. BTW, this dialog behavior is strange. I just noticed that with any update made by me Apply completely changes the structure of presented options. This is for projects created using command line.

    No, my projects are in arbitrary locations.

    Yes, this was an issue in the first releases of Eclipse based CCS few years ago. Not sure if it was reported on E2E, through FAE or directly to CCS support. It since has been fixed but now it is back.

    Eugene

  • Eugene,

    I can't seem to reproduce this with CCS 5.2.1.00018. I created a command line project using almost all of the options you listed above (did not specify -ccs.buildLocation, -ccs.buildCommand and a couple of others) but didn't see the -k option automatically added. Can you send the Project_build.bat file. Not sure if that would make a difference or not, but at least I could try reproducing with it.