Where drivers come from?

[edistskho]

I am new in CCS , the built in functions is OK make not to always check registers such as trisb, porta, intcon and so on. It help very much. But when I have to deal with keypad, LCD, I2C, onewire that only drivers are available.
My questions is "why CCS does not make libraries for peripherals?". I think the drivers are not bad but many are little amateur and unclear. May be because I am new comer in CCS.

[temtronic]

Quick answer is no one can make full drivers for every peripheral device on the market!
Think about it, hundreds of I2C and SPI chips, as well as 1wire chips, let alone the 'odd ball', propriatory devices. Then there's the 'which PIC' problem. Do you make the driver PIC specific or 'universal'?
CCS has included a LOT of drivers for free when you buy the compilers and if there isn't an exact one for your device, odds are you can modify what CCS supplies and carry on.
If you're a reasonably good C coder, you can cut your own drivers. What CCS has done with all their drivers AND example programs is to give you a great beginning or starting point !
hth
jay

[asmboy]

You may feel that a given driver is "amateur" but since the source code is there - its up to you to do it better. The CCS intrinsics however are so far beyond ANY OTHER Pic compiler that you MUST FORGIVE THAT.
to paraphrase Winston Churchill:
"CCS is the worst compiler, except for all THE REST !!"

CODE QUALITY THAT BASICALLY WORKS - IS ALL IN THE MIND OF THE BEHOLDER - OR SHOULD I SAY customer
LOL