From: Mark Geisert <mark@maxrnd.com>
To: cygwin@cygwin.com
Subject: Re: Can't link .res file (from windres) using i686-pc-mingw32-g++
Date: Thu, 25 Feb 2016 04:29:00 -0000 [thread overview]
Message-ID: <56CE833C.2040200@maxrnd.com> (raw)
In-Reply-To: <CAK-n8j6Uq2c-a_Vz1nWq3aZSH6L8yzq5xh3ipOPUqJ+yjPAaNw@mail.gmail.com>
Jim Reisert AD1C wrote:
> I have a 64-bit Cygwin environment. I'm trying to compile a 32-bit
> (target) Windows program using i686-pc-mingw32-g++
>
> # i686-pc-mingw32-g++ -g -Wall -Iinclude -I../../library/include -c
> -o NPOTAdlg.o NPOTAdlg.cpp
> # windres -Iinclude res/NPOTAdlg.rc -O coff -o res/NPOTAdlg.res
> # i686-pc-mingw32-g++ -s -mwindows -static-libgcc -static-libstdc++
> -lwininet NPOTA.o NPOTAdlg.o res/NPOTAdlg.res ../../library/library.a
> /usr/i686-pc-mingw32/sys-root/mingw/lib/libwininet.a -o NPOTA
>
> But I get this error on the link (last) step:
>
> res/NPOTAdlg.res: file not recognized: File format not recognized
>
> This program is a clone of another program I wrote a couple of years
> ago (I wanted to re-use the Windows framework I had developed).
> However, at that time, I was using 32-bit Cygwin, not 64-bit Cygwin.
>
> Is there a work-around for this, other than re-creating a 32-bit
> Cygwin environment?
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. Good luck.
..mark
--
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
next prev parent reply other threads:[~2016-02-25 4:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-25 3:57 Jim Reisert AD1C
2016-02-25 4:29 ` Mark Geisert [this message]
2016-02-25 5:18 ` Tony Kelman
2016-02-25 14:50 ` Jim Reisert AD1C
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56CE833C.2040200@maxrnd.com \
--to=mark@maxrnd.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).