On 2010-06-18, Charles Wilson libt...@cwilson.fastmail.fm wrote:
b3) For these reasons, it's probably best if the package
maintainer also provides rules for embedding the manifest
in binary form into the real exe. How these rules will
deal with the whole lt-*.exe
* Olly Betts wrote on Fri, Jun 18, 2010 at 01:21:27PM CEST:
On 2010-06-18, Charles Wilson libt...@cwilson.fastmail.fm wrote:
b3) For these reasons, it's probably best if the package
maintainer also provides rules for embedding the manifest
in binary form into the real
Original thread(s)
http://lists.gnu.org/archive/html/libtool-patches/2009-06/msg00058.html
http://lists.gnu.org/archive/html/libtool-patches/2009-07/msg2.html
Revived thread(s):
http://lists.gnu.org/archive/html/libtool-patches/2010-02/msg00019.html
Hi Dave,
thanks for your quick review! I've incorporated all changes not
addressed below.
* Dave Korn wrote on Tue, Mar 16, 2010 at 11:24:42AM CET:
On 16/03/2010 06:17, Ralf Wildenhues wrote:
and updating of system-wide software. The level of privileges required
for some executable
Den 2010-03-19 07:18 skrev Ralf Wildenhues:
AFAIU, the resource file (*.rc) is a simple hand-written text file,
which may refer to the manifest file (like a .c file includes a header),
then gets compiled by windres to an object file and linked in like any
other object. Right?
That's not the
On 19/03/2010 06:18, Ralf Wildenhues wrote:
[ ... snip ... ] The level of privileges required
for some executable program to accomplish its task may be designated by
the program developer by means of a manifest file (@pxref{Manifest
Files}), which may either be installed
On 03/16/2010 04:24 AM, Dave Korn wrote:
On 16/03/2010 06:17, Ralf Wildenhues wrote:
Microsoft @sc{dos} and Windows systems. The @sc{gnu}
Should capitalise DOS and GNU.
@sc{} does the capitalization for you. This is correct texinfo usage.
--
Eric Blake ebl...@redhat.com
On 17/03/2010 17:14, Eric Blake wrote:
On 03/16/2010 04:24 AM, Dave Korn wrote:
On 16/03/2010 06:17, Ralf Wildenhues wrote:
Microsoft @sc{dos} and Windows systems. The @sc{gnu}
Should capitalise DOS and GNU.
@sc{} does the capitalization for you. This is correct texinfo usage.
On 03/17/2010 01:23 PM, Dave Korn wrote:
On 17/03/2010 17:14, Eric Blake wrote:
On 03/16/2010 04:24 AM, Dave Korn wrote:
On 16/03/2010 06:17, Ralf Wildenhues wrote:
Microsoft @sc{dos} and Windows systems. The @sc{gnu}
Should capitalise DOS and GNU.
@sc{} does the capitalization for you.
This issue is complex enough that it warrants some explanation.
We should help our users on that front.
I'm not the w32 expert in any measure, so here's a chunk of texinfo
text that I've just run down now, without much integration, and by
stealing some of the explanations of others.
I was going
On 16/03/2010 06:17, Ralf Wildenhues wrote:
Microsoft @sc{dos} and Windows systems. The @sc{gnu}
Should capitalise DOS and GNU.
The Microsoft Vista version of Windows provides increased default
Should refer to Vista and all later versions.
and updating of system-wide software. The
On Tue, Feb 23, 2010 at 2:20 AM, Yaakov (Cygwin/X)
yselkow...@users.sourceforge.net wrote:
On 2010-02-21 06:11, Ralf Wildenhues wrote:
3) This patch will overwrite a .manifest file created in the build dir,
thus may break a package that create them through some other means.
I can't see any
Christopher Hulbert wrote:
On Tue, Feb 23, 2010 at 2:20 AM, Yaakov (Cygwin/X) wrote:
On 2010-02-21 06:11, Ralf Wildenhues wrote:
3) This patch will overwrite a .manifest file created in the build dir,
thus may break a package that create them through some other means.
I can't see any package
The only comment NOT addressed by this version is: Peter Rosin doesn't
want this code activated for msvc, but I'm not sure this patch should be
modified to guard against a compiler, whose support (in Peter's branch)
has not itself yet been merged into master. And I don't know what
symbol to use;
Ralf Wildenhues wrote:
* Charles Wilson wrote on Sun, Feb 21, 2010 at 10:09:43PM CET:
Ralf Wildenhues wrote:
If the
latter, then I don't see how the manifest file ever gets to be installed
at `make install' time, nor uninstalled at `make uninstall' time?
It was a deliberate choice -- a
On 2010-02-21 06:11, Ralf Wildenhues wrote:
3) This patch will overwrite a .manifest file created in the build dir,
thus may break a package that create them through some other means.
I can't see any package generating one of these. If a package uses a
.manifest file, it will be
Hello,
* Charles Wilson wrote on Sun, Feb 21, 2010 at 07:31:15AM CET:
[cygwin|mingw] Create UAC manifest files.
* libltdl/config/ltmain.m4sh (func_emit_exe_manifest): New
function.
(func_mode_link) [cygwin|mingw]: Create manifest files for
wrapper and target
Ralf Wildenhues wrote:
* Charles Wilson wrote on Sun, Feb 21, 2010 at 07:31:15AM CET:
[cygwin|mingw] Create UAC manifest files.
* libltdl/config/ltmain.m4sh (func_emit_exe_manifest): New
function.
(func_mode_link) [cygwin|mingw]: Create manifest files for
wrapper
Charles Wilson wrote:
2010-02-21 Yaakov Selkowitz ...
Charles Wilson ...
[cygwin|mingw] Create UAC manifest files.
* libltdl/config/ltmain.m4sh (func_emit_exe_manifest): New
function.
(func_mode_link) [cygwin|mingw]: Create manifest files for
Hi Charles,
* Charles Wilson wrote on Sun, Feb 21, 2010 at 10:09:43PM CET:
Ralf Wildenhues wrote:
If the
latter, then I don't see how the manifest file ever gets to be installed
at `make install' time, nor uninstalled at `make uninstall' time?
It was a deliberate choice -- a shortcut --
2010-02-21 Yaakov Selkowitz ...
Charles Wilson ...
[cygwin|mingw] Create UAC manifest files.
* libltdl/config/ltmain.m4sh (func_emit_exe_manifest): New
function.
(func_mode_link) [cygwin|mingw]: Create manifest files for
wrapper and target
* libt...@cwilson.fastmail.fm wrote on Wed, Jul 01, 2009 at 12:11:45AM CEST:
On Tue, 30 Jun 2009 16:23 +0200, Ralf Wildenhues wrote:
Can you convey the need for copyright assignment requirements for
nontrivial patches?
[*] The bulk of the patch is a template: there is only one way to
Den 2009-07-01 00:11 skrev libt...@cwilson.fastmail.fm:
On Tue, 30 Jun 2009 16:23 +0200, Ralf Wildenhues wrote:
Why does gcc but not msvc need them?
It does. cl.exe has a flag that causes it to automatically invoke the
MSVC manifest tool (mt? I forget), AND link the resulting object into
the
Ralf Wildenhues wrote:
But IANAL, so...
Me neither. I'm not making up these rules either, so please discuss
them with the FSF if you have an issue with them.
Nope, no issue. I didn't realize the FSF treated patches cumulatively.
You're right, Yaakov has submitted a number of these small
Hello,
* Peter Rosin wrote on Wed, Jul 01, 2009 at 09:05:53AM CEST:
On Tue, 30 Jun 2009 16:23 +0200, Ralf Wildenhues wrote:
Why does gcc but not msvc need them?
cl.exe will generate the manifest file all by itself, regardless of
executable name. My gripe was that any file created by libtool
On Wed, 01 Jul 2009 18:55 +0200, Ralf Wildenhues wrote:
* Peter Rosin wrote on Wed, Jul 01, 2009 at 09:05:53AM CEST:
On Tue, 30 Jun 2009 16:23 +0200, Ralf Wildenhues wrote:
Why does gcc but not msvc need them?
cl.exe will generate the manifest file all by itself, regardless of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Charles Wilson on 6/30/2009 6:05 AM:
The attached patch was submitted on the cygwin list by Yaakov
Selkowitz, and is currently included in the cygwin libtool
distribution. It has received some objection (notably by Peter
Rosin) over
libtool-patches-bounces+kai.tietz=onevision@gnu.org wrote on
30.06.2009 14:05:47:
* libltdl/config/ltmain.m4sh (func_emit_exe_manifest): New function.
(func_mode_link) [cygwin|mingw]: Create manifest files for wrapper
and target exe when target name matches heuristic that triggers
UAC
* Charles Wilson wrote on Tue, Jun 30, 2009 at 02:05:47PM CEST:
* libltdl/config/ltmain.m4sh (func_emit_exe_manifest): New function.
(func_mode_link) [cygwin|mingw]: Create manifest files for wrapper
and target exe when target name matches heuristic that triggers
UAC problems for newer win32
On Tue, 30 Jun 2009 16:23 +0200, Ralf Wildenhues wrote:
* Charles Wilson wrote on Tue, Jun 30, 2009 at 02:05:47PM CEST:
* libltdl/config/ltmain.m4sh (func_emit_exe_manifest): New function.
(func_mode_link) [cygwin|mingw]: Create manifest files for wrapper
and target exe when target name
Eric Blake wrote:
Do we need to worry about deleting *.manifest files at the appropriate
'make *clean' level?
Hmm. Yes, the one in the build directory (for the wrapper, or the real
exe if building without dependencies on uninstalled DLLs) probably
should be. The one in .libs/ not so much,
31 matches
Mail list logo
