From: Scott D. <sc...@da...> - 2003-04-23 02:22:45
|
On Tue, 22 Apr 2003, Harpo Maxx wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > El Tue, Apr 22, 2003 at 04:54:57PM +0300, ri...@uc... dijo: > > > These are really bad news! :( i had the idea of implementing a > > > GPL/OpenSource tcp/ip library a year ago, but I couldn't found a GPL/OS C > > > compiler for the Pic at that time. But now thing are changing... the > > > sdcc's pic port is on the way... > > > > There is already an OpenSource TCp/IP stack (o; > > > > Check at our website: > > > > http://www.opentcp.org/ > > Yes, but I don't see plans for a pic port there...:( > > > When a talk to the people about my plans of tcp/ip implementation for the > pic14 using a C compiler... all of they say me its gonna be very dificult... > > What do you think? I'll tell you why it's going to be difficult (but it's getting easier). Today I commit'd a big change in CVS that adds support for object files in the PIC port. Up until now, your projects could consist of only single .c since the PIC port was only generating absolute mode .asm code. As it stands, you still can only have projects with a single .c file, but at least SDCC will generate relocatable .asm code. The point is that the PIC port is simply not as mature as the other ports and I suspect that there are fundamental things that are still broken and prevent a large project like yours from working. OTOH, porting a large project like yours would certainly expose all of the weaknesses of the PIC port and (hopefully) lead to bug reports. Scott |