pdfdistiller

[Goffioul Michael]

CUPS looks for all backends by executing them (located in /usr/lib/cups/backend/) without
any argument. Then the backend should answer with a well formatted string. This process is
doen at CUPS startup (so you need to restart CUPS).
 
If you look at the script, you'll see that registering will be OK if the executable is correctly found
and has the exec bit set. Note also that the PDFBIN variable uses "which" to locate the executable,
but this is performed as a system user, where the PATH variable reduces to /usr/bin:/bin. So this
means that your new binary should be located in some standard place.
 
Michael.


-----Original Message-----
From: Mohit Kumar [mailto:mohit.kumar at gmail.com]
Sent: Friday, July 08, 2005 11:32
To: kde-print at kde.org
Subject: pdfdistiller


Hi All,
 
I have been trying to understand the working of the pdfdistiller script as I have been wanting to do something like this for a long time. 
Though most of the part is clear to me, the only part that is still is a mystery is how is the "direct pdf" registered as a cups backend. What I mean to say is that if I change the PDFBIN to any other binary it stops showing. 
So I was wondering how this is enabled? 
Any help in this regard would be highly useful.
 
Thanks,
Mohit

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.kde.org/pipermail/kde-print/attachments/20050718/2c9af268/attachment.html