[Desktop_printing] Re: [Printing-architecture] Re: Building PAPI implementation

[Till Kamppeter]

I have probably found bugs in the PAPI library:

I have CUPS 1.2.0 installed and the PAPI library. I have several local
CUPS queues, one for an HP PhotoSmart 2600 using the HPIJS driver. With
this driver I have the PPD options "PageSize", "PrintoutMode",
"Quality", "InputSlot", and "Duplex". See

http://www.linuxprinting.org/ppd-o-matic.cgi?driver=hpijs&printer=HP-PhotoSmart_2600&show=1

for the PPD file. I can print on this printer using the PAPI "lpr "
command and the printer is correctly shown with the PAPI "lpstat -p" and
"lpstat -v".

Now I run

printer-query -d HPPSmart2600

from the sample programs. According to its source code it is supposed to
show all attributes of the printer when the command is called without
the "-o" option (otherwise it wouls show only the specified attribute).

What I get is

--------------------------------------------------------------------------
[root at majax c]# printer-query -d HPPSmart2600
HPPSmart2600 at (default):
        printer-name=HPPSmart2600,HP Photosmart 2600
        rm=majax.mandrakesoft.com
        rp=HPPSmart2600
[root at majax c]#
--------------------------------------------------------------------------

There came out only three attributes, "printer-name", "rp", and "rm".
What I expect is (according to section 9 of the specs) attributes for
each PPD option, and also some more attributes, like whether I have a
color printer, which operations are supported and whatever the specs
tell about required printer attributes.

And if I take the name of one of the required attributes, as for example
"operations-supported", I get the very same output as without supplying
an attribute name:

--------------------------------------------------------------------------
[root at majax c]# printer-query -d HPPSmart2600 -ooperations-supported
HPPSmart2600 at (default):
        printer-name=HPPSmart2600,HP Photosmart 2600
        rm=majax.mandrakesoft.com
        rp=HPPSmart2600
[root at majax c]#
--------------------------------------------------------------------------

It seems that the query function

--------------------------------------------------------------------------
status = papiPrinterQuery(svc, destination, requested, NULL, &printer);
--------------------------------------------------------------------------

is not taking care of what is in "requested". Without "-o" option
"requested" should be NULL and therefore all attributes should be
returned in "printer", if "-o" is used "requested" should contain the
argument of "-o" and therefore only this attribute should be shown (of
an error if the attribute does not exist). See section 6 of the specs.

The query (and the use) of the capabilities )section 9) of a CUPS queue
(independent whether it is local or remote) is essential (all Linux
systems use CUPS by default), as the user expects to be able to control
duplex, finisher, quality, paper size, ... and so an ISV should be able
to get these options into the printing dialog. If this is not possible,
the current PAPI is not fully usable and cannot be suggested as a
standard, as an ISV has to interface to CUPS (or to KDE) on Linux
machines and to the OS-manufacturer-specific printing system on Sun
machines (and so make two dialogs, which we want to avoid with proposing
PAPI as a standard).

   Till

Till Kamppeter wrote:
> Now I got it working with CUPS by changing the default print service at
> compile time. The problem was the quoting. The current code
> 
> -----------------------------------------------------------------------
> #ifndef DEFAULT_PRINT_SERVICE
> #define DEFAULT_PRINT_SERVICE   "lpsched"
> #endif
> 
> ...
> 
> char *scheme = DEFAULT_PRINT_SERVICE;
> -----------------------------------------------------------------------
> 
> requires from the user to supply also the quotes. So in the spec file I
> had to do
> 
> -----------------------------------------------------------------------
> export CFLAGS="$CFLAGS -DDEFAULT_PRINT_SERVICE=\\\"ipp\\\""
> %configure --without-apache
> %make
> -----------------------------------------------------------------------
> 
> Note the quoted quotes in the first line. This I did not do in the first
> place and therefore it broke.
> 
> But please still supply the documentation to configure PAPI at run time.
> Also a possibility to define the compile time default by the configure
> script, both by spooler auto discovery and also by command line option
> would be great.
> 
> Note also that on the linker call(s) for the Ruby bindings the
> 
> -L$RPM_BUILD_DIR/papi/source/libpapi-dynamic/.libs
> 
> is missing. So I had to put
> 
> -----------------------------------------------------------------------
> export LDFLAGS="$LDFLAGS -L$RPM_BUILD_DIR/papi/source/libpapi-dynamic/.libs"
> -----------------------------------------------------------------------
> 
> before the "%configure" in the spec file.
> 
>    Till
> 
> 
> 
> Till Kamppeter wrote:
> 
>>Now I got it RPMized so that it can be installed on a machine with
>>already installed CUPS. No I tried to make it actually working with the
>>installed CUPS. I found out by running an "lpr" command through strace
>>that it tries to load the non-existing "lpsched" service
>>(/usr/lib/psm-lpsched.so) and I have seen in the source code that
>>"lpsched" is used a s the default service (should not be as "lpsched"
>>does not ship with the package.
>>
>>So I compile with
>>
>>export CFLAGS="$CFLAGS -DDEFAULT_PRINT_SERVICE=ipp"
>>./configure --without-apache --without-ruby
>>make
>>
>>to make it using "ipp" as default service (can one configure/switch the
>>service at run time? There are no files in /etc/... and no documentation
>>about such files, man pages are only in section 1 and 8, nothing in
>>section 5).
>>
>>But with this setting it does not build:
>>
>>------------------------------------------------------------------------------------
>>[...]
>>Making all in libpapi-dynamic
>>make[2]: Entering directory
>>`/home/tkamppeter/rpm/BUILD/papi/source/libpapi-dynamic'
>>if /bin/sh ../../libtool --tag=CC --mode=compile
>>i586-mandriva-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I.
>>-I../../source/libpapi-common  -I. -DPSM_DIR=\"/usr/lib\"
>>-I../libpapi-common  -I./nss -DNSS_EMULATION   -I/usr/include/apr-1
>>-DDEFAULT_PRINT_SERVICE=ipp -MT psm.lo -MD -MP -MF ".deps/psm.Tpo" -c -o
>>psm.lo psm.c; \
>>then mv -f ".deps/psm.Tpo" ".deps/psm.Plo"; else rm -f ".deps/psm.Tpo";
>>exit 1; fi
>>mkdir .libs
>> i586-mandriva-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I.
>>-I../../source/libpapi-common -I. -DPSM_DIR=\"/usr/lib\"
>>-I../libpapi-common -I./nss -DNSS_EMULATION -I/usr/include/apr-1
>>-DDEFAULT_PRINT_SERVICE=ipp -MT psm.lo -MD -MP -MF .deps/psm.Tpo -c
>>psm.c  -fPIC -DPIC -o .libs/psm.o
>>if /bin/sh ../../libtool --tag=CC --mode=compile
>>i586-mandriva-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I.
>>-I../../source/libpapi-common  -I. -DPSM_DIR=\"/usr/lib\"
>>-I../libpapi-common  -I./nss -DNSS_EMULATION   -I/usr/include/apr-1
>>-DDEFAULT_PRINT_SERVICE=ipp -MT service.lo -MD -MP -MF
>>".deps/service.Tpo" -c -o service.lo service.c; \
>>then mv -f ".deps/service.Tpo" ".deps/service.Plo"; else rm -f
>>".deps/service.Tpo"; exit 1; fi
>> i586-mandriva-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I.
>>-I../../source/libpapi-common -I. -DPSM_DIR=\"/usr/lib\"
>>-I../libpapi-common -I./nss -DNSS_EMULATION -I/usr/include/apr-1
>>-DDEFAULT_PRINT_SERVICE=ipp -MT service.lo -MD -MP -MF .deps/service.Tpo
>>-c service.c  -fPIC -DPIC -o .libs/service.o
>>service.c: In function 'service_load':
>>service.c:60: error: 'ipp' undeclared (first use in this function)
>>service.c:60: error: (Each undeclared identifier is reported only once
>>service.c:60: error: for each function it appears in.)
>>ICECREAM[19319]: Compiled on 192.168.2.67
>>make[2]: *** [service.lo] Error 1
>>make[2]: Leaving directory
>>`/home/tkamppeter/rpm/BUILD/papi/source/libpapi-dynamic'
>>make[1]: *** [all-recursive] Error 1
>>make[1]: Leaving directory `/home/tkamppeter/rpm/BUILD/papi/source'
>>make: *** [all-recursive] Error 1
>>------------------------------------------------------------------------------------
>>
>>Can you tell me how to get it correctly talking with CUPS? Thanks.
>>
>>   Till
>>
> 
>