Hi again stevieb. It sounds like you have the start of an O'Reilly book on the PerlPi. :-)

One thing I noticed was the number of dependencies for installing all the prerequisite modules for installing the RPi-WiringPi module. 

Warning: prerequisite GPSD::Parse 1.01 not found.
Warning: prerequisite RPi::ADC::ADS 1.01 not found.
Warning: prerequisite RPi::ADC::MCP3008 2.3604 not found.
Warning: prerequisite RPi::BMP180 2.3604 not found.
Warning: prerequisite RPi::DAC::MCP4922 2.3605 not found.
Warning: prerequisite RPi::DHT11 1.03 not found.
Warning: prerequisite RPi::DigiPot::MCP4XXXX 2.3604 not found.
Warning: prerequisite RPi::I2C 2.3604 not found.
Warning: prerequisite RPi::LCD 2.3603 not found.
Warning: prerequisite RPi::Pin 2.3603 not found.
Warning: prerequisite RPi::SPI 2.3607 not found.
Warning: prerequisite RPi::Serial 2.3602 not found.
Warning: prerequisite RPi::WiringPi::Constant 1 not found.
Warning: prerequisite WiringPi::API 2.3613 not found.
Generating a Unix-style Makefile

[download]

Additionally cpan didn't want to install automatically. When I try "cpan install RPi-WiringPi" it returns without finding the module. You need to use "cpan install RPi::WiringPi", and even then a bunch of errors are generated in the cpan tests regarding an unknown error in installing WiringPi::API . It would be nice if you made a Bundle:RPi or something similar.

I finally read that you need to install WiringPi C lib first, before installing WiringPi::API. Then I also needed to manually install RPi-Pin-2.3603. Other than those glitches, it all installed fine.

My next project is driving a 64x32 led display. :-)

I think you ought to look for a publisher.

I'm not really a human, but I play one on earth. ..... an animated JAPH

In reply to Re: Contemplating a documentation series for my Raspberry Pi work by zentara
in thread Contemplating a documentation series for my Raspberry Pi work by stevieb

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.