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.

Code Composer 5.5: No Rule To Make Target

Other Parts Discussed in Thread: TMS320F28035

I am using Code Composer 5.5.0.00077 on a TMS320F28035.  I have added a file to the project via the Project -> Add Files... menu (as I've done previously with other files).  If I try to build it I get an error message stating that functions in the added file called by another function can't be found ("unresolved symbol").

If I try to build the individual file I get the following error:

gmake: *** No rule to make target `acu410028_RelayManager.obj'. acu410028_dev Unknown C/C++ Problem

Any idea as to how to resolve this?

Thanks in advance for any assistance.  

  • andrew barnett66202 said:
     I have added a file to the project via the Project -> Add Files... menu (as I've done previously with other files).

    So you "added" the file to the project, not linked it correct? Can you copy the full output of the CCS build console to a text file and attach it here?

  • Looking at the build output, I don't see the file acu410028_RelayManager.c being passed as a source file to the compiler. Not sure why this is the case, but for some reason the project appears to not be seeing it as a source file.

    Was project created with an older version of CCS? Could you try importing the project into a new, clean workspace to see if that helps, or maybe even create a new project with CCS 5.5 and then add all the source files/build settings to it.

  • That did it, thanks.  the project was originated under CCS4

    Perhaps you can shed some light on this warning that I get for every IQmath function I use:

    Description Resource Path Location Type
    #16002-D build attribute vendor section TI missing in "C:/vss_work/acu2803x/acu410028dev/Project/../../IQmath/lib/IQmath.lib<IQ12div.obj>": compatibility cannot be determined acu410028dev C/C++ Problem

    the consensus seems to be to ignore it, which is fine.