• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 98 subscribers
  • Views 302 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.

CCSTUDIO: CCS 20 - Cannot open file from Linked Resource with CTRL+P

1768011
Intellectual 600 points
Part Number: CCSTUDIO

Tool/software:

we've come a long way from before CCS 3.3. Now we want to migrate from CCS 10/12 to CCS 20.
We used some specialities of eclipse projects to get our workflow done.

In this particular case: we use linked resources to include the complete sourcecode into the ccs project.
The drawback in CCS20: Files cannot be opened via "CTRL+P", which is a mayor flaw.
The reason is, we have several eclipse based IDEs that operate on the same sourcecode, e.g. CCS, ARM DS-5, Altera/Intel NIOS EDS, Infineon DAVE et.al.
Therefore the project root canntot be the root of the sourcecode.
Consider this layout

dir/conf/ccs_project
dir/conf/armds5_project
dir/conf/dave_project
dir/src/

ccs_project is where the project lives. "dir/src" is embeded as external source.
To reprouce in CCS20:

  • Open Project Properties (ALT-ENTER) and go to "General->Valiables"
  • Hit + to add a variable
    • Name SRC_LOC
    • Type Path
    • Value ${PROJECT_LOC}/../../src
  • Open "Add Files/Folders..." from the context menu of the Project folder in Explorer->Workspace and hit "+" on the next dialog
    • Choose "Select fodlers to link"
    • Choose "SRC_LOC" from the dropdown below
    • Add "SRC_LOC" or similar to "Name"
  • Hit "ctrl+p" an type the name of a file that is in "dir/src/" and notice that nothing will shop up.


It would be nice to get this fixed in the next version of CCS.

If there's a new better way of managing several eclipse/CCS theia based projects for one source tree i'm happy to hear!

  • +1
    TI__Guru**** 465171 points

    Hello,

    1768011 said:
    In this particular case: we use linked resources to include the complete sourcecode into the ccs project.

    We have many known issues with the clangd parser and our projects. Many of them are related to linked files.

    We hope to address many of them with in our CCS 20.2.0 release scheduled for end of May.

    Thanks

    ki 

  • 0 in reply to Ki
    Intellectual 600 points

    Hello Ki!

    Thanks for your reply. I certainly see, that there is also a correlation with clangd, since searching for symbols with in the source code in a linked resource does not work as well.

    But searching for a file name in a linked resource should not be related clangd?

    Therefore two followup questions:

    - is the bugtracker still open to the public? then i could go through the issues to see if 20.2 will cover my problem

    - are there beta builds for 20.2? I'd be happy to test.

    Thanks

    Brian

  • 0 in reply to 1768011
    TI__Guru**** 465171 points
    1768011 said:
    But searching for a file name in a linked resource should not be related clangd?

    Not directly. But it is in the same category of CCS failure to properly account for linked files. It is on the list of things to address for 20.2.0

    There is a crude workaround: https://www.youtube.com/watch?v=DCpBYit84dc&list=PL3NIKJ0FKtw75d_K8G0JBJHB9zIm8_YQL&index=6

    1768011 said:
    - is the bugtracker still open to the public? then i could go through the issues to see if 20.2 will cover my problem

    It typically is. But we are having some backend issue that are preventing some of the more recent ones from going public. Hopefully that gets resolved soon but it has been down for some time.

    1768011 said:
    - are there beta builds for 20.2? I'd be happy to test.

    20.1.0 has yet to be released (scheduled for the end of this month) so it will be awhile before a 20.2.0 beta build is available.

    Thanks

    ki