• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Subscribers 55 subscribers
  • Views 642 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.

CCSv5 and Linked Resources

MattB
Expert 2025 points

Hi,

I'm just trying to update from CCSv4 to CCSv5.0.0.00090.

My project includes some linked files and I've changed the project file to used linked resources, in other words the project file contains:

<locationURI>COMMON/VersionInformation.c</locationURI>

and the Linked Resources dialog contains:

COMMON - D:\Documents and Settings\113007312\My Documents\A5000Demonstrator\trunk\common

CCSv5 won't build this project, I think it can't handle the spaces in the linked resource path.

I moved the files to D:\common and it built.

I tried using the 8.3 version of the path but the dialogue kept changing it back to the long path.

Obviously I can move my working folder but I thought I'd check I wasn't doing something wrong first!

Thanks,

Matt

  • 0
    TI__Guru**** 171729 points

    Matt,

    I tried to reproduce this issue here without success. Therefore what error are you exactly getting? Can you save the console window output to a txt file and send it?

    Also, what device family you are using? The CCSv5 LR edition was not yet tested with microcontrollers and there are some know issues with the post-build steps.

    Regards,

    Rafael

  • 0
    TI__Genius 9355 points

    Matt,

    I've created a simple CCS project but could not reproduce the problem with spaces in the path-variable - my project builds without problems.

    Could you try finding the precise steps to reproduce your problem?  What errors do you see when you build your project?

    Thanks,

    - Baltasar

  • 0 in reply to Baltasar Belyavsky
    Expert 2025 points

    Hi,

    Baltasar Belyavsky said:
    What errors do you see when you build your project?

    The console output is:

    **** Build of configuration Release for project VIP_DSP1_Application ****

    D:\Program Files\Texas Instruments\ccsv5\utils\gmake\gmake -k all 
    'Building file: D:/Documents and Settings/113007312/My Documents/A5000Demonstrator/trunk/common/VersionInformation.c'
    'Invoking: C6000 Compiler'
    "D:/Program Files/Texas Instruments/ccsv5/tools/compiler/c6000/bin/cl6x" -@"VersionInformation_ccsCompiler.opt"
    [Documents.]
    Fatal error: could not open source file "D:/Documents"
    1 fatal error detected in the compilation of "D:/Documents".
    Compilation terminated.

    >> Compilation failure
    D:\Program Files\Texas Instruments\ccsv5\utils\gmake\gmake: *** [VersionInformation.obj] Error 1
    D:\Program Files\Texas Instruments\ccsv5\utils\gmake\gmake: Target `all' not remade because of errors.

    I've also added the options file but note I added to .txt.

    Thanks,
    Matt
  • 0 in reply to MattB
    TI__Genius 9355 points

    That helps.  I did reproduce the problem. 

    I've opened a CQ to track this - SDSCM00038382 Long compile-commands fail for source-file paths containing spaces.

    Thanks,

    - Baltasar

  • 0 in reply to MattB
    TI__Guru**** 171729 points

    Matt,

    Thanks for sending this info. The error message is thrown by the compiler (not CCS) and the command invocation implies the file <VersionInformation_ccsCompiler.opt> has references to source files to build your project, is that so? I couldn't find a similar file in my build system therefore is this file being generated by you? 

    The reason of my questions is that I hit the exact same error when I added a custom options file (.opt) that has a reference to a source file without double quotes delimiting its entire path (a requirement for paths with spaces in a Windows environment). My project started to build properly if I included the double quotes in the source file reference inside the .opt file.

    On the other hand, if this file is being autogenerated by CCS then we will need its contents and (maybe) a test project that reproduces this behaviour.

    Hope this helps,

    Rafael

     

     

  • 0 in reply to desouza
    TI__Guru**** 171729 points

    Matt,

    Never mind my questions. Baltasar told me the file <VersionInformation_ccsCompiler.opt> is automatically generated by CCSv5 if the command line becomes too long (more than 1800 characters).

    Learned something new today. Sorry for any inconvenience.

    Cheers,

    Rafael

  • 0 in reply to Baltasar Belyavsky
    Expert 2025 points

    Oh, I've just released that in moving from CCSv4 to CCSv5 I also moved from CGT V7.0.3 to CGT V7.0.4.

    Matt