Luckily, there are several tutorials available... You can start with this one: https://www.cl.cam.ac.uk/projects/raspb ... intro.htmlTheArch1tect wrote:However, I am having a difficult time figuring out exactly how to do this;
What counts is a will and willingness to invest some time in learning.TheArch1tect wrote:I have no programming experience of any sort.
...wrong assumption.TheArch1tect wrote:Therefore, I'm assuming I need a different OS
No need to redirect the questions... power-on the RasPi and start googling instead.TheArch1tect wrote:let me know if I need to redirect my questions.
It's a real shame that C almost always requires make files, because those things suck. Been using C for 25 years, and still cannot write a vaguely complex makefile from scratch. Horrible things. Even the efforts to make things better (Cmake etc) are still fairly horrible. I suppose IDEs like VS and Eclipse have helped.chrisryall wrote:Absolutely wrt "learning go program", Jamie.
I've been tapping in code since 1976 (punched cards, even)) Yet I still find the C implementation (eg make file above, totally different syntax rules) a bit daunting!
Whatever. The vast majority of C projects I have been involved with in the last 25 years have used makefiles. The vast majority of OSS C projects use make or similar. The Linux kernel uses make. And clearly make can be used for other languages apart from C, my point was that, as stated, most C projects use make of one form or another. And the make syntax is as ugly as hell, and pretty much incomprehensible to all but make experts.Joe Schmoe wrote:Um, I don't see the connection between C and make.
Anymore than I see a connection between C and (insert name of your favorite editor here).
Some (obvious) notes:
1) You can use make with any tools that make one sort of file from another sort. I've written systems built around make that don't use C at all. In any case, I don't see how you can say "If you use C, you pretty much have to use make…"
2) It's not like any other system has the same sort of functionality (the basic "to make this file from that file, run this command - and only do the command if you need to - i.e., based on the file date/timestamp" functionality). And those that do, end up looking a lot like make.
3) The "tab" thing. Like everything else in Unix/C, you get used to it. Get over it. And besides, if you like Python, you should love make.
I've never had a problem with it - and I'm no expert (on make or anything else…)And the make syntax is as ugly as hell, and pretty much incomprehensible to all but make experts.
They could. I assume that anything that involves "separate compilation" (in any form) could use make. I think youtube-dl does...Python projects doesn't use make, do they?
The main beef in this thread seems to be the requirement that "rule lines" start with a tab.3) What tab thing?