I only building with the IDE, it embeds the manifests auto.
For a command-line build I should advise:
Do not clutter the makefiles with specific VC2005 stuff,
but use a .bat file to embed the manifests, so no external manifest files:
manifestVC2005.bat
mt -manifest ab.exe.manifest -outputresource:ab.exe;1
mt -manifest httpd.exe.manifest -outputresource:httpd.exe;1
mt -manifest rotatelogs.exe.manifest -outputresource:rotatelogs.exe;1
...
...
mt -manifest mod_actions.so.manifest -outputresource:mod_actions.so;1
mt -manifest mod_alias.so.manifest -outputresource:mod_alias.so;1
...
...
etc. etc.
Steffen
----- Original Message -----
From: "William A. Rowe, Jr." <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Saturday, January 06, 2007 20:21
Subject: Re: [VOTE] httpd-2.2.4 release candidate for review
William A. Rowe, Jr. wrote:
Gustavo Lopes wrote:
No problems compiling (with openssl0.9.8d and zlib1.2.3) with visual
studio 2005 from the command line, except for the usual trouble with the
manifest files.
What trouble? All the libraries/exe's have a post build step that does
this.
Going back to a virgin unpack of the -src.zip - can you point out the
exact
issue you encountered?
Nevermind - I see we apparently haven't finished backporting the .manifest
work from SVN trunk/ (the 2.3 development branch).
I *really* like your hack Gustavo :)
Steffan - given that you aren't having issues either, which hack did you
use
for the .manifest data?
Bill
