[xtensa] Rules for #include used in Zephyr linker script

[williamtcdns]

Are there rules in the way #include statements are used in the linker script ?

When using Xtensa sample_controller, following diff command between the toolchain linker script and Zephyr linker script shows the location of the #include statements in such a way that it can be manually replicated with a different Xtensa config:

diff -ur \
  `xt-run --show-config=config`/xtensa-elf/lib/sim/ldscripts/elf32xtensa.x \
  soc/cdns/xtensa_sample_controller/include/xtensa-sample-controller.ld

We would like to automate the process of generating the Zephyr linker script for an arbitrary Xtensa config;
to that end, is there a rule in the way #include statements are inserted in the linker script ?

[williamtcdns]

@henrikbrixandersen @dcpleung @andyross @nashif @ceolin

[dcpleung]

I don't think there is any rules. Though you need to make sure whatever is included (after preprocessing) can be parsed by the linker.