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.

This project contains unresolved buildable linked resources. It might not build as expected.

On CCS5 I get this warning above. But there is no hint, which resources are unresolved. Therefore the complete project (1000 files) has to be checked by hand. But this is nearly impossible

  • Hi Rainer,

    please have a look at this post:

    http://e2e.ti.com/support/embedded/f/355/t/112870.aspx

    right at the end. That might be the same problem you're facing ...

    Please let us know if that helps.

    Kind regards,

    one and zero

  • Hi One and Zero,

    i did already know before I did write this issue, that 1 of the 1000 files inside the project doesn't exist anymore physically on the disk. But I don't know which one. So for me it is important to know which file causes the warning, that I can remove this entry from my project.

     

     

  • Hi Rainer,

    I understand that it's a pain checking through 1000's of files. That's why I thought it might be helpful to look at just one ... it might solve your issue.

    It is clear that you're asking for a better feedback from CCS ... however this will need some time to implement.

    Could someone from the CCS development team please comment on this enhancement request.

    Thanks,

    one and zero

  • Hi Rainer, 

    Maybe I misuderstood the problem but for files that can not be resolved, I believe you should see a warning icon overlaid on top of source icon in project explorer like picture below when a source file can not be found due to:

    a) it is no longer in the file system or

    b) it has changed its location relative the the linked resource macro that is used in project file. 

    c) last possibility is that linked resource macro is not defined correctly

     

  • Hi Martin,

    this was the case in CCS4 not from the beginning on, but after a TI correction, but in CCS5 the Icon is missing again

     

    Best regards

     

    Rainer

  • Hi Rainer, 

    Which exact version of CCS are using (from Help->About Code Composer Studio). Picture in previous post was captured using a recent CCS v5.1, I changed what the macro is set to. Warning icons appeared right away. 

     

    Martin

     

  • Hello,

     

    I am using version

     5.1.0.201105121800

    but I am also busy with installation of the actual CCS 5.1 Version.

     

    Rainer

  • Hi Rainer, 

    Above build seems like it is 5.1 M5, as far as I know ether is no final release of 5.1 yet. Most recent available is beta 2.1 (M8.5), Release Candidate should be made available shortly. Are you installing beta 2.1? Could you let me know if things behave better on newer 5.1 build? if not, then we may need to schedule a webex to allow us to take a look at your system. 

     

    Martin

     

  • Hi Martin,

    we did try also newer versions of CCS5 including CCS5.1.0.08012_win32.

    As in all this versions we have the problem described in http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/124007/453127.aspx#453127

    we cannot introduce a newer version for all developers.

    We have up  to 3 different build configurations:

    Release

    Release1

    Release2

    with different compile flags

    If there is now an entry EXTERNAL_BUILD_ARTIFACT inside a project file, the building is messed up for other build configurations:

    The entry you can see below:

     

    I just saw a new bug in  CCS5.1.0.08012_win32 Software:

    dependent projects are suddenly gone, see below

     

     

    Rainer

     

     

  • Hi Rainer, 

    I am not sure that I fully understand what the problem is:

    Based on your original issue in this post I was under the impression that issue was that you were getting an error because a linked file could not be found on the file system and you could not figure out which file that was. For linked files that can not be resolve there should be warning icon overlaid. Is this working? 

    The touching of project files when switching build configurations: Yes, unfortunately, this is still a problem that we are hoping of resolving in open source projects by contributing fixes. 

    Your most recent post is talking about an EXTERNAL_BUILD_ARTIFACT. First two sets of pictures showing linked resources: What are you trying to show, should they be the same and they are not? It sounds like you might be trying to control which resources are used for building in a build configuration. If this is the case then I think a better option would be to use Exclude from build functionality(select a file ; right click ; and choose "Resource Configuration->Exclude from Build". I don't think you can control which resources are applicable to which build configuration with linked files in .project file. 

    The last issue seems like a bug: Could you let me know which CCS version was the project first created with? i.e. something like projects were first created with CCsv5.1 M4 and worked fine when imported into M6, but when imported into M8 (8012), the dependent projects disappeared. 

    Thanks,
    Martin

     

  • Hi Martin,

    you asked me to retest with the newes Version, what I did. But we cannot intoduce the newest version, because the things described in the last Post. I will retest the described problem as soon as the blocking issues are solved.

     

    Regards

     

    Rainer

  • Hi Rainer,

    The project references have been replaced with new build-configuration references, which allows you to specify dependencies on exact build-configurations in the referenced project.  These new dependency references are exposed to the user in the project's Properties > Build > Dependencies tab.  FYI, these references are persisted into the .cproject file.

    The old Eclipse project references are no longer needed, and so each project is automatically migrated when you import it into CCSv5.1 - the old project-references are removed and replaced with the new build-configuration references.  The behaviour when building your master project should remain unchanged - each referenced build-configuration is built first.

    - Baltasar

  • Hi Rainer, 

    Ok, I understand now. 

     

    martin

     

  • Hi  Rainer,

    I  am  sorry,my  english  is  very  poor.please  forgive  some  error  in  my word.

    I get  the same problem  that you mentioned. I  want to kown the  solution ,can  you  tell  me?

    Regars

    TanZhicheng

  • Hi Zhicheng,

    Could you give more details on the issues you are seeing?

    Thanks,
    - Baltasar
  • Hi  Baltasar,

    I  met  a  warning  when i builded my  project ,"this  project contains  unresolved  buildable  linked  resources, it  might not build  as  expect“.  But  it builded sucessfully.just  have a warning.

    regards

    TanZhicheng

  • TanZhicheng,

    A "linked resource" is a file (or folder) which is physically located outside of your project, and is referenced by your project through a path reference.  Such resources are referenced using either an absolute path or a path relative to a "path variable".  The warning you are seeing means that one or more such linked resources cannot be resolved at build-time.  This can happen if the file no longer exists at the referenced location, or if it is referenced using a variable that is not defined or has a wrong value.

    Such unresolved linked resources are flagged with a yellow warning icon overlay in the Project Explorer view:

    The best way to see all linked resources is to open the project's Properties > Resource > Linked Resources dialog page:

    Here you can also edit each unresolved linked resource reference, or delete it from your project.

    - Baltasar

  • Baltasar Belyavsky said:
    Such unresolved linked resources are flagged with a yellow warning icon

    What if it is not flagged?

    I have a warning of 4 unresolved buildable linked resources. But as far as I could expand each and every path and file of the project structure, nothing is marked - and the evil warning does not show any additional information as to which resource is unresolved. Is there a way to find the list?

    CCS is 7.0.

  • Hi Bruno,

    Yes, to see all linked resources, open the project's Properties > Resource > Linked Resources dialog page.  See the screenshot in my previous post.  This page shows you all resources that are not resolved, and lets you to edit the links.

    - Baltasar

  • Baltasar,

    Thanks for the input.

    Unfortunately, I'm a magnet for unpredicted errors... There is nothing unresolved on Properties/Resource/LinkedResources...

    Any extra thoughts?

    Cheers,

    Bruno

  • Bruno,

    It is possible that you are hitting a known bug in CCS, which has been fixed for the upcoming CCS v7.1.0. In CCS v7.0.0, the workaround is to build the project a second time. Let me know if this warning disappears then.

    Thanks,
    - Baltasar