I've been really busy with "real work" so I've been unable to contribute=
for a while. However, I've been following the trials and tribulations of=
those attempting to reconcile the build procedures. I have a suggestion=
which will probably invoke much hate mail, but here goes.
Make the build procedure in the fashion of gcc. That is, configure SDCC=
for a particular processor/family and create separate compilers,=
utilities, debugger and libraries for each.
Sandeep - Opinion ?
............Now I duck and cover..............(Bullets and mortars fly=
With the 8051, DS390, Z80, AVR and PIC ports already in process and talk of=
the XA51 port and my intention to add the HC05 and HC08 and possibly the=
ST7 families to the pot soon, we are starting to see some feature and=
options interactions as well as "exe bloat". I understand that this can=
currently be done by configuring out particular ports and creating=
different directories and naming conventions for the executables etc. But=
who wants to do that manually. The people using this "product" are either=
coming from a Win/DOS environment, where you generally buy a tool set for=
a particular processor or they are coming from the Linux side with the=
experience of gcc with the various ports available.
I don't think much work would have to be done on the compiler side as the=
compiler <--> port interface is simpler in a single processor environment.=
The configure/makefiles will require some work but it is do-able.
P.S. : For those wanting to nuke me personally, I will NOT be in Belgium=
next week and will definitely NOT be at CEBIT the week after so don't=
bother looking for me there.