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 project migration to CCSv5 fails



hi,

I have a CCSv4 project generated by a script from an original clearcase project (gmake).

when trying to opening in CCSv5.1 M7, the project is not able to open the source files:.

Looking at the .project file it sounds the modified location for source files is not correct

In .project_initial, I have for instance

<location>S:\cdb\tcomap4440\tc_ivahd\ivahd_ducati_enc_frwk_board\cortexa9_cpu0_ape\airshow_p176x144_h264.c</location>
        </link>
        <link>
            <name>airshow_p176x144_h264_IBBP.c</name>
            <type>1</type>
            <location>S:\cdb\tcomap4440\tc_ivahd\ivahd_ducati_enc_frwk_board\cortexa9_cpu0_ape\airshow_p176x144_h264_IBBP.c</location>

where S: is a clearcase drive

In the .project generated by ccsv5 I have following syntax:

<locationURI>cdb/tcomap4440/tc_ivahd/ivahd_ducati_enc_frwk_board/cortexa9_cpu0_ape/airshow_p176x144_h264.c</locationURI>
        </link>
        <link>
            <name>airshow_p176x144_h264_IBBP.c</name>
            <type>1</type>

It sounds the S:\ is missing.

I have manually modified the .project

<location>S:/cdb/tcomap4440/tc_ivahd/ivahd_ducati_enc_frwk_board/cortexa9_cpu0_ape/airshow_p176x144_h264.c</location>
        </link>
        <link>
            <name>airshow_p176x144_h264_IBBP.c</name>
            <type>1</type>

by adding the S:\ everywhere and also renaming xml tag locationURI to location

I have attached a zip file with the different project files.

4300.ccsv4_to_v5_issue.zip

Does the isue comes from original project files (from script) or is it really a conversion issue?

regards

 

  • Hi,

    I can reproduce this issue and it seems related to the original .project file containing paths to linked files with backslashes("\") rather than forward slashes("/").

    I tried a couple of experiments and found that if the project is created with CCS 4.2.4 even with paths with backslashes, during the project build process, they are converted to forward slashes, and subsequently the conversion of CCSv5 will be ok. However, the project build process in 4.2.0 does not seem to convert the slashes and then the conversion to v5 fails. I will file a bug for this issue to request that the conversion process check for this. For the moment, you can work around it by modifying your scripts that generate the v4 projects to contain paths to linked files with "/".

    Hope this helps.

  • The bug # for this is SDSCM00041963.

  • hi Aarti,

    ok thanks for filling bug.

    I have tried with a modified script to use slash.

    it is fine. We can live with this fix

    regards