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.

Unresolved Symbol - for user generated directory, not a system library

Other Parts Discussed in Thread: CCSTUDIO

I see a ton of Unresolved Symbol posts but none seem to match my situation

I am creating some functions for my students to use (EE Freshman and Sophomores) in Code Composer Studio on the MSP432 Launchpad platform. I can create the .c and .h files. Place them in a separate directory, add the directory to the Project - Properties - Build - Compiler - Include Options path. I can see the directory and both .c and .h files in Project Explorer - MyProject - Includes. I #include the .h file in my current program and it finds the .h file and the function prototypes as evidenced by them showing up in the Outline window. When I compile I get the Unresolved Symbol error indicating 

Description Resource Path Location Type
unresolved symbol Clock_Init_48MHz, first referenced in ./delay_check.obj myFirstProject C/C++ Problem

Which I assume means it cannot find the .c file.

A) What am I missing

B) What CCStudio document discusses this - I have looked at several and none go into this detail

thanks

tj

  • I presume Clock_Init_48MHz is a function.  The object file delay_check.obj contains a call to this function. Yet no object file or library seen by the linker contains this function.  Where is it?

    Thanks and regards,

    -George

  • The function is in the .c file (co-located with the .h file). The system sees the .h file and the function prototype and shows it in the outline window. The problem is it is not finding the .c file. I understood that as long as it was in the includes path it would be found (just like the .h file is found). I can't figure out how to include a screenshot but it shows both the .c and .h files under includes in the project explorer, the .h file and the function in the outline.
  • I'm not sure how you have organized your CCS project.  If it is practical, I recommend you start over, following the methods described in the wiki article Projects and Build Handbook for CCS.

    Tim Johnson11 said:
    I understood that as long as it was in the includes path it would be found (just like the .h file is found)

    That is not the case for C files.  A C file must be presented directly to the compiler.  Only #include files are subject to being found along the includes path.

    Thanks and regards,

    -George