• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 52 subscribers
  • Views 460 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.

Project Configurations incorrect when importing a specific existing CCS/CCE Eclipse Project File

Jon Peterson
Expert 1760 points

I downloaded and unpacked slac139c.zip from the TI web site. This is the eZ430-RF2500 Wireless Sensor Monitor. I installed the package and then imported the project into CCS v4.1.2 with "copy" selected. However, doing this caused many build errors. If I delete the project and re-import it with "copy" not selected; ;then it builds ok. However, this is not exactly what the user would like to do since many of the files need to be modified and the project rebuilt inorder to learn how the MSP430 eZ430-RF2500 Development Tool works. We don't really want to modify the original downloaded and installed files but a "copy". Might make a mistake, hard as that is to imagine, and need the originals as reference or just to reset to the initial configuration after testing out trial variations.

  • 0
    TI__Guru**** 463481 points

    Hi Jon,

    Many projects often are very dependent on a specific directory structure, with the project files needing to be in their original location after installation. Otherwise things like relative paths will break if the projects are moved elsewhere (like into your workspace). In these cases I backup my files into a separate location so I have the original files unmodifed.

    ki

  • 0 in reply to Ki
    Expert 1760 points

    Ki,

    I certainly understand that backing up the originals or keeping the original downloaded installer are options.

    However, what I guess I am missing here is the "import" function of CCS. If the "import" function doesn't
    sort out relative paths etc, then, intuitively, I don't understand what "import" is for. And if the "import" function
    can't sort out relative paths and other parts and need to be adjusted during import, then it should, at least,
    give the user a warning that the import is probably not going to be useful. The compile time error messages
    didn't give a clue as to what the problem was. The files were "visible" in CCS, but NOT in the windows
    folder structure for the project in the workspace. Only experience and trial-and-error led to the real problem
    that started with importing the project. I really wonder why you don't consider either the failure of import to
    "import" or to provide adequate warning a "bug" in CCS?

    Thanks, Jon

  • 0 in reply to Jon Peterson
    TI__Guru**** 463481 points

    Jon,

    The import project is to simply add a project to the workspace (it will show up in the C/C++ Projects view). It will try to resolve as much as it can on import, but it doesn't fix everything. It's a bit of a tricky topic. Might I suggest some documentation that hopeful will clear up some concepts on projects:

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

    http://processors.wiki.ti.com/images/0/09/CCSv4_Tips_%26_Tricks.pdf (slides 15-23)

    Thanks

    ki