pigpio vs. wiringpi

[rzusman]

Compare and contrast...

I will be writing software in C with needs to talk to I/O , read/write SPI and I2C.

Is there any advantage of one library over the other?

[joan]

Nothing you mention would drive a choice either way. There is also http://www.airspayce.com/mikem/bcm2835/

[rzusman]

Joan -
You developed pigpio, correct?

Was this before wiringpi or after? There must be some advantage for using one over the other (speed, efficiency, memory footprint, etc.).

[FTrevorGowen]

Compare and contrast...
I will be writing software in C with needs to talk to I/O , read/write SPI and I2C.
Is there any advantage of one library over the other?

Horses for courses ... I've used both but happened to "come across" wiringPi first. Their "philosophies" are different and if you have an "Arduino background" (which I don't - my, what is now called "physical computing", background/experience goes 'way back to the Z80 and before but "ended" around the time of the "Basic Stamp") Gordon's approach with wiringPi may be easier to follow. @joan's pigpio is somewhat more comprehensive and, with her help, enabled me to do a few things that are not supported by wiringPi.
Trev.

[rzusman]

Well, I'm an embedded systems developer, generally working with 8051-based devices.
I'm used to talking directly to a port pin, and most comfortable that way, but I can learn...

This will be my first Embedded Linux project, and it's a big one - redesigning our current RabbitSemi-based system using the Compute module. I'll need both serial ports, SPI, I2C, and around 20 I/O.

[jahboater]

There must be some advantage for using one over the other (speed, efficiency, memory footprint, etc.).

Why don't you just try all three libraries for something simple at first and see how you get on? Perhaps do some measurements.
Joan is a frequent, and obviously highly knowledgeable, contributor to these forums.