4 ms·
You have to use their XC dialect, but it is mostly C anyway. And you can include reglar h-files to easily link to and build regular C. With provided macros yo
by tjoff 7y ago
You have to use their XC dialect, but it is mostly C anyway.
And you can include reglar h-files to easily link to and build regular C. With provided macros you can have h-files which are using some XC features but still be compatible with both XC and C files (making it easy to wrap XC code and call it from C and vice versa).
There is also this that can use XC features from C. https://github.com/xmos/lib_xcore_c https://github.com/xmos/lib_xcore_c
But I don't find XC to be bad, and likely a much better starting point than the library above.
The compiler is a fork from gcc from 2006 (if I remember correctly) and that shows its age somewhat. The many protections in XC can be a bit tedious as well.
- cmrdporcupine 7y agoI had existing code written in C++. I ran it using GCC on the Parallax Propeller instead. I had no desire to port to XC as I was trying to keep a core of it relatively cross platform. Of course this is just another of my unfinished hobby projects, so :-)