• State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 53 subscribers
  • Views 707 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Suggest to separate SYSCONFIG code generation when build project in CCS

YiKai Chen
Guru 735635 points
Other Parts Discussed in Thread: SYSCONFIG

Sysconfig is an useful tool in developing but it's annoying that it will regenerate codes every time when we build project. Sometimes, we would revise the generated code for some reason and it would be overwritten. I would like to suggest to separate SYSCONFIG code generation when build project in CCS. Allow use to generate the code separately to avoid overwriting customized codes.

  • 0
    TI__Guru**** 450911 points

    Hello YiKai,

    I inquired about your request with the SysConfig engineering team. They mentioned that this has been discussed in the past. In the end, the below procedure of disabling SysConfig was decided upon:

    https://software-dl.ti.com/simplelink/esd/simplelink_cc13x2_26x2_sdk/3.40.00.02/exports/docs/ti154stack/html/sysconfig/sysconfig-disable.html

    In short: The files are always generated.  If you wish to freeze them or modify them, it is necessary to copy them out of the generated folder and stop using SysConfig. There were requests to support editing of generated files but the implementation of this would have been quite complex given the limited demand.

    Thanks

    ki

  • 0 in reply to Ki
    Guru 735635 points

    I know this workaround but It's still annoying to do such modification when you want to enable and disable sysconf. Hope your team would reconsider this seriously. Thanks for your help anyway.

  • 0 in reply to YiKai Chen
    TI__Guru**** 450911 points

    Understood.

    I just wanted to bring attention to another option that could be useful. You can use the “include in build” feature (available on the generated files view on the right via the a little slider for each file). If disabled, the file is generated to an “excluded” folder which isn’t part of the build. The idea is that you can copy it from there and alter it however you want, but it’s still generated each time so you can compare it to your modified version. Not quite what you need but perhaps useful in cases of working with an individual file.

  • 0 in reply to Ki
    Guru 735635 points

    Thanks for the workaround. Over automation is not a good practice from my point of view but it’s just my personal opinion anyway.