• State
  • Locked Locked
  • Replies 6 replies
  • Subscribers 52 subscribers
  • Views 2227 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.

CCS target configuration directory confusion

Kurt Jensen
Genius 5040 points

I have trying to clean up links and target configurations between multiple computers and users

I work on two comnputers with two different operating systems - XP and Vista (neither are my choice...)

I consolidated a confusing mess of target configurations into 3 that we actually use. I then assigned these 3 as needed - simulator, emulator, no gel. this works fine on the one computer. but when I move to the other computer it cannot find the target configuration because the user directory is different!

in Vista we have c:/users/<name>/user/CCSTargetConfigurations/<targetconfig>.ccxml

in XP we have c:/documents and settings/<name>/user/CCSTargetConfigurations/<targetconfig>.ccxml

any ideas how to deal with this problem? (note that the .project file is stored in version control so we really need a common solution)

  • 0
    TI__Guru**** 463981 points

    Hi Kurt,

    You can change the shared target configuration directory to something more fixed (not dependent on the user name or OS) and have all workspaces use the same path. You can change this under 'Windows -> Preferences -> Code Composer Studio -> Debug' and look at the field called "Shared target configuration directory'

    Thanks

    ki

  • 0 in reply to Ki
    Genius 5040 points

    thank you.  we are close but I see no solution.

    the problem I am trying to solve is to not have hard coded paths.  your solution is another hard coded path. granted I get a choice but it is still hard coded

    if two people on the same computer must use different mapped directories (TFS) and workspaces (CCS) then a hard coded path cannot work without undue difficultty.  what I need is the ability to enter a relative path. 

    when I entered "..\CCSTargetConfigurations" I got an error saying the path did not exist.  if I knew the absolute base address maybe I could fake it somehow.

  • 0 in reply to Kurt Jensen
    Genius 5040 points

    after mucking with the macros.ini and .project files, I think I have it

    1) added "CCSTARGETCONFIGURATIONS_PATH_VARIABLE=..\..\CCSTargetConfigurations" to macros.ini then deleted and imported the project (macros.ini is only effective when a project is imported)

    2) added a CCSTargetConfigurations directory to source control, at the same level as the Workspace directory, and populated it with ccxml files.

    3) added these lines to the .project file

      <link>
       <name>XDS100v2_evm6748.ccxml</name>
       <type>1</type>
       <locationURI>CCSTARGETCONFIGURATIONS_PATH_VARIABLE/XDS100v2_evm6748.ccxml</locationURI>
      </link>

    now this target configuration is relative regardless of the mapped directory and the workspace project.

  • 0 in reply to Kurt Jensen
    Genius 5040 points

    well that didn't work at all. careful when you assume that CCS will function in a reasonable way...

    NOW it is telling me that it cannot find c:\ccsv4\CCSTARGETCONFIGURATIONS_PATH_VARIABLE\XDS100v2_evm6748.ccxml

    THIS despite the fact that right-click Properties shows the Location=CCSTARGETCONFIGURATIONS_PATH_VARIABLE\XDS100v2_evm6748.ccxml and the Resolved location=E:\PyrocamIV\CCSTargetConfigurations\XDS100v2_evm6748.ccxml --- apparently no one told the debugger how to handle macros

    so now we're back to the original question...is there any way to configure target configurations in a .project file using relative paths?

  • 0 in reply to Kurt Jensen
    TI__Guru**** 173310 points

    Kurt,

    Please see this related thread: http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/151494.aspx
    Your error seems to be due to the same reason. But that thread also mentions that in spite of the error about not finding the file, the target configuration still launches ok. Is that true in your case as well?

  • 0 in reply to AartiG
    Genius 5040 points

    No, it does not launch