problems access propeller gcc libraries
zoraster
Posts: 10
I've just started using the simpleIDE+propellergcc and it went well for a day or two but now I can't get the compiler to find the utility libraries. This is the error I get: Decision Chain.c:3:25: fatal error: simpletools.h: No such file or directory. I tried clicking on the button to add libraries but that didn't work and I also checked the paths to the libraries and that seems to be correct. What am I missing?
Comments
Can you sprinkle some fairy dust to fix my problem as well?for me also.
Johnmb
Looks like the plan is to use that instead of "propeller.h" to add support for various things such as .wav file playing and so forth.
I think I might have gone another way and instead made things like "PropBOE.h", etc., to make it even simpler for people with a certain board.
But, this way might be better for general use.
I suppose I see a value for Parallax to make this as easy as possible for people and this type of thing seems pretty good.
The primary customer of the Learn C program (links to be posted today) is Education. This customer will mostly use the Propeller Activity Board, or maybe the PropBOE. The two boards are the same, so we opted not to identify specific boards through the .h files. Also, this could've added some additional confusion between the various memory model variants. We want to keep it as simple as possible for the target customer.
If you have version 0-9-xx, use the Add Library button. Older 0-8-5 versions use the project manager to add relevant items.
One of the enhancements we are looking at going forward is Auto-Lib. Version 0-9-27 has an "Auto Include Library" checkbox in properties that is disabled by default. If you enable that, you don't need to use Add Library unless you want to Save Project As or Zip the project.
The latest version 0-9-27 which is not "publicly posted" is the latest but has a documentation bug. I'll be uploading a 0-9-28 windows version this morning for general use. Mac version doesn't seem to have the documentation bug.
Ken, thanks for your explanation.
GCC has a strong advantage, in my opinion, of being able to compile C++ code that is nearly the same size as C code
(when the library is left off). This gives you the opportunity to teach C++ object oriented concepts as well as the
traditional C approach to microcontrollers...
Yes, and that is exactly what the Arduino is all about. There has been discussion of implementing Arduino libraries (classes) for the propeller.
I discovered a long time ago that if you use C++ in a simple way (rather like object programming in Spin) it can compile to the same size as doing the same thing in C.
In fact in my experiments with this it produced byte for byte the same code as the C version. For example:
Using a C++ method like so;
Will generate exactly the same code as the object oriented C approach:
Not only that the code in the objects methods is exactly the same in both languages.
I talked to Andy about this at the OPC, and Parallax decided to teach C instead of C++ for a number of reasons:
1. Target audience is bigger for C
2. Hopefully the community will make a C++ version of simpletools library.
To me, it seems like for just a little effort, they could tap into a wider audience and gain more interest...
It would be interesting to see the resulting size and ease of use differences given some reasonable coding methodologies.