Because of the Thanksgiving holiday in the U.S., TI E2E™ design support forum responses may be delayed the week of November 23.

CCSTUDIO-THEIA: CCSTUDIO-THEIA: How to add include paths

Part Number: CCSTUDIO-THEIA

I am currently using CCS Version: 21.0.1.10__1.12.1.
I am using an external library (WIZnet).
I don't understand how to specify the additional include path for it.
I do know that I need to add it via this screen, though.

For a single source file (e.g, main.c), I can add it by selecting the filename and right-clicking to select [Properties...].
However, I don't know of a reliable way to add this to all source files (*.c).

A related issue is that include specifications do not take effect when the "-Iquote" option is used.
The build log showed the string "-Iquote xxxx", but it was not enabled (specified with double quotes "").
Specifying with "-I" is valid.

Best regrads.

 

  • Kato-san,

    I am using an external library (WIZnet).
    I don't understand how to specify the additional include path for it.

    I assume you are looking to add an include search path to the header files associated with the external library,correct?

    For a single source file (e.g, main.c), I can add it by selecting the filename and right-clicking to select [Properties...].
    However, I don't know of a reliable way to add this to all source files (*.c).

    If you wish to apply it to all files in the project, add the include search path to the project level properties, not per source.

    Right-click on the project and select the Properties option in the context menu. This is the way you can access the properties for the entire project:

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

    Any settings applied here should apply for the entire project. But note that if you set an option specifically at the file level, those settings will override the ones at the project level.

    A related issue is that include specifications do not take effect when the "-Iquote" option is used.
    The build log showed the string "-Iquote xxxx", but it was not enabled (specified with double quotes "").
    Specifying with "-I" is valid.

    For your use case I would recommend using -l.

    Thank you

    ki

  • > Right-click on the project and select the Properties option in the context menu.
    Until now, the property select options were not displayed.

    By moving up one level from the folder opened in CCS, it has become possible to select properties.
    (Understanding the issues with how projects are handled in CCS. --> To another question)
    I understand that the issue with the "-Iquote" option is a compiler issue.
    (In what situations would I use it?)

    Thank you for your support.

    Kato T.

  • By moving up one level from the folder opened in CCS, it has become possible to select properties.

    It sounds like you selected the project folder as the workspace folder when using the "Open Folder" option. Is this the case? 

    Thanks

    ki

  • I think it is correct.
    I think that the understanding of projects and workspaces is insufficient.

    Thanks,
    Kato T.

  • I think it is correct.

    That scenario is not supported. The issue is that the project must be imported to a workspace to be recognized as an official CCS project (an official CCS project will have a little cube in the folder icon). Specifying the project folder when opening a new workspace folder does not import the project and hence not recognized as a CCS project). However, opening the parent folder as the workspace folder is find since CCS will scan for CCS projects inside that parent folder and auto-import it (which is why moving up one level worked).

    I understand that the issue with the "-Iquote" option is a compiler issue.
    (In what situations would I use it?)

    Actually while basic -I is simpler (since it will apply to all header files), -Iquote can be more effective (safer) in some ways and should not be easily discounted like I initially mentioned.

    -Iquote will only apply to header files included while wrapped in quotes. For example, the below would apply:

    #include "types.h"

    while the below does not:

    #include <types.h>

    So it gives you an extra level of control.

  • I understand the relationship between projects and workspaces. (I will review it.)

    > -Iquote will only apply to header files included while wrapped in quotes. For example, the below would apply:
    > #include "types.h"

    This format was no effect. (Specifying with "-I" is valid.)

    Best regards,
    Kato T.