Re: Print to PDF under Windows [changeset-4]

[Ben Abbott]

On Nov 22, 2009, at 4:07 PM, Tatsuro MATSUOKA wrote:

> Hello Ben
> 
> Thanks for your efforts.
> 
> I have installed two ghostscript. One is for native windows (gswin32.exe ) 
> and the other is for cygwin
> (gs.exe).
> 
> This patch seems to search ghostscript in the order of  'gswin32c.exe', 
> gs.exe and gs?
> If it is so, is 'gswin32c.exe' selected even for cygwin ?
> If it is the case, it will be bad for cygwin.
> 
> I think that it is OK to search 'gs.exe' or 'gs' when isunix() is true.
> 
> For the people who do not like to use non standard ghostscript binary (e.g. 
> who would like to use
> gswin32c.exe but not gs.exe from cygwin) , they should set 'GSC' 
> environmental variable.
> 
> 
> Marco, who is a maintainer of cygwin version maintainer, perhaps have similar 
> opinion on this matter. 
> Please see his reply for 'OCTAVE_PROG_GHOSTSCRIPT for windows'.
> 
> http://old.nabble.com/Re:-OCTAVE_PROG_GHOSTSCRIPT-for-windows-p26463802.html
> 
> At this post, it is also better to hear Macro's opinion.
> 
> Regards
> 
> Tatsuro
> 
> 
> 
> --- Ben Abbott  wrote:
> 
>> 
>> On Nov 21, 2009, at 10:05 AM, Ben Abbott wrote:
>> 
>>> On Nov 21, 2009, at 9:15 AM, Benjamin Lindner wrote:
>>> 
>>>>> Michael or other Window users,
>>>>> Can you confirm the attached works?
>>>>> Ben
>>>> 
>>>> The console version of ghostscript on win32 is called "gswin32c.exe".
>>>> There is also a GUI version, which is called "gswin32.exe".
>>>> I don't see the reason for using the gui version. What if you want to
>>>> pipe commands to ghostscript?
>>>> 
>>>> If one insists on using the GUI version, well then you can specify
>>>> it in GSC anyway, but in my opinion the correct version to use
>>>> by default is the console version. Hence "gswin32c.exe"
>>>> 
>>>> benjamin
>>> 
>>> Ok, my understanding is that EXEC_PATH is equivalent to the PATH 
>>> environment variable that was
>> in place when Octave was run. Which is likely to include the default shell's 
>> PATH as well as
>> additions needed to run Octave. In the event  ghostscript is bundled with 
>> Octave, then EXEC_PATH
>> is preferred over PATH.
>>> 
>>> The attached changeset looks for the console version of ghostscript, 
>>> "gswin32c.exe", and still
>> searches EXEC_PATH for gswin32c.exe.
>>> 
>>> Ben
>>> 
>>> <changeset.patch>
>> 
>> If I understand correctly ...
>> 
>> isunix() == true for cygwin and unix systems.
>> ispc() == true for Win32 and mingw
>> 
>> For Win32, mingw, and cygwin, I assume that "gswin32c.exe", and "gs.exe" may 
>> each represent the
>> ghostscript binary?
>> 
>> For cygwin and unix, the binary may be "gs".
>> 
>> Thus, I don't see the utility of using isunix() or ispc() ... hence another 
>> proposed changeset.
>> 
>> Ben
>> 


Ok ... a fourth attempt.

Ben

changeset.patch
Description: Binary data