Re: Improving build system

On Tue, 13 May 2025, pozz wrote:
"[. . .]
How to choose the correct toolchain? Embedded target needs arm-gcc toolchain,
for example in
   C:\Program Files (x86)\Atmel\Studio\7.0\toolchain\arm\arm-gnu-toolchain\bin
while simulator targets needs simply gcc.
How do you choose toolchain in Makefile?  I think one trick is using the prefix.
Usually arm-gcc is arm-none-eabi-gcc.exe, with "arm-none-eabi-" prefix.  Is
there other approach?
[. . .]
[. . .]  Should I change the PATH and use arm-none-eabi- prefix?"
Buona sera!
Did you consider the technique of assigning a concrete compiler to an abstract compiler varaible in a Makefile like many projects do? For example from
checkmate-0.20/libgnugetopt-1.2/Makefile
. . .
# Makefile.in generated by automake 1.15 from Makefile.am.
# libgnugetopt-1.2/Makefile.  Generated from Makefile.in by configure.
# Copyright (C) 1994-2014 Free Software Foundation, Inc.
# This Makefile.in is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
# with or without modifications, as long as this notice is preserved.
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY, to the extent permitted by law; without
# even the implied warranty of MERCHANTABILITY or FITNESS FOR A
# PARTICULAR PURPOSE.
[. . .]
[. . .]
COMPILE = $(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(AM_CPPFLAGS) \
         $(CPPFLAGS) $(AM_CFLAGS) $(CFLAGS)
[. . .]
CC = gcc
[. . .]