• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 53 subscribers
  • Views 3958 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.

Where is system variable XDAIS_CG_ROOT defined?

Scott Hansohn
Prodigy 60 points
Other Parts Discussed in Thread: TMS320DM6435

I imported several CCSv3.3 .pjt's into CCSv5.5, which worked great.  Now I want to add a couple of new projects.  I used the "bigtime" DSP/BIOS template as mentioned in http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/73127.aspx.  My target configuration is TMS320DM6435 which isn't in the list so I chose the evm6424 template (not much information is provided to help choose the best template).


For the imported projects XDAIS_CG_ROOT shows up with "Show system variables" in the Properties->Build, Variables tab.  For the new projects it doesn't show up.  If I manually define it as (Directory, C:/ti/xdais_7_21_01_07), I can add this symbol to my -include path and am able to compile and build just fine.

I'm unable to figure out how the imported projects are getting this variable automatically defined.  I'd like to have all of my projects use a common definition -- preferably determined by CCSv5.

  • 0
    TI__Guru**** 162285 points

    Depending how the original 3.3 project was created or if a macros.ini file is present CCS will create the variables automatically.

    Another option and one I like is to define the variables at the workspace level instead of the project level.  That way all projects have access to them.  If you go to the Windows menu and select Preferences, the in the search box at the top left type variables.   This will filter the preferences to just those related to variables.  Select Build Variables.  Now you can define the variable and have it available to all your projects.

    John

  • 0 in reply to JohnS
    Prodigy 60 points

    Workspace-level wouldn't work so well unless there's some way to commit CCS Build Variable definitions to source control (e.g. git).  My understanding is workspace is per-user and not intended to be shared or source controlled.

    Without this we'd have to train/remind our developers to manually add this whenever creating a new workspace.

    More importantly, we have a build machine that runs a script (.bat) that

    • extracts from source control to a clean folder,
    • creates a workspace,
    • imports the CCSv5 projects and
    • builds everything. 

    I'm not sure how I'd script adding the XDAIS_CG_ROOT Build Variable definition to the workspace.

  • 0
    Prodigy 60 points

    Once imported from CCSv3.3, the CCSv5 projects know about the system variable XDAIS_CG_ROOT -- projects I've manually created do not.  I've grep'd through all files in my workspace/projects/source and can't find where XDAIS_CG_ROOT is defined. However, diffing the .cproject files for the create-by-import vs. create-by-template, the imported project had this line in the Debug and Release definitions for cproject/storageModule/cconfiguration/storageModule/configuration/folderInfo/toolChain/option:

    <listOptionValue builtIn="false" value="RTSC_PRODUCTS=com.ti.rtsc.XDAIS:latest;"/>

    If I add this line then XDAIS_CG_ROOT shows up when "Show system variables" is checked on the project properties Build/Variables tab.  I don't know if editing the .cproject file is a good idea or not, but the library rebuilds successfully and the application links/runs successfully.

  • 0 in reply to Scott Hansohn
    TI__Guru**** 173310 points

    Scott Hansohn said:
    Once imported from CCSv3.3, the CCSv5 projects know about the system variable XDAIS_CG_ROOT -- projects I've manually created do not. 

    As John mentioned this depends on how the original project was created. As you noticed, it appears that the DSP/BIOS v5 Example templates in CCS v5 do not define this variable or enable the XDAIS component, so if you use one of these examples as a starting point then yes, you would need to define the variable yourself as you already discovered.

    You could either define the variable by going into Project Properties and creating a Build Variable for it, or you could edit the .cproject file as you noted. The line you identified in the .cproject file appears to the correct one. We generally advise against editing the .cproject file directly but minor changes such as this one should be ok. I would be sure to make backups of both versions though in case you need to revert back to the original project file for some reason.