• Locked Locked
  • Replies 5 replies
  • Subscribers 52 subscribers
  • Views 1686 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 and external Tools

Hatem
Expert 1685 points

I have inherited a project based on a makefile.

I can build the project OK, but the parser doesn't resolve all header files, in all source files.

I assume this is because CCS has now no knowledge of the include files paths, as the project is makefile based.

Do I need to define all the include paths in the project properties of CCS to resolve this issue

(this way changing the make file  may require changes in the project properties)

or is there a short cut to make the parser aware of all the include paths of such project?

I have noticed this impacts the debug mode: some source files doesn't recognize break points 

  • TI__Guru**** 173310 points

    Hatem said:
    I have inherited a project based on a makefile.

    So it is not a CCS project, but a makefile project with your own custom makefile, correct? Are you using TI build tools or GCC tools?

    Hatem said:
    but the parser doesn't resolve all header files, in all source files.

    Can you explain what you mean by parser does not resolve all header files? Do you mean that when you try to "open declaration", for example, it does not automatically take you to the declaration in the header file?

    For GCC build tools, you may need to add the header file paths under Project Properties->C/C++ General->Paths and Symbols->Includes tab, but I don't think this is required for TI build tools.

  • in reply to AartiG
    Expert 1685 points

    Hi

    Thanks for the reply.

    Yes our own custom makefile. we use GCC tools (Arm compiler and some TI tools like BIOS etc.

    The project build fine with no erros.  but the source files show bugs near some include files and near functions from those include files.

    Also if I try to "Open Declaration" it does not open the include file.I do not have Includes tab under Project Properties->C/C++ General->Paths and Symbols

  • in reply to Hatem
    TI__Guru**** 173310 points

    Hatem said:
    I do not have Includes tab under Project Properties->C/C++ General->Paths and Symbols

    I noticed that the existence (or not) of the Includes tab depends on which build tools are selected during project creation. For example, for the TI build tools, I do not see the tab, but for Cross GCC or some other GCC toolchain, I do see it. So I suspect this may be dependent on the way your project was created.

    If you go into Project Properties->C/C++ Build->Tool Chain Editor, what do you see there for "Current Toolchain"? With Toolchain as Cross GCC, I do see the Includes tab.

  • in reply to AartiG
    Expert 1685 points

    This is what I have.

    I did not create the project. I inhereted the project from someone who left the company.

    in the makefile I have:

    GNU_Tools_ARM

    bios_6_37_01_24

  • in reply to Hatem
    TI__Guru**** 173310 points

    If I select the toolchain as "TI Build Tools", I also do not see the Includes tab. But in that case, my assumption is that CCS already knows how to index the files, so it is not necessary to specify the include paths explicitly. I may be wrong though as I do not work with custom makefile projects much. 

    You could try rebuilding the index to see if that helps.

    Also, since this is really an Eclipse feature and not CCS specific, you could try searching or posting to other Eclipse forums to see if others in the community who use Makefile projects have additional comments. Sorry for not having a better answer!