X-Recipient: archive-cygwin AT delorie DOT 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:mime-version:in-reply-to:references:date
	:message-id:subject:from:to:content-type; q=dns; s=default; b=Tv
	Ht/I5jtJdDpiYj2q3Ff7ZMDucUe2HvTVMvTa1ZOzaslLkKdKFTFPQGYN8PsfFZJW
	vWMdXsDboEPpgMmyR5WkZPn8wp2Ekl9qs3wU3XHo+fp6UF8iGj5HIMqqYJtU7RZk
	eI1+HvKkTfBpr9N2x9z0EOP/HVlPMZoVo9IZj/aPw=
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:mime-version:in-reply-to:references:date
	:message-id:subject:from:to:content-type; s=default; bh=/KZl63he
	p8wsBGRwdUth+sxvsjg=; b=YIRC44mv4J85/klPp0CY18q0qp9iPWjxBysM1zmS
	mnvbJJ38UeaimWU/6p7xKWM+5C/HjAyYzzDr14m8tpsqn+WiVP210AVZlVI5K/rq
	anQ4BVbCJcvHqt1l1fnYFfckbQLmdym5PPdzWmVSEjRDvTz5GFlFUAmGFmp00O1B
	OnM=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT 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_50,KAM_INFOUSMEBIZ,SPF_PASS autolearn=no version=3.3.2 spammy=coff, UD:us, windres, reisert
X-HELO: alum-mailsec-scanner-8.mit.edu
X-Gm-Message-State: AG10YOT8Z4PIqCB7MzJeUqZkkqE5fLqzEk40Cl4wID9RtZLTQSNx0n+1dmbiWZR7wVjiR9UyDtG1Cjn6kZJ1ng==
MIME-Version: 1.0
X-Received: by 10.107.153.200 with SMTP id b191mr3352295ioe.54.1456411837145; Thu, 25 Feb 2016 06:50:37 -0800 (PST)
In-Reply-To: <56CE833C.2040200@maxrnd.com>
References: <CAK-n8j6Uq2c-a_Vz1nWq3aZSH6L8yzq5xh3ipOPUqJ+yjPAaNw AT mail DOT gmail DOT com>	<56CE833C DOT 2040200 AT maxrnd DOT com>
Date: Thu, 25 Feb 2016 07:50:37 -0700
X-Gmail-Original-Message-ID: <CAK-n8j5-EStXtUSMk50K_89rTpdcDu7iY8Y2379cgj+bFgsGdQ AT mail DOT gmail DOT com>
Message-ID: <CAK-n8j5-EStXtUSMk50K_89rTpdcDu7iY8Y2379cgj+bFgsGdQ@mail.gmail.com>
Subject: Re: Can't link .res file (from windres) using i686-pc-mingw32-g++
From: Jim Reisert AD1C <jjreisert AT alum DOT mit DOT edu>
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=UTF-8
X-IsSubscribed: yes

On Wed, Feb 24, 2016 at 9:29 PM, Mark Geisert wrote:

> Just a guess: your 64-bit windres is generating a 64-bit .res file that the
> 32-bit g++ can't grok.  Look at 'windres -h'.  There's a "-F" == "--target"
> flag that can specify a target type.  I would try adding "-F pe-i386" after
> the "-O coff" on your command.  If windres doesn't accept both -O and -F,
> try leaving off the "-O coff" and just specify the -F flag and value.

Thanks, Mark, that worked! I assumed that -O coff would "do the right
thing" by itself.  I did not realize that "format" and "target" were
independent.  I finally read somewhere that by default, windres picks
the target that is listed first when getting help via "-h".  In my
case that was pe-x86-64, which was wrong for what I wanted to do.

- Jim

-- 
Jim Reisert AD1C, <jjreisert AT alum DOT mit DOT edu>, http://www.ad1c.us

--
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