From: Tonyb <tonylindee@yahoo.com>
To: gcc-help@gcc.gnu.org
Subject: Windres Documentation?
Date: Sat, 08 Feb 2014 16:00:00 -0000 [thread overview]
Message-ID: <1391875225961-1009648.post@n5.nabble.com> (raw)
I'm (still) having difficulties while trying to attempt some windows
programing using gcc and minGW. Most of my problems center around getting
resource (.rc) files accepted by gcc. I find little documentation available
to help me. And what I have found hasn't been sufficient.
For instance: certain keywords seem to be acceptable to windres -
IDR_MYMENU MENU DISCARDABLE
BEGIN
POPUP "&File"
etc.
But others cause a windres syntax error. Such as -
STYLE DS_MODALFRAME | WS_POPUP | WS_CAPTION | WS_SYSMENU
CAPTION "My About Box"
FONT 8, "MS SANS Serif"
cause problems.
The code I'm using is taken from
http://www.winprog.org/tutorial/dialogs.html, theForger's Win32 API
Programming Tutorial. So I expect it to be code that should work.
I haven't found minWG specific documentation describing these windows
keywords either. Where's that at?
I've hunted around http://www.mingw.org/wiki for help and haven't exactly
found what I think I need. However, I have found notes to make me question
whether I need to reinstall some things. Particularly in Getting Started it
says, "The preferred installation target directory is C:\MinGW" I find my
stuff in C:\CigWin\bin and C:\CigWin\lib. I installed gnu several years
ago, and I remember it being rather long and tedious, with various questions
popping up that I mostly had to guess at or use the default. I hate to go
through it again, since I have little faith that it is going to help me find
the information I'm looking for. Of course, it just might make some of my
problems magically disappear!
--
View this message in context: http://gcc.1065356.n5.nabble.com/Windres-Documentation-tp1009648.html
Sent from the gcc - Help mailing list archive at Nabble.com.
reply other threads:[~2014-02-08 16:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1391875225961-1009648.post@n5.nabble.com \
--to=tonylindee@yahoo.com \
--cc=gcc-help@gcc.gnu.org \
/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).