how to create a backend that can be CUPS recognize? about cups HOT 2 CLOSED

When you use Linux,
you may have a look here:
https://en.opensuse.org/SDB:Using_Your_Own_Backends_to_Print_with_CUPS

When you use macOS I don't know.
I think in macOS CUPS runs within some kind of "sandbox"
so user-made CUPS backends may not be allowed by default?
But this is only a blind guess.

Current CUPS upstream is no longer here but under
https://github.com/OpenPrinting
at
https://github.com/OpenPrinting/cups

When you use macOS this place here could be still
the right place for CUPS on macOS - I don't know?

from cups.

When you use Linux, you may have a look here: https://en.opensuse.org/SDB:Using_Your_Own_Backends_to_Print_with_CUPS

When you use macOS I don't know. I think in macOS CUPS runs within some kind of "sandbox" so user-made CUPS backends may not be allowed by default? But this is only a blind guess.

Current CUPS upstream is no longer here but under https://github.com/OpenPrinting at https://github.com/OpenPrinting/cups

When you use macOS this place here could be still the right place for CUPS on macOS - I don't know?

Thanks for your reply!

I've read some manuals you provide and source codes of different backend and found that any new backend MUST report its information through stdout with the form "device_scheme, device_uri, device_make_and_model, device_info, device_id, device_location" or could call cupsBackendReport function instead. CUPS will soon recognize this new backend after reporting operation.

from cups.