Re: Bug #1503114

[<tim...@en...>]

Ethan A Merritt wrote:
> On Tuesday 20 June 2006 07:21 pm, Timoth=E9e Lecomte wrote:
>  =20
>>>  =20
>>>      =20
>> With the current code, 99% of chance of getting the error "Can't find=20
>> PostScript prologue file" out-of-the-box when using the postscript=20
>> terminal on Windows=20
>>    =20
>
> Is that because there is not an appropriate README file?
> How about if we change the message to:
>
> "Please copy your PostScript prolog files to <somewhere Windowish>"
>  =20
The problem is this "somewhere". What would it be ? On Windows, it=20
should be a path relatively to the executable, and the code to retrieve=20
the absolute path from the path of the executable has yet to be written.
> After all, it doesn't work "out of the box" on unix either.=20
> You still have to set up your font paths and add  environmental
> variables to your locally customized initialization files.
>  =20
Well, you do './configure - make - make install' and it works, "out of=20
the box", in my opinion. Then, you can customize, but that's optional.
>> and other non-Unix platforms.=20
>>    =20
>
> Do you mean because of the trailing '/' on the directory name?
> Other than that I don't see much difference.  But yes, I should
> add conditional code for VMS that adds ':' rather than '/'.
> Does windows or os2 need it changed to '\'?
>  =20
I have not even thought about that. I just wanted to distinguish=20
platforms where absolute paths can be determined at compile time, and=20
platforms where it is not possible, such as Windows. I just assume there=20
are others of this type.
>> Two alternatives :
>> 1- Move them back to the source file (the GNUPLOT_PS_DIR environment=20
>> variable can be conserved for flexibility)
>>    =20
>
> Huh?  What does the environmental variable do, if the prolog
> is in the driver?
>  =20
Maybe to use custom prologs that you have modified from the originals=20
and installed by hand (so that you know where they are). What was your=20
first intention ? Reduce executable size ? Make post.trm easier to read ?
>>     * others : include them in the source file at compile time
>>    =20
> I think you are over-generalizing. Why assume that it is an=20
> issue for all non-unix systems?  I'll report back on VMS, but
> I don't see why there should be a problem.  And I doubt we=20
> support anything less unix-like than VMS
Maybe I am.
I think it is probably the first place in gnuplot where external files=20
are needed _on all platforms_.
This issue has never happened on Windows (some needed files are just=20
placed in the directory of the .
On OS/2, pm.trm looks for gnupmdrv.exe
Where the X11 terminal is available, x11.trm looks for gnuplot_x11.
Nowhere we have a code that has been written for all platforms.

Timoth=E9e