• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 54 subscribers
  • Views 618 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.

Compiler/CCSTUDIO: Can not use --preproc_macros along with --preproc_includes in with CGT v18.12.2.LTS

user6135372
Intellectual 765 points

Part Number: CCSTUDIO

Tool/software: TI C/C++ Compiler

I need to generate the ppm and ppi information within one compile step. But this seems not to be possible as the following example shows:

C:\ti\ccs910\ccs\tools\compiler\ti-cgt-arm_18.12.2.LTS\bin\armcl.exe --silicon_version=7R5 --code_state=32 --float_support=VFPv3D16 -g --diag_warning=225 --diag_wrap=off -display_error_number --enum_type=packed --abi=eabi --c99 --gen_cross_reference_listing --gen_func_info_listing --gen_preprocessor_listing --preproc_with_compile --preproc_includes=ti_fee_read.ppm --preproc_macros=ti_fee_read.ppi ti_fee_read.c --output_file=ti_fee_read.obj

But then I get this warning, which is essentially an error for me, as I need the ppi/ppm files to be generated for the further processes.

warning #24003-D: option --preproc_macros overrides preceding option --preproc_includes

Is there an option get get ppi and ppm information in one step?

  • 0
    TI__Guru**** 252200 points

    user6135372 said:
    Is there an option get get ppi and ppm information in one step?


    Unfortunately, no.  I filed the entry CODEGEN-6607 in the SDOWP system to request the compiler be changed to support using these options at the same time.  Note this entry does not report a bug, but requests a change.  You are welcome to follow this entry with the SDOWP link below in my signature.

    How do you perform the build?  With CCS?  With a makefile?

    Thanks and regards,

    -George

  • 0 in reply to George Mock
    Intellectual 765 points

    Dear George,

    thanks for the fast reply and thanks for open this feature request in your ticketing system.

    George Mock said:
    How do you perform the build?  With CCS?  With a makefile?


    No we are not using CCS, but a custom build tool which is make-like.

    Two additional questions based on your answer:

     - if this feature is added, is this something likely to be added in a LTS version? I am asking this specifically, as I need to use a LTS version in the project.
     - I know, tough to answer, but might it be possible to put a timeline on if and when it will be added? Or a short note in the ticket system, if the requested enhancement is valid/accepted?


    An an organizaational question: Should I accept this answer als solving the problem, or should I wait for a version including the feature?


    Thanks!

    Edit: If this feature request is accepted, it might be good to also support -ppd/--preproc_dependency in that list, as the error is basically the same.

    Therefore the best support would be to allow all combinations of

    • -ppd/--preproc_dependency
    • -ppi--preproc_includes
    • -ppm/--preproc_macros

    on a compiler invocation. What do you think George?

  • 0 in reply to user6135372
    TI__Guru**** 252200 points

    user6135372 said:
    if this feature is added, is this something likely to be added in a LTS version?

    It will not be added to any currently active stream of LTS releases.  By definition, we only fix bugs in such releases, and never add new features.  It could appear in a future LTS release.

    user6135372 said:
    might it be possible to put a timeline on if and when it will be added?

    I am unable to give any kind of schedule.  I can tell you that, generally speaking, feature requests similar to this one take around 1-2 years to appear in an LTS release.

    user6135372 said:
    Should I accept this answer als solving the problem, or should I wait for a version including the feature?

    Since the long term timeline is not known, I'd appreciate if you would accept this answer now.

    user6135372 said:

    the best support would be to allow all combinations of

    • -ppd/--preproc_dependency
    • -ppi--preproc_includes
    • -ppm/--preproc_macros

    on a compiler invocation. What do you think George?

    I agree that is reasonable.

    Thanks and regards,

    -George