To use win_flex.exe or win_bison.exe (no matter from VS 2019 or standalone) you should add path to executables to PATH env variable.
you should use '-d' option for bison. see https://stackoverflow.com/questions/47726404/how-to-put-header-file-to-tab-h-in-bison for reference win_bison.exe -d test.y
I duplicated issue on github. Will fix it there
use of %define parser_class_name results in m4eof text in output file
It seems I managed to fix it. Please test win_bison executable attached.
could you tell me which version of M4 tool was used in Linux that successfully works?
Thank you for report. I have reproduced this. Will look into it.
Thank you for report. I have reproduced this. Will look inti it.
Flex C++ lexer redefines stdint.h macros
How to sample files
Availability of Bison 3.0.4?
There are some tools for Visual Studio Code: https://marketplace.visualstudio.com/items?itemName=faustinoaq.lex-flex-yacc-bison https://marketplace.visualstudio.com/items?itemName=se2dev.vscode-yacc https://marketplace.visualstudio.com/items?itemName=luniclynx.bison
win_bison (v2.5.9) uses old 'data' files?
it seems your Lexer.l file is not compatible with the latest GNU flex tool. may be older version will help or your Lexer.l file was previously processed by very different tool
Can you go to "C:\VSTS\ABI\Src\ExpCompile\ConsoleApplication1\" folder and run win_flex.exe --outfile="Lexer.flex.cpp" --wincompat --lex-compat --c++ "Lexer.l" there? Do you have Lexer.l in this folder? Does the command produce Lexer.flex.cpp file?
Hi GS, The first thing I suggest to check is if path to win_flex.exe and win_bison.exe is added to PATH environment variable. Regards, Alex
Hello GS, Win flex and bison executables are 32 bit. But why do you care? Any windows system runs 32 bit applications. Generated C scanners and parsers code could be used in any projects 32 or 64 bit.
I have made the changes and upload new pachage https://sourceforge.net/projects/winflexbison/files/old_versions/win_flex_bison-2.5.10.zip/download I have no scripts to deeply test it, so please check it and reply if everything is ok.
FlexLexer.h out of sync with Flex generated C++ lexer
OK, I will look into it
I don't have access to any win CE system. So I had no chance to test winflexbison...
I have not been working with VS 2010 for a long time. I can only guess if YYSTYPE...
updated. Please check
You are right. Will update package ASAP
OK, I will check
How to sample files
Sorry I'm not an expert in flex/bison tools. Just adopted their code to windows....
Syntax error, unexpected TOKEN, expecting $end
Actually I'm not familiar with flex/bison syntax. Try to find solution or ask your...
win_bison version 3.0.4 has been published
Availability of Bison 3.0.4?
Split Flex / Bison target/props/xml into 2 separates taget/propos/xml group
Done in 2.5.6 version See https://sourceforge.net/projects/winflexbison/files/wi...
Hello Sebastian, thank you for such positive estimation of my work. The first two...
Hello Sebastian, thank you for such positive estimation of my work. The first two...
I will publish this release here after some testing. I appreciate if you can test...
Yes, I've done it a couple days ago. Please check if my resease OK and has fixes...
OK. Wiil do it in a month and a half.
You can grab example flex and bison files from there flex-bison-example I've tried...
ok, I will do it in a few days
Visual Studio Express 2015
Hi Paul, You should not specify full path to winflexbison executables in your project,...
Hi Paul, What VS package are you talking about? Do you mean win_flex.vcxproj and...
Hi Alexey, I've tried to use [:alpha:] expression in flex file. But I did discover...
Привет Алексей, какие-то проблемы на сайте SourceForge, поэтому отвечаю письмом....
It should generate "C" parser code now. Do you mean generated files should be processed...
Hi Francis, Please give me an example what do you mean? Is it not enough to run "win_flex...
It was an error. I added permitions to anyone to create tickets.
Hi James, I think we should continue this topic via e-mail. Please send me your OBJFormatScanner.l...
I've updated winflexbison package. Now custom build rules should work correctly.
Hi James, Actually I'm not familiar with C++ scanners. I agree it seems like your...
Hi James, I believe you can add "--yyclass=S" option to "Command Line"->"Additional...
Thank you! There is a typo in win_flex_bison_custom_build.props file. I've fixed...
Hi Daniel, actually in this minor release I only updated custom build rules files...
Hi Mac! Thank you for notice. I've checked and had the same problem. I fixed it:...
Visual Studio custom build rules
I think you are looking for %option header-file="FILE" option. You can find description...
Hi Nasi! Thank you for your review and rating of winflexbison. To learn flex/bison...
Visual Studio custom build rules
Visual Studio custom build rules
Hi walshy002000, Sorry for delay. I will investigate your issue. Just for sure: Did...
Now winflexbison version 2.4.3 available in Chocolatey
OK. It's my fault - I moved win_flex_bison-2.4.1.zip into subfolder. Are you sure...
You are welcome! In case any other questions feel free to ask here. I will try to...
Hi David! I've updated winflexbison package with fix from your link https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=542482....
Hi David! Thank you for investigation. I'll update win_flex to the latest version...
Thank you David! I will check and fix it. Do you know if this bug exists in original...
I've added wiki page to explain Custom Build Rules.
Visual Studio custom build rules
Visual Studio custom build rules
Visual Studio custom build rules
Visual Studio custom build rules
Visual Studio custom build rules
Visual Studio custom build rules
Visual Studio custom build rules
Visual Studio custom build rules
Visual Studio custom build rules
Visual Studio custom build rules
Visual Studio custom build rules
Visual Studio custom build rules
Visual Studio custom build rules
Visual Studio custom build rules
add
Visual Studio custom build rules
Hi Michael! I've added winflexbison_cusom_build.zip archive to Files section. Please...