• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 54 subscribers
  • Views 1415 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 ccsv6 build using scm for sources

Steve Calfee
Intellectual 290 points

Other Parts Discussed in Thread: CCSTUDIO

Tool/software: Code Composer Studio

Hi,

I am trying to understand how to use ccsv6. We use several ti processors such as the hercules and tiva processors. We create local workspaces and check projects into scm (perforce in this example).

From the GUI on a new windows system I can import the saved project. Sometimes minor path tweaks are needed, (usually not) using relative path addressing. When I import a project I don't get a project folder in my workspace unless I "copy all files".

However in this imported without copy scenario the ccsv6 seems happy to build and operate on the imported project. The problem I am trying to solve is to be able to have a portable dev environment for dev work, but a fixed buildable application using a CI script to build everything from source code.

But I cannot start the compile from the command line because ccs cannot find the project. Maybe I am missing something from my command line incantation:

c:\ti\ccsv6\eclipse\eclipsec.exe -noSplash -data C:\Users\scalfee\workspace_v6_2_SW1.0 -application com.ti.ccstudio.apps.projectBuild -ccs.projects SupKernel -ccs.configuration Release -ccs.buildType full

If I import with the file copies the project subdirectory "supkernel" is there and the build works. If I imported but did not "copy all files" it cannot find the project. -ccs.projects does not take a path.

Thanks, Steve

  • 0
    TI__Guru**** 475841 points

    Hi Steve,

    Steve Calfee said:
    From the GUI on a new windows system I can import the saved project. Sometimes minor path tweaks are needed, (usually not) using relative path addressing. When I import a project I don't get a project folder in my workspace unless I "copy all files".

    I assume you are referring to how there is no project folder physically inside the workspace folder when you do NOT select the option to "copy all files". This is expected behavior. A reference to the external project is kept inside the workspace .metadata folder. 

    Steve Calfee said:

    But I cannot start the compile from the command line because ccs cannot find the project. Maybe I am missing something from my command line incantation:

    c:\ti\ccsv6\eclipse\eclipsec.exe -noSplash -data C:\Users\scalfee\workspace_v6_2_SW1.0 -application com.ti.ccstudio.apps.projectBuild -ccs.projects SupKernel -ccs.configuration Release -ccs.buildType full

    your command line looks fine. Assuming that C:\Users\scalfee\workspace_v6_2_SW1.0 -application is the workspace folder and you have already imported the SupKernel project to that workspace, then it should be able to find the folder - regardless of whether the project folder was copied to the workspace folder or not. I tested this in my environment and it seems to work fine.

    You can quickly test if the project is correctly associated with that workspace folder by launching CCS with that workspace folder and seeing if the SupKernel project exists in the Project Explorer view

    What is the exact error you see? Is it something like:

    Pre processing...


    !WARNING: Project 'SupKernel' was not found in the workspace! Ignoring...
    NOTE: use the '-ccs.autoImport' argument to automatically import projects found in the workspace root directory.

     

    ?

  • 0 in reply to Ki
    Intellectual 290 points

    Ki-Soo Lee said:
    From the GUI on a new windows system I can import the saved project. Sometimes minor path tweaks are needed, (usually not) using relative path addressing. When I import a project I don't get a project folder in my workspace unless I "copy all files".

    I assume you are referring to how there is no project folder physically inside the workspace folder when you do NOT select the option to "copy all files". This is expected behavior. A reference to the external project is kept inside the workspace .metadata folder. 

    Yes, correct.

    Ki-Soo Lee said:
    Steve Calfee

    But I cannot start the compile from the command line because ccs cannot find the project. Maybe I am missing something from my command line incantation:

    c:\ti\ccsv6\eclipse\eclipsec.exe -noSplash -data C:\Users\scalfee\workspace_v6_2_SW1.0 -application com.ti.ccstudio.apps.projectBuild -ccs.projects SupKernel -ccs.configuration Release -ccs.buildType full

    your command line looks fine. Assuming that C:\Users\scalfee\workspace_v6_2_SW1.0 -application is the workspace folder and you have already imported the SupKernel project to that workspace, then it should be able to find the folder - regardless of whether the project folder was copied to the workspace folder or not. I tested this in my environment and it seems to work fine.

    Changing project options (maybe to a write protected project if I forgot to check it out, seems to have created the missing folder in my workspace. I cannot reproduce the success path.

    I do know if I start with a fresh workspace and import a project the eclipse line does give me the error you mentioned. Adding -ccs.autoimport to the command did not help.

    Ki-Soo Lee said:

    !WARNING: Project 'SupKernel' was not found in the workspace! Ignoring...
    NOTE: use the '-ccs.autoImport' argument to automatically import projects found in the workspace root directory.

    OK, you seem to understand my situation, but cannot recreate it. Restarting ccs does find the project in the gui, but not in the command line. What now?

    Thanks, Steve

  • 0 in reply to Steve Calfee
    TI__Guru**** 475841 points

    Steve Calfee said:
    OK, you seem to understand my situation, but cannot recreate it. Restarting ccs does find the project in the gui, but not in the command line. What now?

    Yes, I cannot reproduce the issue. Can you send a test case? I'm looking for a simple project that you can reproduce the issue with. 

    Thanks

    ki

  • 0 in reply to Ki
    Intellectual 290 points
    DOH. I was able to get it to work with the example project. Then I looked at my failure case. I had the name of the project wrong. It is clearly shown in the gui project explorer - I just typed it wrong. When I start the problem project in the correct workspace with the correct project name I can indeed build from the command line.

    Sorry about the noise.

    Steve