Re: [TCLCORE] tkprint-cups branch - please test

[Schelte B. <tc...@tc...>]

Hello Kevin, Emiliano,

Great work, thanks. I have tried this on SUSE 15.4 with the following 
results:

../unix/configure reports (among other things):
checking whether to use libcups... yes
checking for cups/cups.h... no

The make command then fails with:
../unix/tkUnixPrint.c:16:10: fatal error: cups/cups.h: No such file or 
directory
  #include <cups/cups.h>

So it seems the configure check for cups availability is not foolproof 
(me acting as the fool).

After installing cups-devel (zypper in cups-devel), everything builds 
fine. The dialog looks great and correctly shows my printer. I missed 
the option to print to a file, which is normally present in a print 
dialog. But that option is also not available in the scripted version. 
So this is not a deficiency of the compiled version.

I haven't actually tried printing. My understanding is that the request 
was only to check the dialog.


Regards,
Schelte.


On 09/06/2024 03:38, Kevin Walzer wrote:
> Hi all,
> 
> Emiliano Gavilan has been working on a native Tk interface to the CUPS
> printing library on Unices, and has add this implementation to the "tk
> print" command that was added as part of TIP 604. Tk will now link to
> libcups if the library is installed at build time, and the result is a
> much faster implementation. Tk will fall back to the script-level
> implementation that was developed in TIP 604 if CUPS is not installed.
> 
> I've assisted Emiliano with the build-time bits (configure.ac and
> Makefile.in), and have been testing the branch on Debian. It now builds
> without errors and runs fine. We'd like to ask others in the community
> to give the "tkprint-cups" branch and provide feedback. Once we have a
> sense that the build works to others' satisfaction, Emiliano will merge
> the branch.
> 
> I don't believe a TIP is required - this branch adds an additional
> under-the-hood implementation and an optional build-time dependency, but
> introduces no public API changes. If others think adding a note to TIP
> 604 on the additional details is justified, I will do so.
> 
> Looking forward to your comments!
> 
> Thanks,
> 
> Kevin