CCES 2.9.3 project incremental build problem

I have a strange problem when I am doing an incremental build of a project after a source edit.

If I clean the project and then rebuild, it is fine but of course it takes time.

If I edit the source and then rebuild, I get for Core1 and Core2 (Core0 is fine):

make: *** No rule to make target `../../../../../../../../../../../Analog Devices/CrossCore Embedded Studio 2.9.3/SHARC/lib/src/services/Source/dma/adi_dma_def_bf60x.h', needed by `system/services/dma/adi_dma.doj'. Stop.

So I have to clean and rebuild every time I make a source change which is annoying.

What could be the reason?

I have looked closely in the project settings but I cannot find the reason. But I trust it must be a problem in the settings somewhere...


I am using cces 2.9.3 and SigmaStudio for SHARC, hardware EZ-kit SC589

Missing details.
[edited by: bnilsson at 12:30 PM (GMT -5) on 1 Dec 2020]
  • Hi,

    The "No Rule to Make Target" error can be a tricky one to track down, but it is ultimately caused by a reference in your makefile to a non existent file. The problem can be that it doesn't necessarily have to be an actual filename causing the problem; it could be a corrupt command line in the makefile.

    The first place to look is the makefile itself, to try and track where the error is actually coming from; find any references to the filename, and ensure that these commands are correctly formatted.

    Next you should check the files/directories that these commands are referencing; do they actually exist? If the files do exist, are they in the location the command line is looking, or are they elsewhere?

    You should next check your project options. Ensure that all 'Search Directories' for the Linker, and 'Additional Include Directories' for the Compiler/Assembler are configured correctly. If any of your paths or filenames are wrapped in quotes, ensure that they have both a closing and opening quote, as this can cause problems with the makefile.

    Please refer the below FAQ for the same:

    If still you are facing this issue, please share us the complete project which replicated this issue.This will help us to assist you further.


  • Ok, I found it. Stupid of me, I should have known, as I have encountered the same problem so many times before: The project file path length was too long.

    Seriously, a project path length check with an error message would be REALLY useful.