Re: flex for windows

Hans-Peter Diettrich <DrDiettrich1@aol.com>
Thu, 13 Dec 2007 21:05:19 +0100

          From comp.compilers
Related articles
flex for windows Horand.Gassmann@dal.ca (Gus Gassmann) (2007-12-12)
Re: flex for windows julien.hamaide@gmail.com (2007-12-12)
Re: flex for windows tprince@computer.org (Tim Prince) (2007-12-12)
Re: flex for windows timothyprince@sbcglobal.net (Tim Prince) (2007-12-13)
Re: flex for windows gneuner2@comcast.net (George Neuner) (2007-12-13)
Re: flex for windows DrDiettrich1@aol.com (Hans-Peter Diettrich) (2007-12-13)
Re: flex for windows Horand.Gassmann@dal.ca (Gus Gassmann) (2007-12-14)
Re: flex for windows timothyprince@sbcglobal.net (tim prince) (2007-12-14)
Re: flex for windows DrDiettrich1@aol.com (Hans-Peter Diettrich) (2008-01-06)
Re: flex for windows DrDiettrich1@aol.com (Hans-Peter Diettrich) (2008-01-06)
Re: flex for windows dickey@saltmine.radix.net (Thomas Dickey) (2008-01-06)
Re: flex for windows dickey@saltmine.radix.net (Thomas Dickey) (2008-01-06)
[6 later articles]
| List of all articles for this month |
From: Hans-Peter Diettrich <DrDiettrich1@aol.com>
Newsgroups: comp.compilers,comp.lang.c
Date: Thu, 13 Dec 2007 21:05:19 +0100
Organization: Compilers Central
References: 07-12-040 07-12-043 07-12-047
Keywords: lex, Windows, C
Posted-Date: 14 Dec 2007 00:17:54 EST

Tim Prince wrote:


> Part of the problem seems to be that flex has added features which
> can't be supported fully without some posix environment. There are
> plenty of suggestions on line about flex for mingw. You can't say you
> want cygwin capabilities and in the same breath you want everything to
> happen automagically without them.


I don't think that a tool like flex really depends on special POSIX
features, apart from the file handling. More problems will result from
the autobloat implementation, where more platform specific (filesystem
related) features may be required.


My solution for that problem is a Linux box, where ./configure already
works, then compiling the configured sources under the actual target
system (Windows), with "native" tools. Cygwin and MinGW frequently
fail to configure, with ridiculous error messages like "compiler
cannot create executable files". In most cases it's sufficient to link
the result with Windows-specific wrappers around fopen() and similar
filesystem specific functions, to make the code work.


DoDi


Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.