X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 tests=AWL,BAYES_00,J_CHICKENPOX_28,SPF_PASS X-Spam-Check-By: sourceware.org Message-ID: <4A27E612.2030400@users.sourceforge.net> Date: Thu, 04 Jun 2009 10:19:46 -0500 From: "Yaakov (Cygwin/X)" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1b3pre) Gecko/20090223 Thunderbird/3.0b2 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: UAC .manifest files References: <4A25FA67 DOT 4050805 AT users DOT sourceforge DOT net> <20090603081102 DOT GI23519 AT calimero DOT vinschen DOT de> <20090604082551 DOT GB29270 AT calimero DOT vinschen DOT de> <20090604113038 DOT GF21472 AT trikaliotis DOT net> <4A27C9DA DOT 5020609 AT cwilson DOT fastmail DOT fm> In-Reply-To: <4A27C9DA.5020609@cwilson.fastmail.fm> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On 04/06/2009 08:19, Charles Wilson wrote: > Spiro Trikaliotis wrote: > >> - let my.manifest be the manifest file >> - Generate a .rc file with the line: >> 1 RT_MANIFEST "my.manifest" >> - Let the resource compiler handle the .rc file, and let windres merge >> the info into the executable. > > Sounds like a job for automake, not gcc. I don't see anything here > http://autoconf-archive.cryp.to/macros-by-category.html#AUTOMAKE yet, tho. I concur; this is not within the realm of gcc to handle by itself. There are a number of GTK+ packages which include windres .rc files, but it takes all sorts of automake hacking to do it (all within an AM_CONDITIONAL, of course). As for packages which don't use autotools, good luck. Either way, we don't want to go that route. Yaakov -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/