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.

AM2432: Linux CCS projects show error, while same projects are running fine on Windows

Part Number: AM2432

Hello expert,

When we are running CCS through terminal or GUI on Linux-Ubuntu, we are running into errors for one of our CCS projects. However, the same project when executed on Windows OS is running fine without any errors.

For example, one of the error was that, it is not detecting some files, in the below attachment, even though there is the correct path, CCS output gave an error and says 'checksum.h" file not found. This is not the issue in Windows as same code is running successfully without any errors. Please help us understand what is causing this.

Running CCS 11 on Ubuntu 18.

  • Hello

    Check to see if you can build the project from the CCS IDE. If you still have the same issue, please provide a screenshot of the file existing in the specified path (using some kind of file explorer program or running ls -la inthe specified directory.

    Thanks

    ki

  • When we are running CCS through terminal or GUI on Linux-Ubuntu, we are running into errors for one of our CCS projects. However, the same project when executed on Windows OS is running fine without any errors.

    The Linux paths are case sensitive, but Windows paths are case-insensitive.

    I.e. if there is an incorrect case in include paths or filenames then the build can be successful under Windows but fail to find the include file under Linux.

    The screenshot show the include path is /home/bsc/workspace1/code/lib_string/inc (i.e. inc with lower-case ell)

    Can you check if the directory name is actually /home/bsc/workspace1/code/lib_string/Inc (upper-case ell)?

    The error message shows the the checksum.c is in the /home/bsc/workspace1/code/lib_string/Src directory (upper-case S), so just wondering about the case of the include directory.

  • Hello,

    This resolved my issue, it was the case sensitivity with linux that was causing the error just like you said. 

    Thank you very much for helping me resolve.