<html>
    <head>
      <base href="https://bugs.documentfoundation.org/">
    </head>
    <body><span class="vcard"><a class="email" href="mailto:vstuart.foote@utsa.edu" title="V Stuart Foote <vstuart.foote@utsa.edu>"> <span class="fn">V Stuart Foote</span></a>
</span> changed
          <a class="bz_bug_link 
          bz_status_NEW "
   title="NEW - Windows 64-bit and executable name of 64-bit build of ghostscript -- gswin64c.exe"
   href="https://bugs.documentfoundation.org/show_bug.cgi?id=94117">bug 94117</a>
          <br>
             <table border="1" cellspacing="0" cellpadding="8">
          <tr>
            <th>What</th>
            <th>Removed</th>
            <th>Added</th>
          </tr>

         <tr>
           <td style="text-align:right;">CC</td>
           <td>
                
           </td>
           <td>noelgrandin@gmail.com
           </td>
         </tr></table>
      <p>
        <div>
            <b><a class="bz_bug_link 
          bz_status_NEW "
   title="NEW - Windows 64-bit and executable name of 64-bit build of ghostscript -- gswin64c.exe"
   href="https://bugs.documentfoundation.org/show_bug.cgi?id=94117#c7">Comment # 7</a>
              on <a class="bz_bug_link 
          bz_status_NEW "
   title="NEW - Windows 64-bit and executable name of 64-bit build of ghostscript -- gswin64c.exe"
   href="https://bugs.documentfoundation.org/show_bug.cgi?id=94117">bug 94117</a>
              from <span class="vcard"><a class="email" href="mailto:vstuart.foote@utsa.edu" title="V Stuart Foote <vstuart.foote@utsa.edu>"> <span class="fn">V Stuart Foote</span></a>
</span></b>
        <pre>Issue remains, and seems we need to test for _WIN64 here and use the
'"gswin64c" EXESUFFIX,' for RenderAsBMPThroughHelper [1].

Things were complicated with a MS security change in handling of SYMLINKs
[2][3]

On 64-bit Windows we now have to make a hard link [4] creating gswin32c.exe
link to the 64-bit gswin64c.exe to be able to use Ghostscript to render the EPS
to canvas with RenderAsBMPThroughGS [5]


=-ref-=
[1]<a href="https://opengrok.libreoffice.org/xref/core/filter/source/graphicfilter/ieps/ieps.cxx?a=true&h=369#390">https://opengrok.libreoffice.org/xref/core/filter/source/graphicfilter/ieps/ieps.cxx?a=true&h=369#390</a>

[2]
<a href="https://social.technet.microsoft.com/Forums/en-US/0eefc57f-8c01-450a-a1cf-8e2894a951d9/symbolic-link-type-changed">https://social.technet.microsoft.com/Forums/en-US/0eefc57f-8c01-450a-a1cf-8e2894a951d9/symbolic-link-type-changed</a>

[3] <a href="https://technet.microsoft.com/library/security/ms15-020">https://technet.microsoft.com/library/security/ms15-020</a>

[4] That is:
1. navigate to bin directory of the 64-bit gs install, e.g. C:\Program
Files\gs\g9.21\bin

2. hard link with "mklink /h gswin32c.exe gswin64c.exe"

before a simple symlink with mklink sufficed, now have to use the hardlink.

[5]
<a href="https://opengrok.libreoffice.org/xref/core/filter/source/graphicfilter/ieps/ieps.cxx#370">https://opengrok.libreoffice.org/xref/core/filter/source/graphicfilter/ieps/ieps.cxx#370</a></pre>
        </div>
      </p>


      <hr>
      <span>You are receiving this mail because:</span>

      <ul>
          <li>You are the assignee for the bug.</li>
      </ul>
    </body>
</html>