• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 52 subscribers
  • Views 463 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.

Configuration management: No rule to make target 'all' for release configuration and new custom debug configuration.

Mark Swick
Intellectual 565 points

 I have an application project that links two custom libraries. When I try to build the release configuration I get the following error: No rule to make target 'all'

I also created a custom debugEVM configuration for building an executable for the eval module we started with. I have used the main debug configuration for our own DSP module design.

I had successfully built a custom library configuration without this problem also. I basically used the same procedure to create the custom executable build as I did for the library. The executable build gets the following error: No rule to make target 'all'

  • 0
    Intellectual 565 points

    I found the rpoblem to be that we had controlled "org.eclipse.core.resources.prefs" in CM which made it read only. Checking out the file to allow it to be written solved the problem. We may change this file to be a private file (uncontrolled) in the future.