Hello,
I also suggest avoiding this, magical things happening without user
notification are bound to generate day long debugging headaches. At
least make it very clear somewhere (build output) about what linker
script is used.
For example in the final link step, which is rather terse in most cases:
LD nuttx (/some/where/board/ld.script)
Also you'll have issues with monolithic/protected builds, which have
different memory maps with even more room for customization.
If you open github pull requests and open issues for these topics please
link them here so they can be properly discussed.
Thanks,
Sebastien
Le 04/11/2022 à 22:03, Nathan Hartman a écrit :
On Fri, Nov 4, 2022 at 4:32 PM Alan C. Assis <acas...@gmail.com> wrote:
Hi Nathan,
Do you have some other idea?
"Just add another symbol" is not a good idea.
We are going to pass Linux kernel Kconfig is one day or two :-)
I think we need to simplify our Kconfig, not to make each more complex
every single day.
Could make it automatic? If linker script exists in board subdirectory we
use it. If not, we use default linker script of that arch.
This means the linker scripts have to be named consistently, since the
build system will look for the script by name.
Cheers
Nathan
