Introducing a dependency on Kconfig may cause portability issues with some toolchains (IAR for instance)

I am working on adding support for the IAR toolchain to Zephyr, and Kconfig is one of the issues I've run into.

At least in Zephyr, the output from Kconfig is run through the C preprocessor and this causes issues with the IAR preprocessor so for now I use gcc for this step.

Thomas

Den 2020-06-12 kl. 07:32, skrev David Hu via TF-M:

Hi Adrian,

Actually we have been investigating configuration alternatives and making some prototypes of Kconfig.

Kconfig can bring some advantages:

• It can setup configuration and check dependency before CMake starts and therefore it can help CMake simplify dealing with the mutual dependencies. For example, if CPU and arch options can be configured in Kconfig, CMake can avoid the workaround to re-configure compiler after parsing platform files.
• Kconfig can collect together the options which are distributed in various CMake files. Developers can more easily understand the options and their dependencies, compared with searching them all around the build system.

But Kconfig may not cover all the flags in command line. Flags such as compiler selections, build type and project config file, may vary in each build. It can be inconvenient to put them into Kconfig.

Best regards,

Hu Ziji

*From:* TF-M tf-m-bounces@lists.trustedfirmware.org *On Behalf Of *Adrian Shaw via TF-M *Sent:* Friday, June 12, 2020 12:24 AM *To:* Raef Coles Raef.Coles@arm.com *Cc:* tf-m@lists.trustedfirmware.org *Subject:* [TF-M] CMake flags

Hi Raef. Thanks for the presentation today.

If I remember correctly, TF-M's CMake has quite a lot of command line flags now (the ones that are set with -D). And I think this will grow in the future as more options are needed.

From a command line point of view, this is kind of annoying because the commands end up being quite long. Do you guys think something like Kconfig could help?

Adrian