To my personal observations many libs (e.g., openVG) use make, and IIRC I also sometimes have seen installation guides which have been using makefile. I can't remember if I have ever seen cmake, but I'm quite sure that make and makefile have been used more often than cmake AFAIK. Anyway, IMO it's no...
there are also the very convenient wiringPi libs, feat. wiringPiI2C. https://projects.drogon.net/raspberry-pi/wiringpi/i2c-library/ Arduino Wire is C++, wiringPi is C, but both are similar and quite intuitive by usage though. Gordon Henderson also provides a tutorial for using his libs. Nevertheless...
first of all the things what people want having a Pi and being new to C, is simply to write programs which do something awesome. No one is supposed to be a nerd who's intention is to become a native C speaker . The application is which comes first, Sh*t on C only to the senseless self-satisfaction. ...
[MOD EDIT - PROFANITY REMOVED], for Arduino there are tutorials I have learnt from to control the Arduino digital and analog pins. Also libs for hardare access (shields, sensors) are available, But nothing for C to control Pi hardware and/or accessories. But actually I think you do not want to under...
hell no, what a nonsense. Actually they are the best people to do it. They learn for themselves and then write it up without making the assumptions a guru would make. porting that to education in general, that would mean: no one would need teachers, no primary school, no highschool, no professors, n...
joan has a few tutorials, well not tutorials but examples, on the pigpio website for GPIO and other things. If somebody who is good at writing tutorials expanded on the examples it might bridge that middle ground gap. yes I know, and you're right, beginners don't need repositories, they need tutori...
haha, that's an extremely 1-dimensional point of view with a minor radius to the horizon
(or did you misunderstand, that is not meant to be a schedule, 1 topic based on the former one?
It's simply a list of tutorials needed, by random order.)
that MagPi book is good, but it's just the start for the bloody C noobs. Having learnt that, you're still unable to program a simple LED blink program. One urgently would need follow-up tutorials for all of this: C for GPIOs, UART, i2c and SPI (partially availabe by wiringPi) C for HATs C for graphi...
what a nonsense. I doubt that you actually are programming in C. C is the language which is BUILT UPON MULTIPLE LIBRARIES as C just has about 20 defined basic keywords/commands! to start with #include <unistd.h> #include <errno.h> #include <stdio.h> #include <stdint.h> #include <stdlib.h> #include <...
but the C libs and the tutorials to them are missing, you wise guy. No C access without libraries and tutorials to it! for Arduino it's there, but for the Pi are missing: C for GPIOs,UART, i2c and SPI (partially by wiringPi) C for HATs C for graphics C for the Pi Cam C for audio C for game programmi...
yes, because of the huge number of Arduino API Libs.
But it's all legal C/C++ code
providing lot of good C/C++ tutorials,
using legal C/C## libs,
and above all:
it's easy to use, and above all, it works out of the box!
Arduino is a much simpler platform. Python will be a much better language to use on the Pi unless you are already proficient in C (which is unlikely if all you have programmed is an Arduino), First, Arduino is != Arduino. There are small 16MHz / 2KB 8bit AVRs (Uno, Nano), then the 8KB Mega, a "bigg...
Can Arduino only work with C(++)? I actually bought a cheap Arduino starter kit :? ¨ The Arduino IDE is always compiling by a gnu C++ compiler, and most of the libraries are C++ coded (e.g., Serial, Wire, TFTs, and most others too). Nevertheless you may write also standard C code which will be inte...
Hello! New to Raspberry and the forum! I wish to make a car with motors and, maybe get camera and lights attached to it. Hope to learn how things work along the way. Some of the tutorials use Python some use C(++) I think. What's the pro and cons, and which one should I focus on in this type of pro...
just a minor humble suggestion, stumbling over Background() and BackgroundRGB():
as Background(r,g,b) has 3 parameters , i.e. r,g,b
and
BackgroundRGB(r,g,b,a) has 4 parameters i.e. r,g,b,a
wouldn't it be a good idea to rename BackgroundRGB() to BackgroundRGBA() ?
sorry, my English is not so good to understand the details unequivocally. I usually start with sth like this (taken from your github example, modified) #define GRAY25 64, 64, 64 #define YELLOW 255, 255, 0 #define SKYBLUE 135, 206, 235 //... initWindowSize(20, 20, 600, 360); init(&width, &height); //...
thank you!
how to set the clear_color? Is it automatically the last background color which has been set?
or is there also a additional vgClear(x, y, w, h, clear_color );