> I try to use sdcc 2.7.0 like this:
> sdcc main.c -mpic16 -o hello.ihx
> but I get a hello.hex instead of a hello.ihx.
> Is there a reason for that ?
Probably not. SDCC/PIC16 calls the linker via
"gplink" <-Ipaths here> \
-w -r -o hello hello.o \
crt0i.o pic18f1220.lib libsdcc.lib
(in one line); gplink then adds .hex to "-o hello".
Even if SDCC passed hello.ihx, gplink would create hello.hex instead
(tried by issuing the command abone manually). So the culprit is more
likely to be gplink than SDCC, though even fixing gplink would not be
enough as SDCC does play its part.
But then, why not simply issue a
mv hello.hex hello.ihx # Unix
ren hello.hex hello.ihx # Windows