• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 80 subscribers
  • Views 327 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.

Code Composer Studio forum

Chad Baker
Prodigy 60 points


I am using  "Code Composer Studio Version: 11.2.0.00007" compiling projects using the TI-RSLK MAX. I am having difficulty compiling several projects on a Windows laptop. The same project compiles on a Mac. The error message is "gmake: *** No rule to make target 'C:/Facultymyid/Documents/tirslk_maze_1_00_01/tirslk_maze_1_00_00/inc/Clock.c', needed by 'Clock.obj'."

The functions that give this error message are listed in the main file Lab09_SysTickmain.c

#include "..\inc\TExaS.h"
#include "..\inc\Clock.h"
#include "..\inc\CortexM.h"
#include "..\inc\SysTick.h"
#include "..\inc\LaunchPad.h"

It seems to me that compiler is not looking in the same folder for the function that the header is located in.

If this is correct, is there a magic tweak in the "Build Project" script that will resolve this problem?

If this is not correct, can someone help me figure this out.

The same project on the Mac needed to have characters in the five includes above changed from "\" to "/" to compile correctly.

Help please.

  • 0
    TI__Guru**** 474031 points

    Hello,

    The issue is that these example project appear to be set up so that they need to be used from their original location instead of imported to your workspace (which is the default CCS behavior when importing a project).

    If you wish to import and build from your workspace, ou'll need to add an additional include search path that points to the oirginal location of the project.

    For example:

    Thanks

    ki

  • 0
    Prodigy 60 points

    This did not directly resolve the problem but gave me info that helped resolve the problem. The problem was that I installed the workspace on a shared drive and the environment variables did not expand correctly. The problem was resolved by moving to a local drive. 

    Many thanks to Ki!

**Attention** This is a public forum