• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 53 subscribers
  • Views 1993 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Eclipsec command to close a project

Srijith Vijay
Prodigy 145 points

Hi,

I am making use of the eclipsec commands to control CCSV6 from a script.

1) When I try to import two different projects into CCS using the eclipsec command, I cannot visualize them in the 'project explorer' screen of CCS even though the command executed successfully . How do I resolve this without having to close CCS.

2) Also, is there an API that can be used to close an open project in CCS ?

  • 0
    TI__Guru**** 451311 points

    Hello,

    1) Actually, you should not be allowed to import a project to a workspace that is already in use (the running instance of CCS). The command-line tool should fail in these cases. But it appears that it does. I will file a bug for this

    2) There are no commands to close  a project.

    Thanks

    ki

  • 0 in reply to Ki
    TI__Guru**** 451311 points
    I filed a bug for item #1. Tracking ID: CCSIDE-2905
  • 0 in reply to Ki
    Prodigy 145 points

    Hi,

    Thank you for the quick reply.

    But when I have CCS open and try to import a new CCS project using the eclipsec command. It does not show up in the project explorer window along with the other projects in the same workspace.

    I have to close CCS -> Execute the eclipsec command to import the CCS Project -> Now when I open CCS, the project appears in the project explorer window

    Is there a way to make this newly imported CCS project appear in the project explorer window of the already open CCS, immediately after I execute the project import command in eclipsec.

    This is possible if I use the 'Import CCS Project' option in the GUI for importing the project and the same behaviour is expected for the eclipsec command as well

    Thanks
    -Srijith

  • 0 in reply to Srijith Vijay
    Prodigy 145 points
    Also, I do not know how this is a bug. 'Import CCS Project' from the GUI works perfectly fine and it is the same functionality that I am expecting from the eclipsec command to import a new project, that is not already present in the workspace.
  • 0 in reply to Srijith Vijay
    TI__Guru**** 451311 points

    The bug is that you are not supposed to be allowed to use the eclipsec command to import a project to a workspace that is already in use by a running CCS GUI. That is simply not supported. Yes, the command-line import is actually successful in that case. But the issue is that by altering a workspace (via command-line) already in use by a running CCS GUI, it causes various sync issues with the workspace. That is why you don't see the project imported via command-line show up in the Project Explorer. And it is also why you cannot ever launch two separate instances of the CCS GUI that use the same workspace. And also, you probably noticed that when you close CCS afterwards, the project is no longer part of the workspace (the project folder may physically reside in the workspace folder, but the association with the project mananger is gone). You can confirm this if you have CCS open, do a command-line import with the same workspace, do a successful command-line build, then close CCS GUI and try a command-line build again (it will fail this time). This is because of the sync issue (CCS GUI saving the state of the workspace on exit and overwriting the changes made to it via command-line).

    In short, you should have the CCS GUI closed when you do your import (if you want to use the same workspace).  The bug is for the command-line import to fail when the workspace is in use, just like it fails when you try to run a second CCS GUI instance when the a first instance is using the same workspace.

    Thanks

    ki