• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 53 subscribers
  • Views 1136 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/TMS570LC4357: Code Composer build error

Adrian Timis
Intellectual 291 points

Part Number: TMS570LC4357

Tool/software: Code Composer Studio

Hello,

I am trying to create a project where I am integrating the Google protocol buffers into the TMS570LC4357 board. The purpose of this is to send some data over UDP using the lwIP library.

I have included the C++ files generated by the Google protobuf library into the project, which is the lwIP demo code, and after providing the rest of the include paths for the project I still get a weird error. As far as I can tell, it's something to do with the ios and iostream files. The error I get is the following one :

I cannot find any relevant information regarding this Error 2. The path specified in the brackets is a path to the ios file.

I was thinking that maybe I need to set something in the project properties, since I am using some C++ files now as well, though I have not been able to detect the problem at the moment.

Any help regarding this issue is greatly appreciated,

Thank you.

  • 0
    Intellectual 291 points

    This is the error that I am getting, The picture was not posted in the initial post.

  • 0
    Intellectual 291 points

    More helpful I think is this information shown in console when trying to run the project :

    I have tried to run a g++ command in the windows command prompt, and it says that g++ is not recognized as the name of a cmdlet, function, script file or operable program. I would assume that correctly installing g++ and being able to use it from the command prompt will solve the issue, however, I have the impression that there must be a different way of solving this issue.

  • 0 in reply to Adrian Timis
    TI__Guru**** 173310 points

    Is this project meant to build with the TI compiler tools or GCC? I see that there is a reference to both tools in the command.

    g++ is the GCC executable (so it is invoking the GCC tools) but the path to the source file ios.cpp is within the TI compiler's library sources. Was this source file intentionally added to the project?

  • 0 in reply to AartiG
    Intellectual 291 points

    I wanted to build this project with the TI compiler tools, however it was not doing that. The source file was added because of the files generated by Google's Protocol Buffers. I changed the include path for that, and managed to get rid of that error. But despite that, now I am having issues with other files that Google's Protocol Buffer requires, the sys/param.h, which as far as I can tell, has some information regarding the endianess of the system, but I cannot find this file anywhere. So now I am trying to avoid this issue by either altering the code generated by the Google protoc compiler, or by defining some variables which will make the system behave as it should.

    Just for reference, this is the error that I am currently on :

  • 0 in reply to Adrian Timis
    TI__Guru**** 173310 points

    Based on the message, it looks like port.h has a #include for "sys/param.h", so I would imagine that param.h would also be part of the Google Protocol Buffer files. However I am not familiar enough with that code to tell for sure.

    You are on the right path though and the "cannot open source file" type of errors are typically due to missing compiler include paths. 

  • 0 in reply to AartiG
    Intellectual 291 points
    It seems that the sys/param.h file is not part of the Google Protocol Buffers, nevertheless, it would have been too much of a hassle to change everything in order for that to work.

    If anybody else wants to implement Google's Protocol Buffers into an embedded platform, I recommend using Nanopb, github.com/.../nanopb , a plugin for the Google Protocol Buffer. I personally ran into no issues integrating this, compared to the C++ implementation of the Google Protocol Buffer, which was much more trickier than expected.

    Nevertheless, thank you AartiG for the time taken to help me solve this issue.