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 does not warn user that compiler is different when importing project



Hi

I recently added a CCSv4 (v4.1.2)  RTSC (BIOS 6) project to clearcase and had a colleague import the project into his workspace. He compiled and got errors. When we compared the compiler output, we noticed that his compiler was a different version. We checked the "CCS Build" options for the project and the configuration and they both said 6.1.15 (which is what I used). But CCSv4 is using 6.1.16. We believe this is due to 6.1.15 not being installed on his PC.

This seems rather dangerous for CCS to not output a warning and have it select the next best compiler. Is this expected behaviour?

Also, I experimented and found it doing the same thing with the BIOS. Ouch!

Cheers

  • It also decides what XDCtools version its going to use. Arg!

     

  • Eddie,

    I would've expected a message in the Problems View that said something like "This project was created using a version of Code Generation tools that is not currently installed.....". Do you not see any such message? I know I have seen this message many times, but I will test this again to see if anything has changed. I assume your co-worker is importing it into CCS 4.1.3?

  • Hi

    I can't say that I did, but I'll find another PC to check this out.

    We are still on 4.1.2, but will soon migrate to 4.1.3 when the patch is available (it looks like the DVD image is only available now)

     

    Cheers

  • Eddie,

    I was able to duplicate the behavior you are observing. CCS did not warn when I imported a project created with specific versions of CGT/BIOS into a PC that did not have those versions. I think it is ok that it uses the default versions for building the imported project, however I agree that it should at least warn the user that the original project was created using different versions, so if there are discrepencies/errors in the build, it will be easier to pin-point why.

    I entered a bug report to track this issue, the tracking number is SDSCM00037475.

    You may track the status of this issue using the SDOWP link in my signature below.