• State
  • Locked Locked
  • Replies 8 replies
  • Subscribers 53 subscribers
  • Views 703 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.

Original question:

CCS/LAUNCHXL-CC1310: Error gmake no rule to make target 'all'

CCS/PROCESSOR-SDK-AM335X: gmake: *** No rule to make target 'ti/os_drivers...

Christopher Weber
Genius 4995 points

Part Number: PROCESSOR-SDK-AM335X

Tool/software: Code Composer Studio

Hello,

I am using CCS 7.2, and this project uses the TI compiler...

So...  I'm happily right clicking on a files to do a "Build Selected File", one by one, which I copied into a project.  (Because I am resolving include paths for the new files)

All of a sudden, one of the files, in a subdirectory gives me an error "No Rule to make target..... /rndis_nimu.obj" 

Every other file I copied in makes just fine.  (at least so far...)

There is a little symbol of a pin or a key, or something on the file.  NONE OF THE OTHER FILES HAVE SUCH A SYMBOL.  What is that pin??   Why isn't this described anywhere??

This file built just fine in the other project I copied it from.

I've been right clicking and pulling up the properties and pressing "Restore Default" all over the place.  Nothing works...  But those little pins keep multiplying.  

But when they multiply to other places, those files STILL CAN get built.  Just not this one single file it's refusing to compile.

And I actually had to resort to appending "-clean" to the CCS shortcut, since this thing corrupts stuff so bad.   So I starts with "clean" every time.

What is going on??  How to I convince this environment to compile a file??

  • 0
    TI__Guru**** 173310 points

    Christopher Weber said:
    What is that pin??   Why isn't this described anywhere??

    The pin indicates that there are file specific options for that file different from the project level options. 
    http://software-dl.ti.com/ccs/esd/documents/users_guide/ccs_project-management.html#file-specific-options

    Try resetting them to default as described in the page and see if that helps.

  • 0 in reply to AartiG
    Genius 4995 points

    Per that page:

    AartiG said:

    If you instead go to the file’s Properties → Resource and click on Restore Defaults, it will restore the options back to default but will not remove the special icon. This is because even though the override options are removed, the special section for the file that was previously added is still there and so the icon remains.

    Okay, every time I tried to select the next folder up, or another file, and "restore defaults" those pins just kept proliferating.  So that explains why that much was happening.

    But it doesn't explain why it did not actually restore the default.  No matter what I did, it kept telling me no rule to make that file.  But all those other files that now are accented with little pins continued to build as before.

    And there is no simple "remove" to restore it back to the default.

    And there is no warning, or even an indication, that you accidentally left one of the file highlighted...  to ask you "Are you sure you meant to screw with the setting of this one individual file, and not the entire project? "

    Some how, some where, some little setting changed some default rule (the "make" doesn't seem to use explicit recipes, just default ones)  And it's a nightmare to figure out what it did, and how to undo any of it.

    I don't have this issue with any of the Visual Studio's...  CCS is incredibly un-impressive.

    If you instead go to the file’s Properties → Resource and click on Restore Defaults, it will restore the options back to default but will not remove the special icon. This is because even though the override options are removed, the special section for the file that was previously added is still there and so the icon remains.

  • 0 in reply to Christopher Weber
    TI__Guru**** 173310 points

    Did you also try resetting to default setting with the steps below? Did that not reset it either?


    To revert the file back to its default settings:

    1. Right-click on the file in the Project Explorer view.
    2. Select Resource Configurations → Reset to Default.
    3. Select the resource configuration to restore to default settings and click OK.
  • 0 in reply to AartiG
    Genius 4995 points

    Wouldn't that erase all my -I includes, -D defines, libraries, etc...?

    I was pressing the "restore" button on the file in question.  Logically, that is what I wanted after all.  That should have meant the same as "inherit from parent".

  • 0 in reply to Christopher Weber
    TI__Guru**** 173310 points

    By default all source files in a project will initially inherit the options set at the project level. File specific options may then be set at the file level. For example, if file1.c has some file specific options, then doing the above 3 steps to "reset to default" will revert its options back to the project level options. So the -i includes, -D defines, libraries, etc set at the project level will still apply to file1.c, only custom ones that had previously been added to file1.c will be removed.

  • 0 in reply to AartiG
    Genius 4995 points

    ....  When WHAT is highlighted??

    If I highlight it at the "Project" level, then EVERY file gets reset to the default?  What if I want only one file reverted to the default?

    If I highlight that specific file, it doesn't appear to work.  At least it never solved the "No Rule to Make... "  issue I was having.  Which was my original issue. 

    And I notice I was never given any solution to it.  My workaround was to blow away the project, and have to rebuild the project settings by creating a new one.  Nice way to spend an afternoon.

    CCS never fails to un-impress...

  • 0 in reply to Christopher Weber
    TI__Guru**** 173310 points

    Christopher Weber said:
    When WHAT is highlighted??

    The specific file with the pushpin icon.

    Christopher Weber said:
    If I highlight that specific file, it doesn't appear to work.  At least it never solved the "No Rule to Make... "  issue I was having. 

    I'm sorry that did not help with the build error. Seems that the make error was a separate issue or at least unrelated to the file having file specific options. Unfortunately the "No Rule to Make target" error is rather generic and there isn't a single reason that captures all scenarios, and a closer inspection of the  project is usually necessary. 

    I'm glad to hear that you've been able to move forward, and apologize for the troubles and inconvenience. 

  • 0 in reply to Christopher Weber
    Guru 92251 points

    Christopher Weber said:
    If I highlight that specific file, it doesn't appear to work.

    With CCS 10 I found that while selecting "Restore Defaults" on a single source file in the Project Explorer does appear to remove the file specific options, confusingly the "pin" symbol remains on the source file in the Project Explorer.

    In the .cproject file there are XML <fileInfo> nodes for each source file which has been given file specific options. In a text editor deleting the <fileinfo> nodes and then refreshing the Project Explorer removes the file specific options and removes the "pin" symbol in the Project Explorer.