Many thanks to all who have answered my cry for help - very much appreciated!
I watched a chap on Youtube late last night, building Krita. He really knew what he was doing and even he screwed up 5 or 6 times. But he understood all those strange code error messages, and fixed the job - brilliant to watch someone at work who knows what they are doing!
I on the other hand, definitely do not fit into that category, when it comes to ‘terminal’ stuff.
I very occasionally use a terminal command in Mac OS, but I have to go and look those up on the web every time I need them.
But getting dependencies and all that other stuff is so far outside my wheelhouse, and I’m very aware of my own limitations. I’m not dyslexic, but I seriously might as well be when it comes to all this - I had no idea it was going to be so hard.
So, sorry to say. Linux in Parallels on ARM is a non-starter for me - 'cos I’m too thick!
I’m currently running Parallels on a free trial, but in 9 days that will run out and it will cost £90 sterling for a licence.
The latest Parallels for ARM Macs only allows Windows 11 Pro, if I wanted to go with a windows install of ART. Here’s the kicker - a key costs £220.
So that’s £310 total, to run software that is free…that makes zero business sense to me.
So I’m scrapping the whole idea, and following the suggestion of @yasuo and going back to ART v1.23 for the moment.
Again, many thanks to all those who have kindly given their help and advise; but alas, I am a bigger idiot than I thought!!!
I knew this, and that knowledge of building RawTherapee is a pre-requisite.
Going from knowing how to use a tool to building the tool is like learning a musical instrument. Take bassoon for example: in 10 years you will have some technical abilities. In 20 years you’re making refined reeds and start to sound good. That’s a good 20 years of honks and biffs to get through, and your day 2 isn’t going to sound twice as good as your day 1.
Stability is a process by which bugs are squashed at the same rate as they are introduced (new features).
\qquad^{\huge\because} \ \ {Stability= - \log_e\large({N_{bugs} / t *Rate_{squash}}\large )}
\large\therefore\ The key to increased stability for ART is getting good crash reportage.
ART Anatomy of an actionable bug report for macOS users:
Version details of the build you’re using.
Your operating system name and version.
Explain the exact steps to reproduce the problem. Apply the “Neutral” processing profile to your photo and then explain what needs to be done to trigger the problem from there.
Upload the raw + arp. Make your raw and arp files available to us if your bug involves a particular raw file, a particular setting, or lack of support for your raw file.
Show a screenshot of the problem. Do not crop the screenshot, show the full window.
Open one issue per bug, or one issue per feature request. Do not report different bugs in the same issue, do not request different features in the same issue.
Check for duplicates. Search the forum and our issue tracker before filing a new report as chances are that someone has already reported the problem before you, and duplication wastes time.
Make sure you use the latest version as it’s likely that a bug in an old version has been fixed in the latest one.
If your issue involves a crash, provide a system crash report, otherwise your bug report is useless.
Additionally, it is often beneficial to do the following:
Show a video recording of how you trigger the problem. A video recording is the best way of explaining a problem if your screenshot and “steps to reproduce” are insufficient. You can make one easily using system software.