• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 52 subscribers
  • Views 496 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Finding multiple definitions with CCSv4

Gary Lynch
Expert 1310 points

This ought to be pretty straightforward. My build invokes a
bunch of error messages in the "Problems" window.  The first
one is:
  "CSM_PWL" has already been declared in the current scope

If I double-click on the message, it pulls up a line in a
header file where the struct CSM_PWL is declared. Logically,
the header is probably #included inside some .c file and
there may be another #include higher up that declares the
same struct. So ...

1.  Is there any way to get CCS to tell me which .c file it
    was compiling when it emitted this error?

2.  If not, is there any other way to get CCS to help trace
    backward to that earlier declaration?

This is conceptually related to a question I asked about
"listing" files last year, as finding this kind of error
with any tool that generates what I call a listing is a
trivial exercise.

  • 0
    TI__Guru**** 244930 points

    Look at the Console window to see the build unfold from a command line perspective.  That will show you which source file is being compiled when the error occurs.  Once you know that, preprocess the file as described here. (Ignore the parts about sending the file to TI.) You should be able to see the multiple definitions of CSM_PWL in the resulting .pp file.

    Thanks and regards,

    -George

  • 0 in reply to George Mock
    Expert 1310 points

    Thanks George!

    I had gone through several manuals and learned how to turn
    on the preprocessor output (*.pp) files--I thought.  These
    *.pp files were left in the Debug directory and bore no
    resemblance to the *.pp files I was able to route to the
    project directory with your help.