• State TI Thinks Resolved
  • Locked Locked
  • Replies 7 replies
  • Answers 1 answer
  • Subscribers 54 subscribers
  • Views 2175 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.

CCS: CCS V7: Build Artifact tab always has the default path.

Jeevarathnam Kuppusamy
Intellectual 692 points


Tool/software: Code Composer Studio

Hi,

I have recently updated my CCS to V7. And I have the below issue

This is Jacinto-6 project.

The Build Artifact tab always has the default value {ProjName} and I need to change it every time before building the project. or Manyally I have to copy paste the generated lib file.

where as in my ccs project(created in ccs V6) it is 

<configuration artifactExtension="lib" artifactName="${SRC_ROOT}../../../../public/lib/DRX7XX_SYSBIOS-RELEASE/HAF" 

SRC_ROOT is set to project path. And I have 2 project 1 Jacinto-5 project which doesn't have any issue. the lib is generated in the specified path.

Is this the CCS issue or Eclipse issue?

Regards,

Jeeva

  • 0
    TI__Guru**** 467591 points
    Hi Jeeva,
    It should preserve any changes you make there. I tried this with CCSv7.4 and it remember an updates I make to that field. What is the string you are specifying in that field?

    Thanks
    ki
  • 0 in reply to Ki
    Intellectual 692 points

    Hi Ki,

    the project was created in CCS 6. And its read only file. And when I open the project in CCS 7.3.0, it pops-up a warning that the project is read only do you want to make it writable, I clicked no. And just check out the file and see the differences. The file has many changes. How does this is happening? if I don't checkout I can't see these changes but it has internally. Because I can do any modification in CCS without checking out the project file.   And I don't want to check-in the project file. Since it has lots of changes.

    So it was working in CCS V6.

    The string used is  ${SRC_ROOT}../../../../public/lib/DRX7XX_SYSBIOS-RELEASE/HAF. Some how the  artifactName is getting changed.

    after opening the project in CCS if I checkout the project and diff it

    I see

    artifactName="${ProjName}"

    Is this something CCS6 and CCS7 compatibility? I dont think, since Jacinto-5 project works fine from CCS 6 to 7.

    Regards,

    Jeeva

  • 0
    Intellectual 692 points

    This is the warning message I was talking about. I clicked no, so I think its creating local copy. seems its always trying to write the project.

  • 0 in reply to Jeevarathnam Kuppusamy
    TI__Guru**** 467591 points
    I can't seem to reproduce this with my projects. Would it be possible to provide the .*project files in the project folder? I don't need the actual source files, just the *.project files (.project, .cproject, .ccsproject).

    Thanks
    ki
  • 0 in reply to Ki
    Intellectual 692 points

    HI Ki,

    Please find the attached both project content.

    J5 -> no issue

    J6 -> has issue

    j6.zipj5.zip

  • 0 in reply to Jeevarathnam Kuppusamy
    TI__Guru**** 467591 points
    Thank you. I had sent these to the engineering team for analysis.

    Note that the office is closed for a few days due to the holiday season here so it will be a bit of time before we have a response.

    Thank you for your patience
    ki
  • 0 in reply to Ki
    TI__Guru**** 467591 points
    Hello,
    Sorry for the delay. I discussed this with the engineering team. As per the team:

    The popup asking to make the file writeable – that is expected. That particular project requires migration, and CCS must be able to write the migration changes back. Click OK to make the files writeable, and allow the migration to proceed. Then check the changes back into source control. After that, the projects would only work in CCS v7, and not in CCS v6.

    But, the change in the “output file” field – that is a bug in CCS. Work around it by just manually changing that field back to the original value (after allowing the project migration to proceed as mentioned above, and before storing the changes back into source control).

    A bug has been filed for the issue for the change in build artifact setting change. ID: CCSIDE-3245

    Thanks
    ki