Shop OBEX P1 Docs P2 Docs Learn Events
SimpleIDE for Raspberry Pi — Parallax Forums

SimpleIDE for Raspberry Pi

RsadeikaRsadeika Posts: 3,837
edited 2016-10-06 17:11 in Propeller 1
I just tried the installation process via the Learn site, and it keeps showing me a 502 error, when I try to download. The download process does work when you do it through the store site.

Any indication as to when SimpleIDE 0-9-45 for the Raspberry Pi will be updated? It is getting to be older than dirt. :-)

<edit: I removed the " ...Error 502" from the thread title, all is good now.>

Ray
«1

Comments

  • I fixed the broken link on Learn, but I do not know the answer to when or if it will be updated.

    I will direct the question to our development team and point them to this thread.
  • Maybe you should of left the link broken...

    I was looking for sirc.h lib, in the "Add Simple Library", for the Raspberry Pi version of SimpleIDE, and I cannot find it. After further inspection, there is a lot of "stuff" that is missing in the SimpleIDE for Raspberry Pi. If Parallax is not going to support the software, especially SimpleIDE for Raspberry Pi, then maybe you should just pull it off the download list? Don't forget to make an announcement that the software is being pulled, so everybody can make some different arrangements.

    What is going with Parallax?

    Ray
  • Unlike the other OS variants, which are at versions 1.0 RC1 & RC2, SimpleIDE for RaspberryPi is at version 0-9-45 (a Beta version)... Unfortunately, I 'think' this had to do with Qt5 not being available on RaspberryPi at the time of RC1 & RC2 releases. SimpleIDE's RC1 & RC2 versions are dependent on Qt5 (now available on RPi). Also, the Learn folder content of pre-v0-9-64 versions, may be out of date, with fewer available libraries!

    You can copy over the newer Learn Folder "Remote" directory from any of the RC1 or RC2 repositories to your Raspberry Pi's "~/Documents/SimpleIDE/Learn/Simple Libraries" directory and it will work (I tested this).

    Note to Courtney: Looks like the links for the Learn Folders (pre & post v0-9-64) are also giving Error 502, at least some of the time. Makes it hard to update Ray's Learn folder to include the Remote libraries.

    Yes, unfortunate that all the SimpleIDE versions are not sync'd... But, not the end of the world :-)

    dgately
  • The Learn team is working to correct the 502 errors, we appreciate you bringing our attention to them.

    Additional information on SimpleIDE for RaspberryPi will be released when it's available.
  • I thought at one time, SimpleIDE had a feature that would update the Simple Library automatically, or am I thinking of some different software?

    I guess it is for the better that the feature no longer exits, it could look kind of daunting if you kept getting the 502 error every time it tried an auto update.

    A couple of years back their was talk about SimpleIDE improvements?, but I guess the latest would be the 502 error, I guess that is a feature or is that an improvement...

    Ray
  • dgatelydgately Posts: 1,630
    edited 2016-10-06 15:46
    Rsadeika wrote: »
    I thought at one time, SimpleIDE had a feature that would update the Simple Library automatically, or am I thinking of some different software?

    That feature showed up in RC1 & RC2 and still exists on Windows, Linux & Mac OS releases... It's not in version 0-9-45, which was the only released RaspberryPi version.

    EDIT: I hate to say this but, building your own SimpleIDE from the git sources, on the Raspberry Pi might be the better method to get what you want (sorry...).


    dgately
  • SimpleIDE for Mac, Linux, and Windows have the "Update Your Workspace" feature. It was released with v1.0 RC1.

    See release details here: SimpleIDE Version Info

    While you're welcome to express constructive criticism and to contribute meaningful suggestions to the community that supports the SimpleIDE for Raspberry Pi software, being negative and rude is disrespectful and will result in moderation.

    SimpleIDE for the Raspberry Pi is an open-source community initiative (as stated on the installation page). Ongoing support is provided by interested community members here on our forums. A list of the key contributors/developers for this software can be found at the bottom of the SimpleIDE for the Raspberry Pi installation page. I have already brought your original question to the attention of our lead software engineer, any information we have about future releases and/or fixes for the SimpleIDE for Raspberry Pi software will be provided as it becomes available.
  • You may run into issues with the compiler that is shipped with SimpleIDE 0.9.45, but you can use the latest Learn libraries by following PropWare's instructions for SimpleIDE: http://david.zemon.name/PropWare/#/download
    At the top of that page is instructions for using PropWare with SimpleIDE, and PropWare ships with the latest Learn folder... so that would work for you :)
  • While you're welcome to express constructive criticism and to contribute meaningful suggestions to the community that supports the SimpleIDE for Raspberry Pi software, being negative and rude is disrespectful and will result in moderation.
    Yes, I got it.
    SimpleIDE for the Raspberry Pi is an open-source community initiative (as stated on the installation page). Ongoing support is provided by interested community members here on our forums.
    This was the official Parallax statement that I was looking for, I will quit holding my breath now.

    As for the latest Simple Library for, SimpleIDE for Raspberry Pi, I solved that problem.

    Ray
  • dgatelydgately Posts: 1,630
    edited 2016-10-06 18:33
    For any DIY'ers:

    Here's a top-of-the-source-tree SimpleIDE built and running on a RaspberryPi 2B:
    SimpleIDE%20v1.jpg

    Here's the newer "Update Workspace" menu:
    SimpleIDE%20v1%20Workspace.jpg

    Here's the Sony Remote example project built with SimpleIDE v1 on RPi:
    SonyRemoteOnRPi.jpg

    Steps:
    1. Start with a recent RPi installation (2016-09-23-raspbian-jessie.img from the raspberry.org Download page)
    2. Install git, cmake, qt5-qmake, qtcreator with (she may already be installed on RPi Raspian Jessie):
    sudo apt-get install -y git
    sudo apt-get install -y cmake
    sudo apt-get install -y qt5-qmake
    sudo apt-get install -y qtcreator
    3. Download most-recent SimpleIDE source with git:
    mkdir ~/source
    cd ~/source
    git clone --recursive https://github.com/parallaxinc/SimpleIDE.git
    4. Launch Qt Creator from the RaspberryPi Programming menu
    5. Setup the proper compiler kit:
    Select the Options item from the Qt Creator Tools menu
    Select the Build & Run options (left side)
    Select the Compilers tab
    Add a GCC compiler (Add button contains several options)
    Set its PATH to /usr/bin/gcc and click the Apply button
    Select the Qt Versions TAB and check that an Auto-detected qmake path is now visible
    Click OK
    6. Open the propside project in Qt Creator, which is in the git source you downloaded: ~/source/SimpleIDE/propside/propside.pro (on my RPi)
    7. Allow QT Creator to setup the project and bring up the Edit window
    8. Build the project, run it in debug mode to check it out
    9. Build a Release version of the project, find its files and copy them to appropriate directories

    Notes:

    The SimpleIDE project depends on propgcc to be pre-installed. Since I had already installed the previous SimpleIDE 0-9-45 version, the propgcc compiler and all its files had already been installed in /opt/parallax/...

    I also had updated the latest Simple Libraries Folder from GitHub and renamed it in the ~/Documents directory:
    cd ~/Documents
    git clone --recursive https://github.com/parallaxinc/Simple-Libraries.git
    mv Simple-Libraries SimpleIDE

    There are scripts within the SimpleIDE project that assist in packaging the application up for Linux, but I'll leave that for another thread/post.

    I may have missed a step or two, so post comments, I'll update and possibly post this to the SimpleIDE git repository.

    dgately

    614 x 474 - 83K
    614 x 474 - 80K
    614 x 474 - 81K
  • Heater.Heater. Posts: 21,230
    One should not need qtcreator and all that messing with compiler kits etc.

    After cloning the repository:
    $ git clone --recursive https://github.com/parallaxinc/SimpleIDE.git
    
    It should just be a simple:
    $ cd SimpleIDE
    $ qmake
    $ make
    
    That is how it used to work. I have not tried for a while. I hope nothing has broken since then.

    Of course prop-gcc should be installed first.



  • Heater. wrote: »
    One should not need qtcreator and all that messing with compiler kits etc.

    Why do it the "simple way"? When you can use a GUI solution that takes thrice as long and uses 10X more steps :zombie:

    Thanks, Heater!

    dgately
  • Since I purchased the Raspberry Pi 3, and running SimpleIDE on it, I found that to be a very good alternative platform to work with. Also, since the unit has built in WiFi, this makes it very easy to get online.

    Having said that, I am wondering if somebody could check something out for me. Since I do not have a PropellerHAT for the Raspberry Pi, and I prefer using C, does SimpleIDE work with the PropellerHAT? Hopefully somebody could physically check this out instead of theorizing the capability, or make alternate software usage suggestions.

    Since, "SimpleIDE for the Raspberry Pi is an open-source community initiative..." now, as officially described by Parallax, and if their has to be changes made to make it work with the PropellerHAT, using that as an example, is this software still useable for my skill level? The problem that I am thinking about is the capability of SimpleIDE to use /dev/ttyAMA0, in order to program the PropellerHAT. The last time I tried to use /dev/ttyAMA0, their was some problems, it did not work.

    I guess this should be easy enough to resolve for any skill level set, right? Hopefully this post meets with the "being negative and rude is disrespectful and will result in moderation" compliance.

    Ray
  • Rsadeika wrote: »
    Since I purchased the Raspberry Pi 3, and running SimpleIDE on it, I found that to be a very good alternative platform to work with. Also, since the unit has built in WiFi, this makes it very easy to get online.

    Having said that, I am wondering if somebody could check something out for me. Since I do not have a PropellerHAT for the Raspberry Pi, and I prefer using C, does SimpleIDE work with the PropellerHAT? Hopefully somebody could physically check this out instead of theorizing the capability, or make alternate software usage suggestions.

    Since, "SimpleIDE for the Raspberry Pi is an open-source community initiative..." now, as officially described by Parallax, and if their has to be changes made to make it work with the PropellerHAT, using that as an example, is this software still useable for my skill level? The problem that I am thinking about is the capability of SimpleIDE to use /dev/ttyAMA0, in order to program the PropellerHAT. The last time I tried to use /dev/ttyAMA0, their was some problems, it did not work.

    I guess this should be easy enough to resolve for any skill level set, right? Hopefully this post meets with the "being negative and rude is disrespectful and will result in moderation" compliance.

    Ray
    I guess the main problem would be with resetting the RaspberryPi. I don't have a RaspberryPi 3 but I think I have a Propeller had and a RaspPi2. Are there any GPIO changes between the 2 and the 3?

  • Are there any GPIO changes between the 2 and the 3?
    Not that I am aware of. Now that I think about it, their has always been a problem with how SimpleIDE works with the ports. Some times it finds the port(Propeller chip) and some times it does not find the port(Propeller chip). So, you end up hitting Run multiple times to get access to Propeller, this gets to be a little tedious after awhile.

    Ray
  • pmrobertpmrobert Posts: 673
    edited 2016-10-07 14:20
    I have a Hat on a Pi2B that works fine. I also have a 3 I would like to get the Hat working on as well but they have the hardware UART connected to the Bluetooth hardware but I haven't had the spare time to reconfigure the Pi to put the hardware UART back on the appropriate pins. I'm not confident that the bitbang scheme on the stock Pi3/Raspbian serial I/O will work for my app which sends a lot of data at 230.4k between the Pi and Hat.

    -Mike

    Addit: raspberrypi.stackexchange.com/questions/45570/how-do-i-make-serial-work-on-the-raspberry-pi3
  • pmrobert wrote: »
    I have a Hat on a Pi2B that works fine. I also have a 3 I would like to get the Hat working on as well but they have the hardware UART connected to the Bluetooth hardware but I haven't had the spare time to reconfigure the Pi to put the hardware UART back on the appropriate pins. I'm not confident that the bitbang scheme on the stock Pi3/Raspbian serial I/O will work for my app which sends a lot of data at 230.4k between the Pi and Hat.

    -Mike

    Addit: raspberrypi.stackexchange.com/questions/45570/how-do-i-make-serial-work-on-the-raspberry-pi3
    Well, having Bluetooth occupying the UART would certainly cause problems. Is there only one UART on the ARM chip?

  • Heater.Heater. Posts: 21,230
    OK. What is going on here. I remember having the conversation about the use of /dev/ttyAMA0 on the Pi with Steve Denson years and years ago. I thought it got fixed at some point.

    Or an I confusing things with the use of /dev/ttyAMA0 by the loader in prop-gcc?

    Either way it was working at some point.

    Also what happened to the Finnish language translation my friend Matti contributed years ago? That seems to have gone missing.
  • The Raspberry Pi 3 has a built in Bluetooth, along with WiFi. The PropellerHAT uses the /dev/ttyAMA0 connection, which is the only UART on the GPIO. Of course, because it has four USB ports, you are able to use /dev/ttyUSB0, ..., etc.

    My concern was, and still is, the use of /dev/ttyAMA0 with SimpleIDE, as a specific problem, and the weird usage of /dev/ttyUSBxx ports when trying to Run a program with a propeller device attached.

    Ray
  • Rsadeika wrote: »
    The Raspberry Pi 3 has a built in Bluetooth, along with WiFi. The PropellerHAT uses the /dev/ttyAMA0 connection, which is the only UART on the GPIO. Of course, because it has four USB ports, you are able to use /dev/ttyUSB0, ..., etc.

    My concern was, and still is, the use of /dev/ttyAMA0 with SimpleIDE, as a specific problem, and the weird usage of /dev/ttyUSBxx ports when trying to Run a program with a propeller device attached.

    Ray
    The current version of propeller-load certainly supports /dev/ttyAMA0. I'm not sure about the version that comes with SimpleIDE.

  • pmrobertpmrobert Posts: 673
    edited 2016-10-07 15:25
    Good question, no idea why the simpleIDE stuff is a little out of sorts on the Pi, in my experience. The Hat does use GPIO 17 to toggle reset on the PiProp, this is for sure different than loading via the standard serial DTR toggle. The only loader I've gotten to work simply and reliably is one off Bill Henning's mikronauts.com. To be fair, I use Visual Code on a PC to edit and compile then use Bitvises sftp & sexec to run a bash batch file containing "sudo ./propeller-load3 -D clkfreq=96000000 -D clkmode=XTAL1+PLL16X -r -p /dev/ttyAMA0 pgccefi-$1.elf" on the Pi.

    Mike
  • pmrobert wrote: »
    Good question, no idea why the simpleIDE stuff is a little out of sorts on the Pi, in my experience. The Hat does use GPIO 17 to toggle reset on the PiProp, this is for sure different than loading via the standard serial DTR toggle. The only loader I've gotten to work simply and reliably is one off Bill Henning's mikronauts.com. To be fair, I use Visual Code on a PC to edit and compile then use Bitvises sftp & sexec to run a bash batch file containing "sudo ./propeller-load3 -D clkfreq=96000000 -D clkmode=XTAL1+PLL16X -r -p /dev/ttyAMA0 pgccefi-$1.elf" on the Pi.

    Mike
    I have no idea how propeller-load3 differs from the standard propeller-load but the current source for propeller-load on github should support using any GPIO to reset the RaspberryPi.

  • pmrobertpmrobert Posts: 673
    edited 2016-10-07 15:41
    Ahh, there must be the cause of my past issues. The last time I tried Simple on the Pi was quite a while ago and it was less than optimal, that's why I switched to compiling on PC, FTPing the .elf over to the Pi then loading the .elf to the Prop. I'm perfectly happy with my current dev environment, though definitely not simple, but will grab the latest propeller-load off Github and give it a shot. Bill's version works fine but doesn't come with source. I like source.

    Thanks, David!
  • pmrobert wrote: »
    Ahh, there must be the cause of my past issues. The last time I tried Simple on the Pi was quite a while ago and it was less than optimal, that's why I switched to compiling on PC, FTPing the .elf over to the Pi then loading the .elf to the Prop. I'm perfectly happy with my current dev environment, though definitely not simple, but will grab the latest propeller-load off Github and give it a shot. Bill's version works fine but doesn't come with source. I like source.

    Thanks, David!
    I tend to use command line tools myself. Or are you using SimpleIDE on the PC?

  • No, I'm using Visual Code, batch files and hopefully the latest version of PropGCC.
    @echo off
    set memmodel=lmm
    set optimization=-Os
    set fcache=-mfcache
    echo Options: %memmodel%, %optimization%, %fcache%
    echo                          Compiler Output
    echo                          ===============
    propeller-elf-gcc.exe -save-temps -s -I . -L . -I ./SimpleLibraries/Utility/libsimpletools -L ./SimpleLibraries/Utility/libsimpletools/%memmodel%/ -I ./SimpleLibraries/TextDevices/libsimpletext -L ./SimpleLibraries/TextDevices/libsimpletext/%memmodel%/ -I ./SimpleLibraries/Protocol/libsimplei2c -L ./SimpleLibraries/Protocol/libsimplei2c/%memmodel%/ -I ./SimpleLibraries/TextDevices/libfdserial -L ./SimpleLibraries/TextDevices/libfdserial/%memmodel%/ -o %1-%memmodel%.elf %optimization% -m%memmodel% %fcache% -Wall -m32bit-doubles -fno-exceptions -std=c99 -ffunction-sections -fdata-sections -Wl,--gc-sections %1.c -lsimpletools -lsimpletext -lsimplei2c -lfdserial -lsimpletools -lsimpletext -lsimplei2c -lsimpletools -lsimpletext -lsimpletools -ltiny 
    
    
    if not "%errorlevel%" == "0" (
    	echo Compilation Error
    	rem pause
    	goto exit
    	)
    
    if "%2" == "s" (
    	echo.
    	propeller-elf-size -A -d -t pgccefi-%memmodel%.elf
    	pause
    	goto exit
    	)
    
    sftpc -bg -profile=f:\pmrobert\documents\pi.bscp -cmd="put %1-%memmodel%.elf -o"
    if not "%errorlevel%" == "0" (
    	echo ""sftp"" to rpi failed. Errorlevel: %errorlevel%
    	pause
    	goto exit
    	)
    	astyle pgccefi.c
    	sexec -profile=f:\pmrobert\documents\pi.bscp -cmd="./load.sh %memmodel%"
    rem sexec -profile=f:\pmrobert\documents\pi.bscp -cmd="sudo ./propeller-load3 -D clkfreq=96000000 -D clkmode=XTAL1+PLL16X -r -p /dev/ttyAMA0 %1-%memmodel%.elf"
    if not "%errorlevel%" == "1000" (
    	echo ""sexec"" to rpi failed. Errorlevel: %errorlevel%
    	pause
    	goto exit
    	)
    
    
    :exit
    rem sexec -profile=f:\pmrobert\documents\pi.bscp -cmd="./runfpc.sh"
    

    on PC side and a small shell file on the Pi.
    echo Memory Model: $1
    sudo ./propeller-load3 -D clkfreq=96000000 -D clkmode=XTAL1+PLL16X -r -p /dev/ttyAMA0 pgccefi-$1.elf
    sleep 2
    ./ecucom pdsa
    




  • I got tired of the zillion -I and -L options needed on the command line so I created a Makefile that would build all of the Simple Libraries and put all of the .h files in one directory and all of the .a files in another. That way my command lines have just one -I and one -L.
  • David Betz wrote: »
    I got tired of the zillion -I and -L options needed on the command line so I created a Makefile that would build all of the Simple Libraries and put all of the .h files in one directory and all of the .a files in another. That way my command lines have just one -I and one -L.
    That sounds like a great idea! Care to share?

  • Heater.Heater. Posts: 21,230
    edited 2016-10-07 16:52
    The GPIO 17 reset thing was my original hack to the prop-gcc loader. Which Mikronaughts adopted just to be able to get something done.

    Since then it got generalized to any GPIO.

    Turned out to be a useful hack if you were using something other than a Pi. Like a cheap MIPS based router box.

    No idea what happened after that. I'm a bit out of touch. I just worry that SimpleIDE has been retrograding since then.

  • pmrobert wrote: »
    David Betz wrote: »
    I got tired of the zillion -I and -L options needed on the command line so I created a Makefile that would build all of the Simple Libraries and put all of the .h files in one directory and all of the .a files in another. That way my command lines have just one -I and one -L.
    That sounds like a great idea! Care to share?

    http://david.zemon.name:8111/repository/download/PropWare_Develop/1487:id/PropWare-3.0.0.106-Generic-propware.zip
    That link contains only the libraries and header files for PropWare. Here's the output from tree, with the contents of the PropWare and libpropeller folders trimmed:
    ~/tmp/PropWare$ tree -L 2
    .
    ├── include
    │   ├── abcalibrate.h
    │   ├── abdrive.h
    │   ├── abvolts.h
    │   ├── Adafruit_GFX.h
    │   ├── adcACpropab.h
    │   ├── adcDCpropab.h
    │   ├── Arduino.h
    │   ├── badgetools.h
    │   ├── binary.h
    │   ├── colorpal.h
    │   ├── compass3d.h
    │   ├── dacctr.h
    │   ├── datetime.h
    │   ├── fdserial.h
    │   ├── gps.h
    │   ├── Interval.h
    │   ├── libpropeller
    │   ├── Max72xxPanel.h
    │   ├── mma7455.h
    │   ├── mstimer.h
    │   ├── mx2125.h
    │   ├── nonstdlib.h
    │   ├── ping.h
    │   ├── Printable.h
    │   ├── Print.h
    │   ├── PropWare
    │   ├── rfidser.h
    │   ├── serial.h
    │   ├── Serial.h
    │   ├── servoAux.h
    │   ├── servodiffdrive.h
    │   ├── servo.h
    │   ├── Servo.h
    │   ├── simplei2c.h
    │   ├── simpletext.h
    │   ├── simpletools.h
    │   ├── sirc.h
    │   ├── sound.h
    │   ├── soundimpact.h
    │   ├── SPI.h
    │   ├── stacktest.h
    │   ├── Stepper.h
    │   ├── Stream.h
    │   ├── text2speech.h
    │   ├── vgatext.h
    │   ├── wavplayer.h
    │   ├── WCharacter.h
    │   ├── Wire.h
    │   ├── ws2812.h
    │   └── WString.h
    ├── lib
    │   ├── cmm
    │   ├── cog
    │   ├── lmm
    │   ├── PropWare-targets.cmake
    │   ├── PropWare-targets-noconfig.cmake
    │   ├── xmmc
    │   ├── xmm-single
    │   └── xmm-split
    └── version.txt
    
    10 directories, 51 files
    dzweb@davidzemonname:~/tmp/PropWare$ tree lib
    lib
    ├── cmm
    │   ├── libLibpropeller.a
    │   ├── libLibPropelleruino.a
    │   ├── libPropWare.a
    │   └── libSimple.a
    ├── cog
    │   ├── libLibpropeller.a
    │   ├── libLibPropelleruino.a
    │   ├── libPropWare.a
    │   └── libSimple.a
    ├── lmm
    │   ├── libLibpropeller.a
    │   ├── libLibPropelleruino.a
    │   ├── libPropWare.a
    │   └── libSimple.a
    ├── PropWare-targets.cmake
    ├── PropWare-targets-noconfig.cmake
    ├── xmmc
    │   ├── libLibpropeller.a
    │   ├── libLibPropelleruino.a
    │   ├── libPropWare.a
    │   └── libSimple.a
    ├── xmm-single
    │   ├── libLibpropeller.a
    │   ├── libLibPropelleruino.a
    │   ├── libPropWare.a
    │   └── libSimple.a
    └── xmm-split
        ├── libLibpropeller.a
        ├── libLibPropelleruino.a
        ├── libPropWare.a
        └── libSimple.a
    
    6 directories, 26 files
    

    This should hopefully prove useful for anyone who wants to use the Learn folder and/or PropWare libraries, but doesn't want to use PropWare's build system.
  • DavidZemon wrote: »
    pmrobert wrote: »
    David Betz wrote: »
    I got tired of the zillion -I and -L options needed on the command line so I created a Makefile that would build all of the Simple Libraries and put all of the .h files in one directory and all of the .a files in another. That way my command lines have just one -I and one -L.
    That sounds like a great idea! Care to share?

    http://david.zemon.name:8111/repository/download/PropWare_Develop/1487:id/PropWare-3.0.0.106-Generic-propware.zip
    That link contains only the libraries and header files for PropWare. Here's the output from tree, with the contents of the PropWare and libpropeller folders trimmed:
    ~/tmp/PropWare$ tree -L 2
    .
    ├── include
    │   ├── abcalibrate.h
    │   ├── abdrive.h
    │   ├── abvolts.h
    │   ├── Adafruit_GFX.h
    │   ├── adcACpropab.h
    │   ├── adcDCpropab.h
    │   ├── Arduino.h
    │   ├── badgetools.h
    │   ├── binary.h
    │   ├── colorpal.h
    │   ├── compass3d.h
    │   ├── dacctr.h
    │   ├── datetime.h
    │   ├── fdserial.h
    │   ├── gps.h
    │   ├── Interval.h
    │   ├── libpropeller
    │   ├── Max72xxPanel.h
    │   ├── mma7455.h
    │   ├── mstimer.h
    │   ├── mx2125.h
    │   ├── nonstdlib.h
    │   ├── ping.h
    │   ├── Printable.h
    │   ├── Print.h
    │   ├── PropWare
    │   ├── rfidser.h
    │   ├── serial.h
    │   ├── Serial.h
    │   ├── servoAux.h
    │   ├── servodiffdrive.h
    │   ├── servo.h
    │   ├── Servo.h
    │   ├── simplei2c.h
    │   ├── simpletext.h
    │   ├── simpletools.h
    │   ├── sirc.h
    │   ├── sound.h
    │   ├── soundimpact.h
    │   ├── SPI.h
    │   ├── stacktest.h
    │   ├── Stepper.h
    │   ├── Stream.h
    │   ├── text2speech.h
    │   ├── vgatext.h
    │   ├── wavplayer.h
    │   ├── WCharacter.h
    │   ├── Wire.h
    │   ├── ws2812.h
    │   └── WString.h
    ├── lib
    │   ├── cmm
    │   ├── cog
    │   ├── lmm
    │   ├── PropWare-targets.cmake
    │   ├── PropWare-targets-noconfig.cmake
    │   ├── xmmc
    │   ├── xmm-single
    │   └── xmm-split
    └── version.txt
    
    10 directories, 51 files
    dzweb@davidzemonname:~/tmp/PropWare$ tree lib
    lib
    ├── cmm
    │   ├── libLibpropeller.a
    │   ├── libLibPropelleruino.a
    │   ├── libPropWare.a
    │   └── libSimple.a
    ├── cog
    │   ├── libLibpropeller.a
    │   ├── libLibPropelleruino.a
    │   ├── libPropWare.a
    │   └── libSimple.a
    ├── lmm
    │   ├── libLibpropeller.a
    │   ├── libLibPropelleruino.a
    │   ├── libPropWare.a
    │   └── libSimple.a
    ├── PropWare-targets.cmake
    ├── PropWare-targets-noconfig.cmake
    ├── xmmc
    │   ├── libLibpropeller.a
    │   ├── libLibPropelleruino.a
    │   ├── libPropWare.a
    │   └── libSimple.a
    ├── xmm-single
    │   ├── libLibpropeller.a
    │   ├── libLibPropelleruino.a
    │   ├── libPropWare.a
    │   └── libSimple.a
    └── xmm-split
        ├── libLibpropeller.a
        ├── libLibPropelleruino.a
        ├── libPropWare.a
        └── libSimple.a
    
    6 directories, 26 files
    

    This should hopefully prove useful for anyone who wants to use the Learn folder and/or PropWare libraries, but doesn't want to use PropWare's build system.
    I didn't combine all of the Simple Libraries into a single libSimple.a file so David's solution may be preferable to mine.

This discussion has been closed.