• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 54 subscribers
  • Views 1585 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 6.1.2 incremental headless build

Johannes von Löwis
Expert 1816 points
Other Parts Discussed in Thread: CCSTUDIO, CONTROLSUITE

I'm trying to get a headless incremental build done with CCS 6.1.2 (C2000 toolchain).

I invoke eclipse as follows from a Cygwin bash on a Win7 host (the same happens, when I start it from cmd.exe):

 /cygdrive/c/ti/ccsv6/eclipse/eclipsec -nosplash -data ccs_ws -application com.ti.ccstudio.apps.projectBuild -ccs.projects LOJ_F -ccs.configuration Debug -ccs.buildType incremental

Then the whole project is built:


%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
CCS headless build starting... [Wed Apr 20 09:08:37 CEST 2016]
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

================================================================================
Pre processing...


================================================================================
Building...


**** Build of configuration Debug for project LOJ_F ****

"C:\\ti\\ccsv6\\utils\\bin\\gmake" -k all
"C:/Users/loewjoha/LOJ-Test/LOJ_F/preBuildStep_Debug.bat"
make[2]: Nothing to be done for 'code'.
' '
...all source files getting recompiled...

and when I ask for another build (without changing any source file) all source files are recompiled again...

From CCS (Project->Build Project) it appears to work as expected.

What am I doing wrong?

Regards,

Johannes

 

  • 0
    TI__Guru**** 171309 points
    Johannes,

    Interesting; I couldn't reproduce this in my setup with various projects (TI-RTOS, plain, GCC) and varying degrees of build completion (some built fully, others failed in the middle) but all of them always built incrementally. I even tested leaving CCS open and trying to see if I could reproduce this - no luck.

    Therefore, I suspect something else may be going on: my strongest suspicion is that perhaps a file is being kept as read-only by a version control plugin or another external factor.

    I will do some more tests and see if I am able to reproduce this.

    Regards,
    Rafael
  • 0 in reply to desouza
    Expert 1816 points

    Rafael, thank you for your response.

    I have investigated the problem a little further.

    By the way, the project is a legacy V3.3 project. I took the following steps:

    1.  import V3.3 project into CCS 6.2.1, close
    2. command line import project into empty workspace ccs_ws using:  eclipsec -nosplash -data ccs_ws -application com.ti.ccstudio.apps.projectImport -ccs.location "C:\Users\loewjoha\LOJ-Sandbox/LOJ_F"
    3. command line build project using eclipsec -nosplash -data ccs_ws -application com.ti.ccstudio.apps.projectBuild -ccs.projects LOJ_F -ccs.configuration Debug
    4. second command line build with the same command does a full build again
    5. Start CCS 6.2.1 again and add a predefined symbol  (Build->C2000 Compiler->Advanced Options->Predefined Symbols)  FILENAME_IN_ECLIPSE="\"${InputFileName}"\", close CCS
    6. command line build using the above command: "Nothing to be done for 'main-build'
    7. touch a single source file, restart command line build: only the files depending on that source file are recompiled.

    I.e., the symbol definition in step 5 appears to solve the problem.

    I hope this helps reproducing the problem and investigating its cause.

    Regards, Johannes

  • 0 in reply to Johannes von Löwis
    TI__Guru**** 171309 points
    Johannes,

    I was able to reproduce this issue here with projects that have some or all source files linked to the project directory.

    I can't necessarily explain the reason why the predefined symbol would fix that in your case, but it did not work for me (I am using the Symmetric PWM Example for F28069 controlCARD from the controlSUITE). I suspect it may have to do with "touching" the project build options and thus updating some internal references, but that does not seem to be a general workaround.

    In any case, I filed a bug report (CCDSK-471) for the development team and let you know how it progresses.

    I apologize for the inconvenience,
    Rafael