|
From: Geoff C. <geo...@bj...> - 2002-07-22 04:01:27
|
I have recompiled ghostscript, changing fDebugOutput to 1. The output I saw
was exactly the same as before. Ie, there were no extra diagnostic messages
displayed to indicate some problems.
Are there any other suggestions?
I had a look into the code. It seems that the error message is being
generated in the gomni.c, line 650, after checking something:
if (!pDev->vhOmni)
{
// Failure!
fprintf (stderr, "\n<<<<<<<<<<<<<<<<<<<<<< ERROR
>>>>>>>>>>>>>>>>>>>>>>>\n\n");
fprintf (stderr, "Error: Could not load libomni.so!\n\n");
However, I have no idea why pDev->vhOmni is NULL, and I don't have the
skills to track it down.
Thanks for anyhelp
Geoff
On Sat, 13 Jul 2002 00:36, Mark Hamzy wrote:
> Hi Geoff,
>
> How do you enable omni into ghostscript? Did you recompile ghostscript
> with our patch?
> If so, can you check out Ghostscript/new_src/gomni.c, change fDebugOutput
> to 1 and recompile and retest.
> That should give more debug output as to what is wrong.
>
> As far as your test program, libomni.so is C++ code so the calling
> application should link with stdc++. Also,
> while I don't know if this causes problems or not, all of our loading code
> uses glib's g_module_open instead of dlopen.
>
> Also, as a test you can run OmniDeviceOptions libKyocera_FS_1600_.so and
> see if that works.
>
> Mark
>
> Take a look at the Linux Omni Printer Driver Framework at
> http://www.ibm.com/linux/ltc/projects/omni/
|