From: Christopher David Hundhausen <chundhau@cs.uoregon.edu>
To: gnu-win32@cygnus.com
Subject: Compiling Bison-generated parsers with MS VC++?
Date: Wed, 07 Oct 1998 09:04:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.02.9810070843070.6029-100000@ix.cs.uoregon.edu> (raw)
I've used VC++ (v 5.0) to successfully compile a flex-generated lexical
analyzer (lex.yy.cpp). I did this by using the trick of creating a dummy
(empty) uinstd.h file (this trick was recently suggested on this mailing
list).
The next step is to get VC++ to compile a bison-generated parser that
makes use of MFC classes. Does anyone have any suggestions on
how to get this to work? At present, my compilation results in
the following error messages:
/cygnus/b19/share/bison.simple(327) : error C2065: 'yyerror' : undeclared
identifier
/cygnus/b19/share/bison.simple(333) : error C2065: 'alloca' : undeclared
identifier
/cygnus/b19/share/bison.simple(387) : error C2065: 'yylex' : undeclared
identifier
Once I get the parser to compile, what will I need to do to get
everything to link properly with my MFC app? Is there a gnu-win32
object file that I need to include in the link? Does anyone have any
advice?
Please send you responses directly to me (chundhau@cs.uoregon.edu), in
addition to posting them to the list.
Thanks in advance,
:-)Chris
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
next reply other threads:[~1998-10-07 9:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-10-07 9:04 Christopher David Hundhausen [this message]
1998-10-08 7:35 ` Can you explain product relationships? David Young
1998-10-08 15:29 Compiling Bison-generated parsers with MS VC++? Kubat, Karel
1998-10-08 21:43 Michael Czapski
1998-10-08 21:43 Gilles Depeyrot
1998-10-13 0:20 Steven J. Zeil
1998-10-14 7:39 Steven J. Zeil
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=Pine.GSO.4.02.9810070843070.6029-100000@ix.cs.uoregon.edu \
--to=chundhau@cs.uoregon.edu \
--cc=gnu-win32@cygnus.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).