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.

CCS/TMS320C6657: Import of Variables in Window Preferences does not work.

Part Number: TMS320C6657

Tool/software: Code Composer Studio

Hi TI Support Team,

I try to import Variables settings via Preferences dialog from a file, which I have exported from another workspace. 

I have try out the import in CCS 7.0.0 and 7.1.0 as well. Unfortunately it does not work on both versions.

Kind regards

Sven

  • Postscript:
    The first import via CCS > Build > Variables dialog will be written to General > Workspace > Linked Recources

    I am a little confused about that.

    Kind regards
    Sven
  • This is actually expected behavior. The imported variable will be set both as a Build Variable and Linked Resource Path Variable.
    More information on this is in this wiki page. Note the section that mentions what was updated for CCSv6/v7, but in other respects it works the same way as in CCSv5.

  • Hi AartiG,

    the problem is that the imported variables are not viewed in CCS > Build > Variables, the list is empty !!!

    And also a second import with modified content does not overwrite the old variables in General > Workspace > Linked Recources (the override option has been selected).

    As result the behaviour is not as expected. Please would you try it out on your site.

    Kind regards
    Sven
  • Hi AartiG,

    I have play around the Windows > Preferences > CCS > Build > Environment.

    I am working with CCS 7.0.0 and a clean Workspace. 

    If I define a new Environment variable and I want to replace the existing Environment variable of my system, then it does not work as expected, because the switch Append or Replace has no effect.

    In my clean workspace the Environment variable will be appended and in my old workspace it will be replaced regardless of the settings.

    Kind regards

    Sven

  • Some more information:

    It looks so that the file org.eclipse.cdt.core.prefs must be edit manual to avoid the "Append" behaviour. E.g. my both workspaces have the following different entries:

    clean workspace from CCS 7.0.0:

    environment/workspace/BOOST_DIR/delimiter=;

    environment/workspace/BOOST_DIR/operation=append

    environment/workspace/BOOST_DIR/value=D\:\\Libraries\\Boost\\boost_1_58_0

    old workspace (origin from CCS 6.x imported):

    environment/workspace/BOOST_DIR/delimiter=;

    environment/workspace/BOOST_DIR/operation=replace

    environment/workspace/BOOST_DIR/value=D\:\\Libraries\\Boost\\boost_1_58_0

    Hint to CCS 7.1.0:

    This version is not really useable for C66xx, because it required xdctools_3_50_01_12_core and all provided libraries (OpenMP, IPC, PDK) are not compiled again this new XDC Tools.

    Kind regards

    Sven

  • Sven Mulka said:

    the problem is that the imported variables are not viewed in CCS > Build > Variables, the list is empty !!!

    I tried this out and after importing a variables file, I see it listed as a Linked Resource path variable under Window->Preferences->General->Workspace->Linked Resources,  but not under Window Preferences->CCS->Build->Variables (as you mentioned). I'm not sure if this is intended behavior or not so I will file the issue so the development team can verify and confirm. I did notice though that if I go into the Properties of any project in the workspace, I see the variable listed under Build->Variables tab when "Show system variables" is enabled. So the variable is in fact getting recognized as a build variable by the projects in the workspace, it is just not listing it at the workspace level.

    Sven Mulka said:

    And also a second import with modified content does not overwrite the old variables in General > Workspace > Linked Recources (the override option has been selected).

    I see this as well. The Build Variable at the project level does get updated with the new value, but the Linked Resource path variable at the workspace level does not. I will file this as an issue for investigation as well.

    Sven Mulka said:

    If I define a new Environment variable and I want to replace the existing Environment variable of my system, then it does not work as expected, because the switch Append or Replace has no effect.

    Could you provide a detailed example of how/where you are defining the environment variable and how/where you are checking whether the replace/append has occurred correctly?

    Sven Mulka said:

    Hint to CCS 7.1.0:

    This version is not really useable for C66xx, because it required xdctools_3_50_01_12_core and all provided libraries (OpenMP, IPC, PDK) are not compiled again this new XDC Tools.

    CCS 7.1.0 also comes with xdctools 3.32.01.22 in case that version is compatible with the other tools.

  • The tracking number for the two issues with the import of variables file is CCSIDE-3159.

  • Hi AartiG,

    thanks for your reply. To your question:

    Could you provide a detailed example of how/where you are defining the environment variable and how/where you are checking whether the replace/append has occurred correctly?


    I have defined some environment variables via Windows settings (some global and some per user). As described before in my post, I want to modify the BOOST_DIR environment variable local for the workspace only to select a different version of BOOST library for the DSP project.

    After Apply and reopen the Preferences dialog I can see that the variable was not replaced in CCS > Build > Variables with "Show system variables". Instead it was a string list.

    I found the origin file <workspace>\.metadata\.plugins\org.eclipse.core.runtime\.settings\org.eclipse.cdt.core.prefs. Here you can see that each new Environment Replacement will be define in Append mode.

    I hope that clarify my approach.

    Kind regards

    Sven

  • Comment to CCS 7.1.0:

    If I select the provided xdctools 3.32.01.22, then I get some errors during the compilation.
    The newer version CCS 7.2.0 provides an update to xdctools_3_32_02_25_core. With that version the CCS 7.2.0 is able to compile my projects, but the version CCS 7.2.0 has some other issues :-( For that I am in discussion in another thread.

    Kind regards
    Sven
  • Sven Mulka said:

    After Apply and reopen the Preferences dialog I can see that the variable was not replaced in CCS > Build > Variables with "Show system variables". Instead it was a string list.

    I found the origin file <workspace>\.metadata\.plugins\org.eclipse.core.runtime\.settings\org.eclipse.cdt.core.prefs. Here you can see that each new Environment Replacement will be define in Append mode.

    Thank you for providing details. I have filed bug # CCSIDE-3162 tot rack this issue. Feel free to track it using the SDOWP link in my signature.

  • Hi AartiG,

    thanks for tracking the bug in the SDOWP.

    Kind regards
    Sven