#include "simpletools.h" throws "No such file or directory"
John Kauffman
Posts: 653
#include "simpletools.h" throws compile error "No such file or directory"
I was under the impression that all the simplexxx.h were available without spec of path. But reference to it throws above error.
simpletools.h exists in C:\Users\John Kauffman\Documents\SimpleIDE\Learn\Simple Libraries\Utility\libsimpletools
I'm running (without modification) the Sense Light.c sample program form the Learn C tutorials: C:\Users\John Kauffman\Documents\SimpleIDE\Learn\Examples\circuits
I was under the impression that all the simplexxx.h were available without spec of path. But reference to it throws above error.
simpletools.h exists in C:\Users\John Kauffman\Documents\SimpleIDE\Learn\Simple Libraries\Utility\libsimpletools
I'm running (without modification) the Sense Light.c sample program form the Learn C tutorials: C:\Users\John Kauffman\Documents\SimpleIDE\Learn\Examples\circuits
Comments
I was having this problem yesterday after installing a new release on my Mac (I had installed and removed and reinstalled many of the early SimpleIDE releases during the Alpha testing). My solution was to make sure that the library folder field in the preferences panel pointed to Documents/SimpleIDE. That seemed to clear everything up for me.
I just loaded and compiled Sense Light.c set up like this, so it is working for me currently.
Hope this helps!
1) The GCC Folders tab "Library Folder" must be set: I.E. C:/Users/Steve/Documents/SimpleIDE/Learn/Simple Libraries
2) The General tab "Auto Include Simple Libraries" must be checked.
These items should get set automatically in the latest package. You can check them by opening Properties.
The Properties dialog can be opened using the tool-bar wrench, pressing F6, or selecting Menu -> Tools -> Properties.
This information should be added to the User Guide.
John,
In addition to the things already said, I'd like to verify that you renamed, moved, or deleted your original <user>\My Documents\Simple IDE\ folder path before starting the version of SimpleIDE you're using. If you do that, then start SimpleIDE, it will recreate that folder/file structure for you based on the latest Simple Library fileset included with the SimpleIDE install.
Otherwise, you could be using older versions of the libraries that don't match the current capabilities of the software nor the current tutorials posted on our learn.parallax.com website.
A near-future release of the software will make this set of steps more automatic and friendly.
I can get it to compile the files by including all the Simple Library subdirectories with -I as below, but the link step doesn't work. I have to include the whole directory up to and including /lmm as below (which breaks it if I want to switch easily between lmm an cmm, for example) in the -L, and it can find the library file, but it complains that it can't find the modules in the file.
For completeness, here's the input file (t.c) that generated the above:
If someone can help me make it work, I will help with whatever glue is necessary and document it for anyone else wanting to do such a thing.
David Voss
If not, we need to understand why not.
https://code.google.com/p/propside/downloads/list
David (altosack)
I found some free time ....
You must add -l entries after the .c entry on the command line. For example:
propeller-elf-gcc t.c -o t.elf -mcmm -Wall -m32bit-doubles -Os -I . -L . -I "/Users/steve/Documents/SimpleIDE/Learn/Simple Libraries/Text Devices/libsimpletext" -L "/Users/steve/Documents/SimpleIDE/Learn/Simple Libraries/Text Devices/libsimpletext"/cmm -lsimpletext
Here is a very simple Makefile.
Thanks also for the reminder about .../$(MODEL); I of course was already using $(MODEL) for other things in my Makefile, but it hadn't (yet) occured to me to apply it to the library search path.
I promised a while back to write a tutorial on using a Makefile with propgcc development, but I never delivered. Maybe I'll look again at doing that, of course with a detractor in the beginning suggesting that most people would be happier with SimpleIDE (it just keeps getting better). I still have my reasons for using a Makefile, though.