but I am fairly sure that my version of Cups is older than
1.1.14-10. I will download the newer version of Cups or at least the same one that you guys are using.
I prefer to install things via gunzip and tape archive (tar), I do not like RPMs though I know most people do. Is there a tar'ed source of the OMNI driver somewhere?
Thanks,
Jeremiah
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for your replies. I have downloaded the latest source in a tar.gz format both for GhostScript and for Omni. I have configured and made GhostScript with the commands ./configure and make in the GhostScript directory. The Omni source is now untarred without the errors I was receiving when I tried to download it as a package or RPM.
In dipping into some of the documentation I read in Read.me.1st about a "well defined pluggable interface." What is this "well defined pluggable interface," and what set of files is it comprised of? Is it the XML file and additional files? So that I edit the XML file to fit my printer's specifications, then send files through the XML file to the device and the XML file formats the file into GhostScript which formats the file for the printer?
Secondly, when I read "how to build a device" in the docs directory, the first directive I encountered was "Determine and edit the build layout."
What is meant by this terminology? What specifically is the build layout?
Thanks,
Jeremiah
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The "well defined pluggable interface" is described in the document "Pluggable Blitter." It is part XML files and part C++ code. It is for cases where you have a different printer language than is already provided by existing Omni printers and you want to use a proprietary or closed-source solution.
Right now, the XML files are compiled in driver code, so if you change them, you will need to recompile omni.
I have clarified the "How To Create A Device" a little bit. I hope this helps.
Mark
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The printer that we have is using a set of Epson commands. So if there is a pre-existing driver included with the other Omni drivers, that uses these commands, then I can use this as a driver by modifying the XML file appropriately. Am I correct in this? So essentially all I modify is the XML file then recompile Omni with g++?
Jeremiah
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Sorry about the delay.
Yes.
If there are differences between, for example, the forms, then you will need to create a new forms xml file. If the two devices are exactly the same, then you will only need to create a new device xml file (which has the same contents as the old device with the new device name in it).
Mark
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have been going through the "Building" document carefully and have stumbled upon a problem. At 1.6 I received an error trying to unpack the rpm for GTK. When issuing the command:
rpm --install gtkmm . . .
I received and error message that said;
error: failed dependancies: libsigc++
so I jumped ahead to 1.7 and downloaded and installed libsigc++ from sourceforge. There was no developer's version in the http location given so I downloaded and installed what I could find. (I think the order of building should be changed so that SigC++ comes before GTK.)
After installing and successfully testing SigC++, GTK still fails to unpack complaining with the above mentioned error message. Is there a work-around for this?
Jeremiah
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Sorry about the delay. Its been really busy around here.
When you install RPMs you can install multiple RPM packages at the same time in order to satisfy the dependancy issues. For example, rpm -i gtkmm*rpm libsigc++*rpm
When you have installed sigc++ as source code, it does not tell the RPM package manager that it is installed so the dependancy will still fail.
You might try the --nodeps option. That may work around it.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I will try that. I am grateful for your help and do not want to pester you. I apologize if
I seem impatient, I will try to be more patient in the future.
Thanks again,
Jeremiah
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have followed your instructions and tried to install libsc++ as an rpm. I downloaded it from Red Hat and ran it. Now when I do;
./makeOmni
I get an error message that says: error: c++:/usr/lib/libsigc.so: No such file or directory
make [2]: ***[Tester] Error 1
make [2]: Leaving directory `/home/jeremiah/tar_archive/ghostscript-7.0.5/Omni/JobDialog
make [1]: ***[all-recursive] Error 1
make [1]: Leaving directory `/home/jeremiah/tar_archive/ghostscript-7.0.5/Omni
make: ***[all-recursive-am] Error 2
Error Build break!
I have retried installing libsc++ ina variety of directories and retried making Omni but no luck. Do you have a recopmmendation? Should I just find a copy od libsigc.so and place it in the roght dir?
Jeremiah
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
After trying to install the rpm of the OMNI driver I get a message saying failed dependencies;
libscup.so.2
libcupsimage.so.2
libgdk-1.2.so.1
libgtk-1.2.so.0
libsigc-.10.so.0
But I know that I have libscup.so.2 in my cups directory. Does it need to be moved?
How much does the OMNI driver depend upon CUPS and should I have that running before I use the OMNI driver?
Thanks,
Jeremiah
Well, CUPS is optional but that probably isnt the way it works yet with the RPMs.
Do a rpm -qa | grep cups
On my system, I have
cups-1.1.14-10
cups-libs-1.1.14-10
gdk, gtk, and sigc are for the optional job dialog but it is probably required in the RPM now. We will work on both issues.
Mark
Thanks Mark,
I will do a
rpm -qa | grep cups
but I am fairly sure that my version of Cups is older than
1.1.14-10. I will download the newer version of Cups or at least the same one that you guys are using.
I prefer to install things via gunzip and tape archive (tar), I do not like RPMs though I know most people do. Is there a tar'ed source of the OMNI driver somewhere?
Thanks,
Jeremiah
Hi Jeremiah,
Yes. The source code is always a tgz file. The latest source is at http://prdownloads.sourceforge.net/omniprint/Omni-0.7.0.tar.gz?download
Mark-
Thanks for your replies. I have downloaded the latest source in a tar.gz format both for GhostScript and for Omni. I have configured and made GhostScript with the commands ./configure and make in the GhostScript directory. The Omni source is now untarred without the errors I was receiving when I tried to download it as a package or RPM.
In dipping into some of the documentation I read in Read.me.1st about a "well defined pluggable interface." What is this "well defined pluggable interface," and what set of files is it comprised of? Is it the XML file and additional files? So that I edit the XML file to fit my printer's specifications, then send files through the XML file to the device and the XML file formats the file into GhostScript which formats the file for the printer?
Secondly, when I read "how to build a device" in the docs directory, the first directive I encountered was "Determine and edit the build layout."
What is meant by this terminology? What specifically is the build layout?
Thanks,
Jeremiah
Hi Jeremiah,
I think that I am monitoring this forum now.
The "well defined pluggable interface" is described in the document "Pluggable Blitter." It is part XML files and part C++ code. It is for cases where you have a different printer language than is already provided by existing Omni printers and you want to use a proprietary or closed-source solution.
Right now, the XML files are compiled in driver code, so if you change them, you will need to recompile omni.
I have clarified the "How To Create A Device" a little bit. I hope this helps.
Mark
Thanks Mark,
The printer that we have is using a set of Epson commands. So if there is a pre-existing driver included with the other Omni drivers, that uses these commands, then I can use this as a driver by modifying the XML file appropriately. Am I correct in this? So essentially all I modify is the XML file then recompile Omni with g++?
Jeremiah
Hey Jeremiah,
Sorry about the delay.
Yes.
If there are differences between, for example, the forms, then you will need to create a new forms xml file. If the two devices are exactly the same, then you will only need to create a new device xml file (which has the same contents as the old device with the new device name in it).
Mark
Thanks, this helps. Obviously I need to spend more time mucking about in the files that are provided with the Omni.
The device we are working on may function under the XML file of another driver, I will test them and see if there is any effect.
Jeremiah
Hello,
I have been going through the "Building" document carefully and have stumbled upon a problem. At 1.6 I received an error trying to unpack the rpm for GTK. When issuing the command:
rpm --install gtkmm . . .
I received and error message that said;
error: failed dependancies: libsigc++
so I jumped ahead to 1.7 and downloaded and installed libsigc++ from sourceforge. There was no developer's version in the http location given so I downloaded and installed what I could find. (I think the order of building should be changed so that SigC++ comes before GTK.)
After installing and successfully testing SigC++, GTK still fails to unpack complaining with the above mentioned error message. Is there a work-around for this?
Jeremiah
Jeremiah,
Sorry about the delay. Its been really busy around here.
When you install RPMs you can install multiple RPM packages at the same time in order to satisfy the dependancy issues. For example, rpm -i gtkmm*rpm libsigc++*rpm
When you have installed sigc++ as source code, it does not tell the RPM package manager that it is installed so the dependancy will still fail.
You might try the --nodeps option. That may work around it.
Thanks Mark!
I will try that. I am grateful for your help and do not want to pester you. I apologize if
I seem impatient, I will try to be more patient in the future.
Thanks again,
Jeremiah
Mark,
I have followed your instructions and tried to install libsc++ as an rpm. I downloaded it from Red Hat and ran it. Now when I do;
./makeOmni
I get an error message that says: error: c++:/usr/lib/libsigc.so: No such file or directory
make [2]: ***[Tester] Error 1
make [2]: Leaving directory `/home/jeremiah/tar_archive/ghostscript-7.0.5/Omni/JobDialog
make [1]: ***[all-recursive] Error 1
make [1]: Leaving directory `/home/jeremiah/tar_archive/ghostscript-7.0.5/Omni
make: ***[all-recursive-am] Error 2
Error Build break!
I have retried installing libsc++ ina variety of directories and retried making Omni but no luck. Do you have a recopmmendation? Should I just find a copy od libsigc.so and place it in the roght dir?
Jeremiah