-
Notifications
You must be signed in to change notification settings - Fork 457
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
how to create a backend that can be CUPS recognize? #6195
Comments
When you use Linux, When you use macOS I don't know. Current CUPS upstream is no longer here but under When you use macOS this place here could be still |
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. |
I've created a new backend which is based on the cups-pdf but with fewer code , only keeping the main function and triming the code which is used to generate config file.
After compiling using gcc -O9 -s cups-pdf.c -lcups and copying cups-mybackend binary to /usr/lib/cups/backend/, also copying the ppd file to /usr/share/ppd/cups-mybackend, CUPS cannot recognize this new backend.(sudo lpinfo -v has nothing about cups-my-backend and it also couldn't be selected in AddPrinter in WEB .)
So how should I do to let CUPS know this new backend?
The text was updated successfully, but these errors were encountered: