• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 54 subscribers
  • Views 501 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.

CCSv4 CGT tools version use warning - enhancement request

one and zero
Mastermind 18256 points

Hi,

I am using CCS 4.2.0.10012.

I am using CGT 7.0.3 on different workspaces. Everything works fine.
I am additionally installing CGT 7.0.4 and announce that to workspace A. All .cdtbuild files of my projects are adapted and saved. They are used when I open my projects on workspace A again.
With CGT 7.0.4, but workspace B, the projects open and build, but without any warning that CGT 7.0.3 instead of 7.0.4 is used! It works again if I manually make CGT 7.0.4 known to  workspace B. This however may easily be forgotten and I build using the wrong tools version.

Could you please add a warning that discovers this?

(Same story applies to new versions of DSP BIOS).

Thanks and regards,

one and zero

  • 0
    TI__Guru**** 163035 points

    There has been a lot of debate on this one.  If the version # (X.Y.Z) is different in X or Y then it lets you know there is a problem.  If just the patch level differs (Z) it doesn't warn you.  This is the intentional behavior today.

    The reasoning being that compilers with only the last digit different are "equivalent" the only difference being a small number of bug fixes.

    Here is more info on how the notifications work.  If you really want it to give a warning in the third case that is something we can discuss again.

    John

     

    CCS outputs a warning  when the codegen-tool used is compatible but not equivalent to the original tool.  This happens when only the first version increment matches, and the rest do not (eg. 6.1.12 -> 6.2.0 will result in a warning).

     

    CCS outputs an error, for all ISA families, when the codegen-tool used is not compatible with the original tool.  This happens when the first version increment differs (eg. 6.1.12 -> 7.0.0 will result in an error).

     

    When both the first and second version increments are identical (eg. 6.1.12 -> 6.1.13), the codegen-tools are considered to be 'equivalent', and this generates no warnings.  Equivalent codegen tools would only differ in minor things, like changes to the tool-tip text, option labels, etc, so they should result in identical runtime behaviour, and there is no need to warn the user.

  • 0 in reply to JohnS
    TI__Guru**** 163035 points

    Ok we discussed this and filed a defect to track the issue: SDSCM00038205

    What we are planning on doing is: 

     

    1) In the CCS Build page of Build Properties, show both the version of CGT that original project was created with and effective version of CGT being used for the current build

    2) In C/C++ Build page, if possible, change label of Code Generation Tools version to be more intuitive and let people know that a different version might be used during build.  Likely not able to do this one.

    3) Warn users if the version they are using is a lower .Z number than what project was created with ( assuming X.Y.Z versioning - for eg, going from 6.1.5 to 6.1.2).

    What you are looking for is #3 but #1 should help as well.

     

     

    Regards,

    John