On Fri, Feb 19, 2021 at 4:14 AM Philipp Klaus Krause <p...@spth.de> wrote:
> The pic ports are annoying. They never passed regression tests, they > cause trouble for the build of SDCC (see e.g. > https://sourceforge.net/p/sdcc/bugs/3140/). Two thirds of the open SDCC > bug reports are about pic-specific bugs. > > They have been unmaintained for over a decade. They depend on > unmaintained upstream gputils. > While they have users, clearly no one is willing to maintain them. > > IMO, dropping those ports would make it much easier for SDCC to move > forward. The remaining pic port users could just use an older SDCC version. > A first step would be disabling their build by default (i.e. to attempt > to build them, one would ahve to use --enable-pic14-port and > --enable-pic16-port, while currently to disable them one needs > --disable-pic14-port and --disable-pic16-port). > The sentencew ont he website "Work is in progress on supporting the > Padauk (pdk13), Microchip PIC16 and PIC18 targets." should be changed to > "Work is in progress on supporting the Padauk pdk13 target. Microchip > PIC targets are deprecated and will be removed in the future." > As a recent new user, I ran into this issue and had to disable building the pic ports through an iterative process of trial and error that involved an unsuccessful attempt to pull in gputils... It would help the 'out of the box' experience since I thought I was doing something wrong... Warner
_______________________________________________ Sdcc-user mailing list Sdcc-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sdcc-user
