[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: texinfo-5.0 available

From: Eli Zaretskii
Subject: Re: texinfo-5.0 available
Date: Mon, 18 Feb 2013 19:38:29 +0200

This builds OK on MS-Windows with MinGW tools, but I found out that I
need a manifest file on Windows Vista and later, to avoid the annoying
UAC elevation prompts.  (Evidently, ginstall-info is treated by
Windows as some kind of installer program.)  The manifest is also
needed to run the test suite on latest versions of Windows, because
otherwise Bash cannot run executables which require elevation, and all
the tests for install-info fail.

My question is how to do this.  The manifest (an XML file) should be
named install-info/ginstall-info.exe.manifest in the distribution, so
that its name matches ginstall-info.exe used by the test suite, but
then it should be installed in the bin directory alongside
install-info.exe under the name install-info.exe.manifest.  So will
the change below to install-info/Makefile.am do the trick?  Also, will
'transform' rename the file to install-info.exe.manifest at "make
install" time?  (I couldn't test this in Automake myself, since I use
an older version than the one required by Texinfo.)


--- install-info/Makefile.am~0  2012-06-11 20:54:27.000000000 +0300
+++ install-info/Makefile.am    2013-02-18 19:26:52.302000000 +0200
@@ -13,6 +13,11 @@
 SUBDIRS = tests
 bin_PROGRAMS = ginstall-info
+w32_manifest = install-info.exe.manifest
+ dist_bin_SCRIPTS = $(w32_manifest)
 # Use `ginstall-info' in the definition of PROGRAMS and in dependencies
 # because automake generates an install-info target in every Makefile

reply via email to

[Prev in Thread] Current Thread [Next in Thread]