On 12 Apr 2008, at 5:27, Michael Sweet wrote:
> No, you can't "make install" on Windows.  It isn't supported and
> won't work.

With Msys/mingw it is supported, and it does work - except for the  
specific case that Brian has triggered on Vista.

There's a problem with the way that Vista UAC reacts to some of the  
executables bundled with the Msys "current" release (Msys 1.0.10),  
specifically install.exe, install-info.exe and patch.exe.

Now install-info I can live without, but install and patch are  
important.

(Note: rumour has it that these issues are addressed in the Msys  
"Technology Preview" tree, but for folk like me who like to follow  
"current" that's not always an option. I think Brian's in broadly the  
same position.)

However: All is not lost, it seems there is an easy workaround.
The trick seems to be to give the aberrant exe's a stub manifest  
file, and then everything just works. I got access to a Vista box  
today to try this, and it appears to work well. I guess the technique  
may even be useful for fixing other tricky exe's on Vista (like a  
fltk-config --post option for Vista, if it proves to be necessary  
longer term...)

Anyway, here's the trick.
Say you want to fix patch.exe to run, you make a file called  
patch.exe.manifest, in the Msys /bin directory, alongside patch.exe,  
then "touch patch.exe". After that, patch works fine without  
permission issues (ditto install.exe and install-info.exe, and  
presumably others.)

Worked well for me - should hopefully work for everyone else too, if  
they need it.

Here's what goes in the manifest stub:
-------------
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1"  
manifestVersion="1.0">
   <v3:trustInfo xmlns:v3="urn:schemas-microsoft-com:asm.v3">
     <v3:security>
       <v3:requestedPrivileges>
         <v3:requestedExecutionLevel level="asInvoker" />
       </v3:requestedPrivileges>
     </v3:security>
   </v3:trustInfo>
</assembly>
-------------

Hope that proves useful,
-- 
Ian



_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk

Reply via email to