X-Recipient: archive-cygwin@delorie.com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:reply-to:mime-version:to
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=UOHBd9alLHRoNVaF
	0kZlgp6fP+QGa+3ns5VeA/8ZsF5taUsy83Dm62QepHv1HaOq970QZGk4qM5SX6et
	0UCK2Q6TslXW9aJYKhMSoJc3euRF5Iz+g0p+Vlw2+Z61my0zBkMYxcIfZiVqNVog
	Xdt4ZFqs6n+VcT5MXnb+1M1W+tQ=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:reply-to:mime-version:to
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=i+W5udGNwf52Bfrlux7o9P
	j8LVw=; b=uSRn8tX2NSAuOYslx2DFO/N+QEZxIrGUFv23BfHW0LXo+kk8J+JcYZ
	bg8WkSQJGO3Qwd2FZkmdCiMgCv6rOZywLfb9STzuQHcfN4wme3vDvcBdCj/BYg4u
	k1KBds1JX8QtnixmfBXlAAht4MCf1ww/wBD8iCKtwXWDp9uiaHcwU=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-1.3 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2
X-HELO: vms173025pub.verizon.net
Message-id: <53435811.6080104@cygwin.com>
Date: Mon, 07 Apr 2014 21:59:45 -0400
From: "Larry Hall (Cygwin)" <reply-to-list-only-lh@cygwin.com>
Reply-to: cygwin@cygwin.com
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-version: 1.0
To: cygwin@cygwin.com
Subject: Re: Trouble with running cygwin dll on Vortex86MX+ CPU
References: <20140404083359.GD2508@calimero.vinschen.de> <loom.20140404T113717-470@post.gmane.org> <20140404113738.GF2508@calimero.vinschen.de> <loom.20140407T124141-753@post.gmane.org> <20140407112313.GA17922@calimero.vinschen.de> <5342D299.1040101@cygwin.com> <loom.20140407T225832-327@post.gmane.org> <534322E8.8070701@cygwin.com> <alpine.LNX.2.00.1404071509070.9344@ming.fruitbat.org> <534350BD.9040806@cygwin.com> <20140408015026.GA2359@ednor.casa.cgf.cx>
In-reply-to: <20140408015026.GA2359@ednor.casa.cgf.cx>
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7bit

On 4/7/2014 9:50 PM, Christopher Faylor wrote:
> On Mon, Apr 07, 2014 at 09:28:29PM -0400, Larry Hall (Cygwin) wrote:

<snip>

>>> 2) Packaging changes of setup.exe have made extracting the version string
>>>      impossible, save for actually running setup, which isn't something I'm
>>>      going to do on a daily basis.  If there is a method of extracting this
>>>      info from it, please do tell me how.
>>
>> I'm assuming it used to just be in the RC file in the past.  Didn't look
>> in the history to trace it back.  But now it is generated and put in
>> setup_version.c as a global constant setup_version.
>
> setup.exe is packed with upx.  If you want to see the version string I
> suppose you could unpack it with upx.

Of course!  Why didn't I think of that?

strings setup*.exe | grep setup-version

This returns the version for a _decompressed_ setup executable.

-- 
Larry

_____________________________________________________________________

A: Yes.
 > Q: Are you sure?
 >> A: Because it reverses the logical flow of conversation.
 >>> Q: Why is top posting annoying in email?

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple