• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 52 subscribers
  • Views 2719 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

gmake dependency dropped error

Justin Oliver
Intellectual 530 points
Other Parts Discussed in Thread: AM1808

Hello,

I imported some projects into a workspace, and now I am getting this error:

 

gmake: Circular ../lib/am1808_bsl.lib <- ../lib/am1808_bsl.lib dependency dropped.

 

I am able to run other projects in the workspace, but not these that I just imported.  Any ideas?

Thanks,

Justin

  • 0
    Intellectual 530 points

    Here is a picture of the error when it is occurring:

     

    Any help at all would be appreciated!

    Thanks,

    Justin

  • 0 in reply to Justin Oliver
    TI__Guru**** 421230 points

    Hi Justin,

    I see this issue only when I do an incremental (standard) build of the AM1808 BSL library project where no changes were made (hence nothing to build). So it doesn't look like a big issue, though I will see why the error is occurring and let you know when I have an answer.

    Note that the other projects have the 'AM1808 BSL' project as a dependent project so building any example project will try building the the BSL project first.

    Thanks

    ki

     

     

  • 0 in reply to Ki
    TI__Guru**** 421230 points

    Justin - the cause of the issue is that in CCSv4, any file that is in the project folder besides in the generated configuration subfolder is considered part of the project. So because the library exists outside the configuration folder and in ..\lib, the library that is inside the folder is added as part of the build. Hence CCS detects that the file the project wishes to build is part of files added to the project. Hence the funky circular dependency warning. A Rebuild (or building when a change is detected) does not cause the error because it would delete that library file first before building.

    So while this warning does not impact anything. However the original project really should not have the library generated in a folder that is in the project folder but outside the generated configuration folder. Either have it inside the generated configuration folder or completely outside the project folder altogether.

    Thanks

    ki