[Info-vax] Ghostscript update for VMS
Mark Berryman
mark at theberrymans.com
Thu Jul 7 17:10:27 EDT 2011
On 7/7/11 2:28 AM, JOUKJ wrote:
> Mark Berryman wrote:
>> On 7/4/11 11:01 AM, Mark Berryman wrote:
>>> Is anyone still using ghostscript? I have a build of 9.02 I'd like to
>>> have a couple of folks try out. I am also wondering if anyone still
>>> wants this done as a PCSI kit or if a simple ZIP of the necessary files
>>> (which are fewer in number than they were before) is sufficient.
>>>
>> > [snip]
>>
>> Ok. I need to put together an actual download page on my web server
>> but, for now, a copy of this distribution can be found from the same
>> place where I make my PHP kits available. You can download this file
>> at http://www.theberrymans.com/php_kits/ghostscript_9_2.zip
>>
>> Note that this is not a source kit. It simply contains everything you
>> need to run Ghostscript on VMS.
>>
>> Comments regarding the build or the distribution kit are welcome and
>> appreciated.
>>
>> Mark Berryman
>>
>> --- Posted via news://freenews.netfront.net/ - Complaints to
>> news at netfront.net ---
> Tested and it worked. Still I had to set the gs symbol (i.e. needed by
> GhostView) manually. It would be handy if this was done by setup.com
> Thanks for the porting effort.
Do you have a version of GhostView that works with this version of
Ghostscript? The one I could find, GV v3.5.8, does not work at all,
either with the current GhostScript (it can't give GS a simple file
name) or with VMS V8.4 (the file selection window does not paint
anything until you mouse over where the files are supposed to be listed).
> Mark, are you planning to make also a source-code distribution, or (even
> better) merge your changes into the "official" ghostscript
> distributions? My experience in the past was that the ghostscript
> developers were willing to include the changes for OpenVMS.
I'll be including a backup save set of the source code when I release
the PCSI kit. The code changes would probably be easy enough to get
into the official release. However, I had to make several changes to
the .mak files, in some cases completely rewriting them. The changes
are not compatible with the Unix versions.
For example, all of the .mak files use $(D) as the path separator,
defined as / for unix and \ windows and it is null for VMS. That is
because you cannot simply concatenate things together to build a path on
VMS. As long as the reference in question is simply $(DIR)$(D)filename,
this is not a problem. However, when the reference needs to go more
than one level deep, i.e. $(DIR1)$(D)$(DIR2)$(D)$(DIR3)($D)filename,
everything breaks. There are a number of such instances in the build
files. I simply edited them for VMS when doing the build. We'd need to
come up with a way to fix the issue that doesn't break the build file
for other platforms in order to submit it.
Mark Berryman
--- Posted via news://freenews.netfront.net/ - Complaints to news at netfront.net ---
More information about the Info-vax
mailing list