What do you mean by "macOS makes it too difficult" to provide compiled binaries?
From last time I looked into this, I seem to recall that you need a MacOS SDK which explicitly must only be used on Apple hardware. Furthermore it seemed that you probably also have to join some Apple developer ...

"Non-commercial" and not making money are different things. If someone uses your compiler to write a NES game and sells it for $25 because they have to package it in a cartridge and physically mail it to buyers, then that person has a business but is hardly "making money." That's the person that ...

So what you are saying is that I should do stuff that I do not enjoy and perhaps buy hardware that I do not need, in order to make it easier for people who are making money using my tools, but do not want to pay for it? Sorry, that does not really click with me.

No, that's not what I'm saying at ...

A lot of people are using gitlab these days as a close analogue of github.
Thanks for the hints (in other posts as well) regarding hosting sites, but I prefer to keep the version control system for my sources on my own server.

If you really want to retain a no-commercial clause, please make it ...

Ask yourself what you're hoping to accomplish.
I have done that a long time ago and I act accordingly.

But cc65 already is a pretty good compiler. It's up there on GitHub, and anyone can use it. It doesn't have a restrictive license. It compiles and runs on the Mac with no problem.
If those are ...

Thanks; I'm getting further. But as I understand (quite probably incorrectly) your comment above, the code in rom will be moved to ram to execute? I can't e.g. put a monitor or a bios written in C in the rom and execute directly from there?
No, no, the copying is only necessary for the data ...

I have managed to modify a config file copy to work (I put it in the same directory as the source) so now it builds 65c02 and (I hope) to use the memory map of my SBC. Still need to find out how to make romable code (i.e. more reading).
To run from ROM you can add a memory region "rom", analogous ...

I downloaded the vbcc source and was, after looking at the makefile, able to build it on my ARM Mac. But, I too got to the point where it was wanting a config file, and I didn't have one. The source vbcc.tar.gz doesn't have a config directory.
Yes, this only the source snapshot. The target ...

I want to build for a generic 65c02, to a terminal output (I expect to have to provide a cout() somewhere). Do I need to build a config file in line with the ones in the config directory? And if so, how do I select it?
As the 6502 distribution supports many target systems, it does not provide a ...

You may find the vbcc compiler a better choice for this project. It’s significantly more advanced than cc65 and was developed by someone who is a compiler expert.

A better compiler would be welcome. Does it have an assembler, run on an ARM Mac, and generate debug data?
It has an assembler and ...

I have uploaded version 5 of the vbcc distribution for 6502 targets at http://www.compilers.de/vbcc.html

Major changes since last update:
- much faster floating point library based on MSBASIC code (about 10x faster than wozfp/SANE)
- option to use routines from Basic ROM on selected targets (VIC-20 ...

10× speedup is a huge leap. :shock: I had no idea the Microsoft FP code was that much more efficient than the Wozniak-Rankin version.
The Wozniak-Rankin code is highly optimized for size, but it is very slow. I think it does a lot of bitwise shifting without much speed optimizations.

I take it ...

I have just uploaded a second release of the vbcc compiler for the 65816 at: http://www.compilers.de/vbcc.html

Changes since r1:
- new floating point format based on MSBASIC code
- more complete math library
- vc allows passthrough of linker options
- certain options like stack size can now be ...

I might have written it wrongly, I'm new to the 65816 and actually find the syntax confusing...
With the exception of the “long” addressing modes and differentiating between eight- and 16-bit immediate-mode operands, syntax is the same as with the 65C02.
The syntax may be, but the semantics are ...

For a number of reasons, I tend to be stingy with direct-page usage, probably a habit acquired long ago when the 6502 was new, RAM was expensive and there was never enough direct-page space. Global variables are placed on direct page only if they are accessed often enough to justify doing so.
Of ...