• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 53 subscribers
  • Views 3137 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: Command line import of projects into a new workspace not working

Anthony Davis73
Prodigy 50 points
Other Parts Discussed in Thread: CCSTUDIO

Tool/software: Code Composer Studio

When I execute the following command:

C:\ti\ccsv7\eclipse\eclipsec.exe -noSplash -application com.ti.ccstudio.apps.importProject -data "C:\gitlocal\myproject\buildws" -ccs.location "C:\gitlocal\myproject\source"

...a new workspace in c:\gitlocal\myproject\buildws is successfully created, but at the command prompt I receive the help info:

 Usage:

     eclipsec -noSplash -data "<workspace_dir>"

     -application com.ti.ccstudio.apps.importProject

     -ccs.location <path> [<options>]

where options include:

     -ccs.location <path> 

and on and on.  It does not import the project at all, and immediately exits.  So it seems it's just not recognizing the importProject command, or it doesn't like the project path.  I've tried quotes, no quotes, all manner of slashes at the end.  I think I'm missing something really obvious, but I cannot figure out what.  In the buildws/.metadata/.log file, I get these entries:

!ENTRY com.ti.common.core 4 0 2017-10-09 14:37:36.499
!MESSAGE path=ccs_base/DebugServer

!ENTRY com.ti.common.core 4 0 2017-10-09 14:37:36.504
!MESSAGE debugServerDir=C:/ti/ccsv7/ccs_base/DebugServer
!SESSION 2017-10-09 14:38:00.594 -----------------------------------------------
eclipse.buildId=4.6.0.I20160606-1100
java.version=1.8.0_112
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Framework arguments: -application com.ti.ccstudio.apps.importProject -ccs .location C:\gitlocal\myproject\source -ccs .overwrite
Command-line arguments: -os win32 -ws win32 -arch x86 -application com.ti.ccstudio.apps.importProject -data C:\gitlocal\myproject\buildws -ccs .location C:\gitlocal\myproject\source -ccs .overwrite

The only thing that looks odd to me in the log is the space after the "-ccs" and before ".location".  I didn't have that in my command, but who knows what it needs.  

  • 0
    TI__Guru**** 173310 points

    Anthony Davis73 said:
    So it seems it's just not recognizing the importProject command, or it doesn't like the project path. 

    There does appear to be some sort of typo or an extra space or something in the command, especially since the log file alludes to the same. 

    Could you take a closer look at the command and see if that is the case? Are you running the command directly from command line or from a batch file?

  • 0 in reply to AartiG
    Prodigy 50 points

    AartiG said:

    There does appear to be some sort of typo or an extra space or something in the command, especially since the log file alludes to the same. 

    Could you take a closer look at the command and see if that is the case? Are you running the command directly from command line or from a batch file?

    The command above is just being run at the Windows command prompt...the only difference is that I've changed the project name here.  I wonder if that's the problem--the real project name has an underscore in it.  Let me try changing the directory name and running it again.  I'll report back.

  • 0 in reply to Anthony Davis73
    Prodigy 50 points

    Ok, after much fiddling around, I still don't know why the command above does not work.  It should, according to the documentation.  But this command achieves the same goal (and works):

    C:\ti\ccsv7\eclipse\eclipsec.exe -noSplash -application com.ti.ccstudio.apps.importProject -data "C:\gitlocal\myproject\buildws" -ccs.location "C:\gitlocal\myproject\source"

    It doesn't explicitly command the creation the workspace as the previous command would, but the workspace is indeed created nonetheless. I still think the previous command should work, and that it does not work is a bug.  In no place in the help (that I can find) does it specify this pattern.  Indeed, the pattern of command in the help system itself does not work at all. 

  • 0 in reply to Anthony Davis73
    TI__Guru**** 173310 points
    I am glad you now have a working command that satisfies your requirements. However, I don't see any difference between the command in your last post (which works) and the one in your first post.

    I am still curious - what is the exact command that fails?
  • 0 in reply to AartiG
    Prodigy 50 points
    Um, you're correct, they're exactly the same. huh.

    Ok, I don't know why it's working now at all. I had someone else reproduce the problem with the command, and it failed the same way, and then it worked for him, then he sent it back to me and now it works for me. When you said that, I double checked the differences, and as you say, they're identical!

    I'm so confused.
  • 0 in reply to Anthony Davis73
    Prodigy 50 points
    ...the only think I can think of is that both of us who were having this problem rebooted our machines, and then it started working. So maybe a reboot fixed it? ugh

    Anyway, the command works now.