• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 53 subscribers
  • Views 593 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.

Original question:

CCS/TMS320C5515: Exporting Projects

CCS/LAUNCHXL-CC2640R2: CCS Export/Import issues

James Whitney
Intellectual 490 points

Part Number: LAUNCHXL-CC2640R2

Tool/software: Code Composer Studio

Greetings,

I have a project that was quite a struggle to finish. I need to demo this project periodically so I need a way to make this happen with minimal time and minimal possibility of failure. My problem is with the way the Project/Workspace 'Export' and 'Import' functions work.

I have used the Eclipse suite in several different chip/manufac. environments. In those environments it was as simple as 'exporting' the workspace/paths/.....Then, on the same/different machine running the same version of IDE, 'Importing' that project. Once that was done, the project compiled without error "....just as if it had never left..." So far, this is not my experience with CCS (Ver. 7.4.0). I have exported my workspace. I have tried several methods of importing the project, none of which seem to work. It is a Bluetooth project, so I build stack library first before I build the application. The stack library builds without error. When I build the application it tells me it can't find the stack library. I suppose this could be a path error, but that's part of the issue - in every other usage of Eclipse where the 'Import' command is used I've never had to come in and start tweaking 'this and that'. I thought the purpose of 'Export' was to preserve the entire workspace environment such that when it is imported - particularly to the same version of the tool - it was basically plug-and-play after import.

I've tried 'Open Projects From File System' (which loads everything, but again, gets hung not being able to find/open any of the stack library files). I've also tried 'Import' - same result.

Seems to be a two-part issue.

1. The Export/Import issue, which leads to - at least in this case -

2. Application errors in finding the stack library (from which all of the remaining errors originate).

Help/comments are appreciated.

J.

  • 0
    TI__Guru**** 173310 points

    James,

    Your attachment did not come through, could you try to attach it again please?

    The export/import process may not always "preserve" your original environment in its entirety. Especially when working with linked resources and path/build variables, it can sometimes be a bit complex to truly preserve the complete environment. Please see this page on Sharing Projects for a little background on how the export/import works. http://software-dl.ti.com/ccs/esd/documents/ccs_sharing-projects.html

    If you can show us the build errors (a full CCS build log will be helpful) along with any other useful screenshots, we should hopefully be able to point you in the right direction.

  • 0 in reply to AartiG
    Intellectual 490 points
    Hello, AartiG,
    Yes, earlier I had taken a *quick look* at the 'sharing' page. I'll take another look and read a bit closer.
    Periodically, I have to step away from TI. As mentioned, in the 'other' manufacturers implementation/usage of Eclipse, 'Export/Import' is absolutely plug-and-play, at least for the particular projects I'm dealing with in that environment.
    Once I've acquired the CCS build log, I'll be back.
    Many thanks,
    Jim
  • 0 in reply to James Whitney
    TI__Guru**** 173310 points
    Jim,

    It's been a few days since I heard back from you, so I plan to close this thread for now. Please do feel free to come back to it when you have more details and the build log and the thread will re-open. If the thread is locked due to inactivity, then simply create a new thread using the "As a related question" button. Thanks!