Re: GSCUPS is in

[Fred Kiefer]

Chad Hardin wrote:
> I added GSCUPS to cvs.  However, I want everyone to know that this does 
> not mean you can start printing to your OS X computer's printers.  At 
> least, not without some kind of zeroconf installed on your box.  I 
> installed tmdns, which is available at sourceforge, and it seems to be 
> working so far as a good zerconf solution for linux machines.
>
> Why do you need zerconf?  The reason is because GSCUPS actually 
> downloads the PPD from the computer serving the printer, it does not 
> store them locally.  Since OS X uses zeroconf and its cups server 
> broadcasts the host name using the zerconf hostname (ie: iMac.local), 
> you need zerconf to resolve the hostname.
>
> OTOH, you can also hook in printers directly into your box and configure 
> cups yourself as a local printer.  I'd like to hear how that works out too.
>
> So, try it out, send in bug reports!
When trying to compile GUI now I get:

Making all in GSCUPS...
make[2]: Entering directory `/usr/src/gnustep/core/gui/Printing/GSCUPS'
Making all for bundle GSCUPS...
 Creating GSCUPS.bundle/....
 Compiling file GSCUPSPrincipalClass.m ...
 Compiling file GSCUPSPageLayout.m ...
 Compiling file GSCUPSPrintInfo.m ...
 Compiling file GSCUPSPrintOperation.m ...
 Compiling file GSCUPSPrintPanel.m ...
 Compiling file GSCUPSPrinter.m ...
 Linking bundle GSCUPS ...
/usr/lib/gcc-lib/i586-suse-linux/3.3.3/../../../../i586-suse-linux/bin/ld: 
cannot find -lssl
collect2: ld returned 1 exit status
make[3]: *** [GSCUPS.bundle/./GSCUPS] Fehler 1
make[2]: *** [GSCUPS.all.bundle.variables] Fehler 2
make[2]: Leaving directory `/usr/src/gnustep/core/gui/Printing/GSCUPS'
make[1]: *** [internal-all] Fehler 2
make[1]: Leaving directory `/usr/src/gnustep/core/gui/Printing'
make: *** [internal-all] Fehler 2

I first thought that this means I havent installed any ssl library, but 
this is not true. There are libssl.so.0 and libssl.so.0.9.7 in /use/lib. 
Perhaps it also needs libssl.so, but than if it cannot find libssl, that 
it should not try to use it. The same also happend after correcting the 
missing symlink for libcrypto.

Cheers
Fred