A while ago I played with several of the C compilers, including the free 
ones.

The free ones were disappointing - but you might find they work well.

I have C18 from Microchip.  This works well, but only works on the C18 
processors.   I have the full edition, but understand the student 
edition is basically the same, but simply with a few optimizations 
turned off after an initial period.

I also have the full CCS PIC-C PCWH package.   This works quite well.  
If you only want to use it from MPLAB, then you don't need the full 
version... you can buy the appropriate command line compiler for 
somewhat less...  like $150.   You can also get a linux version of 
this.   This is actually my preferred compiler for the PIC16 parts, and 
I sometimes use it for the PIC18's as well.

If you're into cheap, hobbyist C, you might want to try the MikroC.   I 
use it when I'm just hacking out some proof of concept thing, since the 
libs they include are much easier to use.  However, for larger projects, 
it doesn't seem to do as good of a job as the CCS... for instance, it 
doesn't handle large quantities of string constants well - plus 
occasionally I've had it do weird things.     The free version of MikroC 
is limited to 2k of code size - but will compile for any pic 
processor.   To purchase this, you can either pay the full $249, or 
bundle it with a development board for an effective price of $175.   I 
really like the EasyPIC development system - I have an EasyPIC4, and am 
thinking about buying a easypic5 sometime in the future.

I think if I was just going to be doing hobbyist things, I'd consider 
buying a EasyPic5 and MikroC. 

Jason Hsu wrote:
> Thanks for the suggestions on how to program microcontrollers in C
> instead of Assembly language.
>
> In the process of trying to get started, I can see why Assembly
> language is MUCH more popular among hobbyists than C.  There is
> EXCELLENT support for Assembly language.  MPLAB offers FREE and full
> functionality for Assembly language programming of microcontrollers.
>
> Most of the available tools for C for microcontrollers are very costly
> (hundreds or thousands of dollars).  The free tool PICC-LITE works for
> very few microcontrollers.  The open source tools are tricky to set up
> and are in alpha state.  I have been able to work with PICC-LITE.
> Until I can get GPUTILS to work on my Linux machine (gtkextra
> installation problems), I won't be able to use SDCC on it either.
>
> I've summarized my experience at http://www.jasonhsu.com/microcontroller.html .
>
> I'm going to try GPUTILS/SDCC in Windows next.  But before I do, what
> are the prerequisites for these programs (in addition to gcc)?
>
> Would I have an easier time with Ktechlab?  Or PiKdev/lab?  Does
> dependency hell come into play here as well?  I haven't tried these
> yet.
>
> What are my other options?
>
> Given that I would like to turn my experience in microcontrollers into
> a career and that C is much more widely used in industry than Assembly
> language, I need more experience using C for microcontrollers.  Having
> as much experience with C as I already have with Assembly language
> would help me in both my job search and in my productivity on the job.
>
>   

-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist