• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 53 subscribers
  • Views 897 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.

Feature request: Quiet option for CCS5 generated make files.

Eliot Blennerhassett
Intellectual 445 points

Current build console output is exeedingly verbose.

Request is to generate makefiles using verbosity-limiting macros a-la linux kernel or automake.

make V=1 results in former verbose output

Example of verbosity-limiting macro definition and use.

V_CC = $(_v_CC_$(V))
_v_CC_ = $(_v_CC_$(DEFAULT_VERBOSITY))
_v_CC_0 = @echo "  C6000 Compiler :  " $<;


DEFAULT_VERBOSITY = 0


axctrl_base.obj: /home/sw/dsp/axctrl_base.c $(GEN_OPTS) $(GEN_SRCS)
    $(V_CC)"/opt/TI/ccsv5/tools/compiler/c6000/bin/cl6x"   ... all the rest of the commandline

 

Resulting output is one line when V=0 or not defined:

  C6000 Compiler :   /home/sw/dsp/axctrl_base.c

Errors and warnings are much easier to see.

As opposed to 15 wrapped lines on a 132 column terminal for the verbose version.

  • 0
    TI__Guru**** 171809 points

    Hi,

    There are ways to reduce the output of the gmake and the compiler.

    For gmake, add the option -s to its launch command. Go to Project properties --> C/C++ Build --> tab Builder Settings --> Build Command. 

    For the compiler select the options -q or -qq. Go to Project properties --> CCS Build --> Compiler --> Diagnostic options.

    Although this reduces the information output on the console, it does not eliminate the file descriptions. Can you give it a try and see if this helps a bit in your case?

    This is what came on the top of my mind, but I will check if there are additional configurations that can help.

    Regards,

    Rafael

  • 0 in reply to desouza
    Intellectual 445 points

    Thanks Rafael, that helps a lot.

    -q was sufficient for compiler (Note it is set using "Quiet Level' selector in Diagnostic Options. I missed this at first because by default the selector is blank)

    but still there is IMO excessive @echo generated text and blank line per file in the output Eg.

    Building file: ../dsp2310.c
    Invoking: C6000 Compiler
    "../dsp2310.c", line 370: warning: #warning directive: There are still some stub functions
    Finished building: ../dsp2310.c
    (blank line)

    I'd like to see something like:

    C6000 Compiler :  ../dsp2310.c
    "../dsp2310.c", line 370: warning: #warning directive: There are still some stub functions

     

  • 0 in reply to Eliot Blennerhassett
    TI__Guru**** 171809 points

    Hi,

    I am glad the verbosity was reduced with the options. I couldn't find a way to reduce it even further.

    Since CCS uses the Eclipse CDT Builder in all the managed projects (and the Makefile is generated by it), I think the change is not very easy. We usually stay away from modifying the standard core components and potentially breaking compatibility with everybody else...

    I searched around and found a similar request in the Eclipse forums and found a still open Bugzilla entry. This will probably have to be implemented before we apply this change to our tool.

    I would experiment with one thing, though. The pre-build step (project Properties --> CCS Build -> tab Build Steps) runs after the makeifile is generated by the CDT. You can write a simple Perl script that removes the extra @echo lines and therefore achieve what you need.

    Regards,

    Rafael

     

     

  • 0 in reply to desouza
    TI__Guru**** 171809 points

    In any case I filed the enhancement request SDSCM00040952 (you can check its status in the link SDOWP in my signature below).

    Cheers,

    Rafael

  • 0 in reply to desouza
    Intellectual 445 points

    desouza said:

    I would experiment with one thing, though. The pre-build step (project Properties --> CCS Build -> tab Build Steps) runs after the makeifile is generated by the CDT. You can write a simple Perl script that removes the extra @echo lines and therefore achieve what you need.

    Good thought, but the prebuild step is actually part of the generated makefile, and only gets executed after all the makfiles have been read.

    the current situation is adequate, but I may make a script that tweaks the generated makefiles when I do a commandline build, and one day the bugzilla issue may get fixed, and I'll be pleasantly surprised.

  • 0 in reply to Eliot Blennerhassett
    TI__Genius 9435 points

    FYI - this has been implemented and will be available in CCSv5.1.1.  The Build Console verbosity can now be controlled through the Preferences > CCS > Build page:

    Four settings will be available: Verbose, Normal, Quiet, and Super quiet.

    - Baltasar