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

CCSv4 - compile errors for files linked using portable projects do not show in "Problems" tab

Eddie3909
Guru 10385 points

Hi Folks

CCSv4.2.4 (and previous versions)

I know I posted this some time ago but can't find it. The problem is that files linked to a project using the "link files to project" method with macros.ini outlined in

http://processors.wiki.ti.com/index.php/Portable_Projects

do not show errors in the "Problems" tab (although they show errors in the "Console" tab).

This is a real pain when it comes to fixing compile errors.

Cheers

  • TI__Guru**** 169894 points

    Eddie,

    Was the forum thread below?

    http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/89359/313406.aspx#313406

    If not, could you send additional details?

    I just re-checked and several of my projects with linked files pointed by a macro inside macros.ini (not physically in the workspace) show errors in the Problems view. I am using 4.2.3.

    Regards,

    Rafael

     

  • in reply to desouza
    Guru 10385 points

    Hi Rafael

    Yes, thats the one. I see that the bug case SDSCM00039161 fix was targeted for CCSv5.

    Could it be that your directory structure is not the same as I specified in the forum post?

    I have not changed my directory structure since I first reported the error. But I'll try the example I sent in the previous post and see if 4.2.4 outputs errors in the problems page.

    (good job at finding my old post!!!!!)

    Cheers

  • in reply to Eddie3909
    Guru 10385 points

    Hi Rafael

    I used the files in the other post and followed the steps I had outlined in the post you found

    http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/89359/313406.aspx#313406

    Eddie -From post: CCsv4 build errors not showing in Problems tab said:

    The file doSomething.c has an error in it. When you build the CCSv4_linkFiles\ReferanceFileFromStaircase project, the error is shown in the console but not in the Problems tab.

    1) First, edit doSomething.c and remove the "j" declaration error. 

    2) Build the projects in CCSv4_origFiles, then built the CCSv4_linkFiles projects. (is the .cfg build ever slow!!!!!!!!).

    3) add the error into doSomething.c (i.e. int i; j)

    4) Build CCSv4_linkFiles\ReferenceFileFromStaircase.

    5) the console should display the error but it does not show in the Problems tab.

    With 4.2.4 I observed the same problem as 4.2.1. The error in doSomething.c is showing up in the Console window but not in the Problems window.

    Cheers

  • in reply to Eddie3909
    Guru 10385 points

    Hi Rafael

    Could it be that some of the project meta data is screwing up CCSv4.2.4's ability to display in the Problems tab? Is there a way to delete the meta data without having to redo the links?

    Cheers
    Eddie

  • in reply to Eddie3909
    Guru 10385 points

    Actually, that can't be the problem. I just created a new project that had links and it still has the same problem.

    Arg.

  • in reply to Eddie3909
    TI__Guru**** 169894 points

    Eddie,

    As you mentioned before, this issue is targeted to be fixed in CCSv5 and I imagine that 4.2.4 would still show the error.

    I recall the directory structure of the example project is somewhat convoluted (linked files inside other projects in the same workspace), therefore I agree with you: the arrangement of files is confusing CCS when dealing with the project in focus.

    The metadata would carry all the file information, but the Problems view does not seem to recognize that the file is part of two opened projects (I recall that, if you close one of them, the issue does not happen). Unfortunately I do not understand the metadata structures in deep detail to precisely know where the issue could be located or if a fix is possible in CCSv4. 

    I will check if the current CCS version I have (5.1 M6) shows this issue.

    Cheers,

    Rafael

  • in reply to desouza
    Guru 10385 points

    desouza said:
    As you mentioned before, this issue is targeted to be fixed in CCSv5 and I imagine that 4.2.4 would still show the error.

    But in your previous email you said you don't see this problem in 4.2.3?

    Is CCSv4 going the way of the dodo bird? I thought that bugs found in CCSv4 would be targets for both CCSv5 fixes and CCSv4. Not true?

    Can I run CCSv4 and CCSv5 on the same computer (I dont have to uninstall one to try the other?)

    Are most of you gals/guys using CCSv5?

    Cheers

  • in reply to Eddie3909
    TI__Guru**** 451311 points

    Eddie3909 said:
    Is CCSv4 going the way of the dodo bird? I thought that bugs found in CCSv4 would be targets for both CCSv5 fixes and CCSv4. Not true?

    Sort of. CCSv5.1 is the priority and all fixes will first be targeted for 5.1. Whether they make it to v4 depends on priority and impact. But when v5.1 is released, we hope to start moving people over asap. v4 will go into maintenance mode.

    Eddie3909 said:
    Can I run CCSv4 and CCSv5 on the same computer (I dont have to uninstall one to try the other?)

    Yup. Just keep them in different directories and have them use separate workspaces. I have a PC with 4 different CCSv4 installs and 6 different v5 installs and they all play nicely together for the most part.

    Eddie3909 said:
    Are most of you gals/guys using CCSv5?

    pretty much. I still use v4 quite a bit to investigate customer issues. Otherwise I use v5 for my own stuff.

    ki