• Locked Locked
  • Replies 5 replies
  • Subscribers 54 subscribers
  • Views 1012 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.

Platform wizard - absolute paths to xdctools

Ian Cole (old profile)
Intellectual 260 points

Hi,

I have created a platform definition for our board.  But it contains absolute paths to the xdc tools install dir in many files.
This means that for colleagues that have installed xdctools on different drives - the build fails.

From package.cfg.dep

C:/tools/ptp700/ti/xdctools_3_20_08_88/packages/ti/catalog/c6000/Arctic.xs
C:/tools/ptp700/ti/xdctools_3_20_08_88/packages/ti/catalog/c6000/IAntara.xs
etc 

from package.ext.xml 

<xdcRoot base="C:/tools/ptp700/ti/xdctools_3_20_08_88/">

from package.rel.dot

URL="../C:\tools\ptp700\ti\xdctools_3_20_08_88\packages\xdc\services\intern\cmd\package/package.rel.svg"];
etc 

Is there a way to make these definitions portable?

Ian

  • TI__Guru*** 130875 points

    Hi Ian,

    have at look at these two wiki topics.  You should be able to create some path variables to help overcome the issue.

    http://processors.wiki.ti.com/index.php/Portable_Projects

    http://processors.wiki.ti.com/index.php/Project_Sharing

    Please keep us informed whether this gives you the information you require.

    Best Regards,
    Lisa

  • in reply to Lisa TI
    Intellectual 260 points

    Hi Lisa,

    thanks for your reply. I have looked at those links - and whilst they might be helpful for producing portable projects. I could see nothing that might help to produce a portable platform package.

    The platform wizard takes a few memory and processor details and produces a package. There is no opportunity to reference any project variables within the wizard.

    Are you suggesting that I edit the files that are generated?

    Best regards,

    Ian

  • in reply to Ian Cole (old profile)
    TI__Guru*** 130875 points

    Hi Ian,

    Have you tried using the build variable for the XDIAS installation directory or an environment variable for example?  Please have a look at the Build Variables as per the screenshot below.  Note, you will have to tick "Show system variables".    If this does not do the trick I am going to have to dig a bit further for you.

    Best Regards,
    Lisa

     

  • in reply to Lisa TI
    TI__Guru*** 130875 points

    Hi Ian,

    just thought I would double check whether my last post helped or whether there is any update or unresolved issues regarding your enquiry.

    Best Regards,
    Lisa

  • in reply to Lisa TI
    Prodigy 95 points

    I have also encountered this problem, but don't have a great solution. 

    1. Close CCS.
    2. I chdir to my package directory. If I recursively grep all the files there, I'll find that CCS has saved a number of files with the explicit path to the XDC tools, making it difficult to share these files with other users.
    3. I did a search and replace of the path with the Build Variable ${XDCROOT}.
      For example, find . -type f | grep -v .svn | xargs sed -i 's/\/opt\/ti\/xdctools_3_04_46/${XDCROOT}/g' 
    4. Start CCS.
    5. I can build just fine. I can even edit the RTSC configuration, rebuild, and it's fine. However, when using the RTSC Wizard to make any changes, CCS rewrites the package files, replacing the Build Variable ${XDCROOT} with the explicit path to the XDC tools.
    My workaround is to repeat step 3 before sharing w/ other users, but this is a hassle.
    I consider this a CCS bug. The tool allows for Build Variables, and does a great job using those in all other CCS project files, making it easy share configurations across users. But, that's not the case with the RTSC tool, which writes the explicit path to the XDC tools in the config settings instead of using the handy Build Variable ${XDCROOT}.