• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 98 subscribers
  • Views 388 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: CCS20.0.1.4 linking malfunction

ga jo
Prodigy 70 points

Part Number: CCSTUDIO

Tool/software:

Hello,

Since we migrated from CC12.5 to CCS20, we have two problems with the link of our projects.
The context:
We have a main project that points to 5 subprojects.
What we used to do:
We create a virtual folder in which we create 5 'folder to link' using a relative link:
${CCS_WORKSPACE_DIR}/subprojectsName.
Then we used to create source folders pointing to the 'folder to link', but it seems that this option is no longer available.

First problem:
The indexing of files does not seem to be done correctly, when we navigate with a control click to go to the instantiation of an element, the opened file is not the one of the relative link, but of the absolute and from this moment, no more links are made.
Which is very irritating to program.

Second problem:
We put submodule folders in 'exlude form build', the compilation works, but in the output window we have errors on unresolved links of files that are excluded.
Which complicates the debugging a lot, because we have a very large number of non-existent errors.

Since we migrated from CC12.5 to CCS20, we have two problems with the link of our projects.
The context:
We have a main project that points to 5 subprojects.
What we used to do:
We create a virtual folder in which we create 5 'folder to link' using a relative link:
${CCS_WORKSPACE_DIR}/subprojectsName.
Then we used to create source folders pointing to the 'folder to link', but it seems that this option is no longer available.

First problem:
The indexing of files does not seem to be done correctly, when we navigate with a control click to go to the instantiation of an element, the opened file is not the one of the relative link, but of the absolute and from this moment, no more links are made.
Which is very irritating to program.

Second problem:
We put submodule folders in 'exclude form build', the compilation works, but in the output window we have errors on unresolved links of files that are excluded.
Which complicates the debugging a lot, because we have a very large number of non-existent errors.

We did the same operation using 'Visual studio Code', the problems are not present

  • 0
    TI__Guru**** 485111 points

    Hello,

    ga jo said:
    First problem:
    The indexing of files does not seem to be done correctly, when we navigate with a control click to go to the instantiation of an element, the opened file is not the one of the relative link, but of the absolute and from this moment, no more links are made.
    Which is very irritating to program.

    Are these subfolders actual separate CCS projects? Does the main project have these as actual project dependencies?

    ga jo said:
    First problem:
    The indexing of files does not seem to be done correctly, when we navigate with a control click to go to the instantiation of an element, the opened file is not the one of the relative link, but of the absolute and from this moment, no more links are made.
    Which is very irritating to program.

    This should still be supported in CCS 20. Can you show me a screenshot of the project explorer on how this setup looks like in CCS Eclipse? Expand your virtual folder so that I can see the 5 subproject folders underneath and also expand one of the subfolders.

    ga jo said:
    First problem:
    The indexing of files does not seem to be done correctly, when we navigate with a control click to go to the instantiation of an element, the opened file is not the one of the relative link, but of the absolute and from this moment, no more links are made.
    Which is very irritating to program.

    Yes we do have several known issues with our clangd parser which we hope to address with 20.2.0 (mid-2025 release)

    ga jo said:
    Second problem:
    We put submodule folders in 'exclude form build', the compilation works, but in the output window we have errors on unresolved links of files that are excluded.
    Which complicates the debugging a lot, because we have a very large number of non-existent errors.

    I suspect the issue is the submodule project is associated with the error and it appears in the problems view even though the other project has context. The view should really should not show the errors unassociated with the current project

  • 0 in reply to Ki
    Prodigy 70 points

    Hello,
    To clarify the architecture, here is an image representing our architecture under Eclipse as well as an explanatory diagram

  • 0 in reply to Ki
    Prodigy 70 points
    Ki said:
    Are these subfolders actual separate CCS projects? Does the main project have these as actual project dependencies?

    These are not projects, just common file containers. I'm not sure what you mean by 'project dependency', but the project needs these files in order to compile.

    Ki said:
    Yes we do have several known issues with our clangd parser which we hope to address with 20.2.0 (mid-2025 release)

    We will look forward to it Slight smile

    Ki said:
    I suspect the issue is the submodule project is associated with the error and it appears in the problems view even though the other project has context. The view should really should not show the errors unassociated with the current project

    The submodule has no project. Linking and indexing of these files should only be done based on the inclusions made by the main project. In addition, problematic files are excluded from the build, see the image below:

    This kind of link error is neither present in Eclipse nor in visual studio code. Only in CCS20

  • 0 in reply to ga jo
    TI__Guru**** 485111 points
    ga jo said:
    I'm not sure what you mean by 'project dependency'

    Please see: https://software-dl.ti.com/ccs/esd/documents/users_guide_ccs/ccs_project-management.html#project-dependencies

    It doesn't look like this is the case for you.

    ga jo said:
    This kind of link error is neither present in Eclipse nor in visual studio code. Only in CCS20

    Can you provide a screenshot of the whole explorer view in CCS 20? I suspect that the folders for the submodules were added to the workspace root and the error persists because of that.

  • 0 in reply to Ki
    Prodigy 70 points
    Ki said:
    Can you provide a screenshot of the whole explorer view in CCS 20? I suspect that the folders for the submodules were added to the workspace root and the error persists because of that

    Yes, folders for the submodules seams to be added to the workspace :

    If we don't add them, we have the following problem :

  • +1 in reply to ga jo
    TI__Guru**** 485111 points

    I believe I know the issue. I filed a ticket for this issue. Tracking link: https://sir.ext.ti.com/jira/browse/EXT_EP-12188