Thread: [Doxygen-users] Doxygen-1.5.7.1-20111117 in SVN
Brought to you by:
dimitri
From: Dimitri v. H. <di...@st...> - 2011-11-17 21:38:24
|
Hi, With this update the following has changed: ------------------------------------------------------------------------------ + CHG: Included redesigned VHDL parser (thanks to Martin Kreis for the patch) + CHG: The selected member is now briefly highlighted in the HTML output (when GENERATE_TREEVIEW is enabled). + CHG: Improved support for IE9. + BUG: id 625518: Fortran: first problem where subroutine using results variable appeared as a function. + BUG: id 654153: If an URL appeared at the end of a sentence, the period was included in the URL. + BUG: id 656560: Fortran: Added support for the Double Complex type. + BUG: id 663640: Included workaround for Solaris CC issue in index.cpp + BUG: id 662190: Included patch to fix some TCL issues and add the TCL_SUBST configuration option. ------------------------------------------------------------------------------ Enjoy, Dimitri |
From: Jaco N. <nau...@gm...> - 2011-11-18 05:38:10
|
Hi Dimitri Thanks for the continued improvements! Where can I get more info about the VHDL parser updates? Would love to see improved support for VHDL. Thanks, Jaco On Thu, Nov 17, 2011 at 11:38 PM, Dimitri van Heesch <di...@st...>wrote: > Hi, > > With this update the following has changed: > > ------------------------------------------------------------------------------ > + CHG: Included redesigned VHDL parser (thanks to Martin Kreis for the > patch) > + CHG: The selected member is now briefly highlighted in the HTML output > (when GENERATE_TREEVIEW is enabled). > + CHG: Improved support for IE9. > + BUG: id 625518: Fortran: first problem where subroutine using results > variable appeared as a function. > + BUG: id 654153: If an URL appeared at the end of a sentence, the period > was included in the URL. > + BUG: id 656560: Fortran: Added support for the Double Complex type. > + BUG: id 663640: Included workaround for Solaris CC issue in index.cpp > + BUG: id 662190: Included patch to fix some TCL issues and add the > TCL_SUBST > configuration option. > > ------------------------------------------------------------------------------ > Enjoy, > Dimitri > > > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure > contains a definitive record of customers, application performance, > security threats, fraudulent activity, and more. Splunk takes this > data and makes sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-novd2d > _______________________________________________ > Doxygen-users mailing list > Dox...@li... > https://lists.sourceforge.net/lists/listinfo/doxygen-users > |
From: Jens S. <Jen...@t-...> - 2011-11-18 17:58:31
|
On Thu, 17 Nov 2011, Dimitri van Heesch wrote: > Hi, > > With this update the following has changed: > ------------------------------------------------------------------------------ > + CHG: Included redesigned VHDL parser (thanks to Martin Kreis for the patch) > + CHG: The selected member is now briefly highlighted in the HTML output > (when GENERATE_TREEVIEW is enabled). > + CHG: Improved support for IE9. > + BUG: id 625518: Fortran: first problem where subroutine using results > variable appeared as a function. > + BUG: id 654153: If an URL appeared at the end of a sentence, the period > was included in the URL. > + BUG: id 656560: Fortran: Added support for the Double Complex type. > + BUG: id 663640: Included workaround for Solaris CC issue in index.cpp > + BUG: id 662190: Included patch to fix some TCL issues and add the TCL_SUBST > configuration option. > ------------------------------------------------------------------------------ The "redesigned VHDL parser" makes compile problems: g++ -c -pipe -fno-exceptions -fno-rtti -D_LARGEFILE_SOURCE -Wall -W -fno-exceptions -O2 -I../qtools -I../libmd5 -o ../objects/vhdlparser.o vhdlparser.cpp vhdlparser.cpp: In function ‘void createFunction(QCString, int, QCString)’: vhdlparser.cpp:316:8: error: ‘t_PROCEDURE’ was not declared in this scope vhdlparser.cpp:321:8: error: ‘t_FUNCTION’ was not declared in this scope vhdlparser.cpp:326:8: error: ‘t_PROCESS’ was not declared in this scope Used gcc version 4.5.1 20101208 [gcc-4_5-branch revision 167585] (SUSE Linux) and bison (GNU Bison) 2.4.1. Any ideas? Sorry, I'm not a C++ respectively yacc/bison expert. Jens |
From: Dimitri V. H. <do...@gm...> - 2011-11-19 10:27:40
|
Hi Jens, On Nov 18, 2011, at 18:58 , Jens Schleusener wrote: > On Thu, 17 Nov 2011, Dimitri van Heesch wrote: > > > The "redesigned VHDL parser" makes compile problems: > > g++ -c -pipe -fno-exceptions -fno-rtti -D_LARGEFILE_SOURCE -Wall -W > -fno-exceptions -O2 -I../qtools -I../libmd5 -o ../objects/vhdlparser.o > vhdlparser.cpp > vhdlparser.cpp: In function ‘void createFunction(QCString, int, QCString)’: > vhdlparser.cpp:316:8: error: ‘t_PROCEDURE’ was not declared in this scope > vhdlparser.cpp:321:8: error: ‘t_FUNCTION’ was not declared in this scope > vhdlparser.cpp:326:8: error: ‘t_PROCESS’ was not declared in this scope > > Used gcc version 4.5.1 20101208 [gcc-4_5-branch revision 167585] (SUSE Linux) and bison (GNU Bison) 2.4.1. > > Any ideas? No, this is rather strange. I don't see this myself using the same version of bison on my Linux box. Can you try to manually delete src/vhdlparser.cpp and src/vhdlparser.h and run make again? If that also don't help, please send me the generated src/vhdlparser.cpp file for analysis. Regards, Dimitri |
From: Jens S. <Jen...@t-...> - 2011-11-19 11:31:59
|
Hi Dimitri, > On Nov 18, 2011, at 18:58 , Jens Schleusener wrote: >> On Thu, 17 Nov 2011, Dimitri van Heesch wrote: >> >> >> The "redesigned VHDL parser" makes compile problems: >> >> g++ -c -pipe -fno-exceptions -fno-rtti -D_LARGEFILE_SOURCE -Wall -W >> -fno-exceptions -O2 -I../qtools -I../libmd5 -o ../objects/vhdlparser.o >> vhdlparser.cpp >> vhdlparser.cpp: In function ‘void createFunction(QCString, int, QCString)’: >> vhdlparser.cpp:316:8: error: ‘t_PROCEDURE’ was not declared in this scope >> vhdlparser.cpp:321:8: error: ‘t_FUNCTION’ was not declared in this scope >> vhdlparser.cpp:326:8: error: ‘t_PROCESS’ was not declared in this scope >> >> Used gcc version 4.5.1 20101208 [gcc-4_5-branch revision 167585] (SUSE Linux) and bison (GNU Bison) 2.4.1. >> >> Any ideas? > > No, this is rather strange. I don't see this myself using the same version of bison on my Linux box. > Can you try to manually delete src/vhdlparser.cpp and src/vhdlparser.h and run make again? That didn't help. But there was only a src/vhdlparser.cpp file and no src/vhdlparser.h file. Maybe that is the real problem. > If that also don't help, please send me the generated src/vhdlparser.cpp file for analysis. I will sent it to you in a PM. Thanks Jens |
From: Dimitri V. H. <do...@gm...> - 2011-11-19 13:11:34
|
Hi Jens, On Nov 19, 2011, at 12:31 , Jens Schleusener wrote: > Hi Dimitri, > >> On Nov 18, 2011, at 18:58 , Jens Schleusener wrote: >>> On Thu, 17 Nov 2011, Dimitri van Heesch wrote: >>> >>> >>> The "redesigned VHDL parser" makes compile problems: >>> >>> g++ -c -pipe -fno-exceptions -fno-rtti -D_LARGEFILE_SOURCE -Wall -W >>> -fno-exceptions -O2 -I../qtools -I../libmd5 -o ../objects/vhdlparser.o >>> vhdlparser.cpp >>> vhdlparser.cpp: In function ‘void createFunction(QCString, int, QCString)’: >>> vhdlparser.cpp:316:8: error: ‘t_PROCEDURE’ was not declared in this scope >>> vhdlparser.cpp:321:8: error: ‘t_FUNCTION’ was not declared in this scope >>> vhdlparser.cpp:326:8: error: ‘t_PROCESS’ was not declared in this scope >>> >>> Used gcc version 4.5.1 20101208 [gcc-4_5-branch revision 167585] (SUSE Linux) and bison (GNU Bison) 2.4.1. >>> >>> Any ideas? >> >> No, this is rather strange. I don't see this myself using the same version of bison on my Linux box. >> Can you try to manually delete src/vhdlparser.cpp and src/vhdlparser.h and run make again? > > That didn't help. But there was only a src/vhdlparser.cpp file and no src/vhdlparser.h file. Maybe that is the real problem. > >> If that also don't help, please send me the generated src/vhdlparser.cpp file for analysis. > > I will sent it to you in a PM. Thanks, I found the problem and updated SVN. Let me know if compiles now. Regards, Dimitri |
From: Jens S. <Jen...@t-...> - 2011-11-19 13:44:49
|
Hi Dimitri, > On Nov 19, 2011, at 12:31 , Jens Schleusener wrote: > >> Hi Dimitri, >> >>> On Nov 18, 2011, at 18:58 , Jens Schleusener wrote: >>>> On Thu, 17 Nov 2011, Dimitri van Heesch wrote: >>>> >>>> >>>> The "redesigned VHDL parser" makes compile problems: >>>> >>>> g++ -c -pipe -fno-exceptions -fno-rtti -D_LARGEFILE_SOURCE -Wall -W >>>> -fno-exceptions -O2 -I../qtools -I../libmd5 -o ../objects/vhdlparser.o >>>> vhdlparser.cpp >>>> vhdlparser.cpp: In function ‘void createFunction(QCString, int, QCString)’: >>>> vhdlparser.cpp:316:8: error: ‘t_PROCEDURE’ was not declared in this scope >>>> vhdlparser.cpp:321:8: error: ‘t_FUNCTION’ was not declared in this scope >>>> vhdlparser.cpp:326:8: error: ‘t_PROCESS’ was not declared in this scope >>>> >>>> Used gcc version 4.5.1 20101208 [gcc-4_5-branch revision 167585] (SUSE Linux) and bison (GNU Bison) 2.4.1. >>>> >>>> Any ideas? >>> >>> No, this is rather strange. I don't see this myself using the same version of bison on my Linux box. >>> Can you try to manually delete src/vhdlparser.cpp and src/vhdlparser.h and run make again? >> >> That didn't help. But there was only a src/vhdlparser.cpp file and no src/vhdlparser.h file. Maybe that is the real problem. >> >>> If that also don't help, please send me the generated src/vhdlparser.cpp file for analysis. >> >> I will sent it to you in a PM. > > Thanks, I found the problem and updated SVN. Let me know if compiles now. Great, it compiles now well (and after compilation I found now also a src/vhdlparser.h). Thanks for your quick help Jens |
From: Albert <alb...@gm...> - 2011-11-19 14:33:26
|
Hi Dimitri, Just checked out version 788 from svn. Tried to compile it on windows. With cygwin no problem, with Visiual C 2008 express I get the error messages: 4>Executing Lex for d:\Programs\Doxygen\Doxygen-.distr\doxygen-788\src\/vhdlcode.cpp ... 4>Running bison on vhdlparser.y 4>d:\programs\doxygen\doxygen-.distr\doxygen-788\src\\..\src\vhdlparser.y:324: unrecognized: %debug 4>d:\programs\doxygen\doxygen-.distr\doxygen-788\src\\..\src\vhdlparser.y:324: Skipping to next % 4>d:\programs\doxygen\doxygen-.distr\doxygen-788\src\\..\src\vhdlparser.y:327: unrecognized: %initial_action 4>d:\programs\doxygen\doxygen-.distr\doxygen-788\src\\..\src\vhdlparser.y:327: Skipping to next % 4>d:\programs\doxygen\doxygen-.distr\doxygen-788\src\\..\src\vhdlparser.y:367: invalid input: ; 4>d:\programs\doxygen\doxygen-.distr\doxygen-788\src\\..\src\vhdlparser.y:379: type clash (`' `qstr') on default action ..... 4>d:\programs\doxygen\doxygen-.distr\doxygen-788\src\\..\src\vhdlparser.y:1956: type clash (`' `qstr') on default action 4>Could Not Find d:\Programs\Doxygen\Doxygen-.distr\doxygen-788\src\vhdlparser.c 4>d:\programs\doxygen\doxygen-.distr\doxygen-788\src\\..\src\vhdlparser.y:324: unrecognized: %debug 4>d:\programs\doxygen\doxygen-.distr\doxygen-788\src\\..\src\vhdlparser.y:324: Skipping to next % 4>d:\programs\doxygen\doxygen-.distr\doxygen-788\src\\..\src\vhdlparser.y:327: unrecognized: %initial_action 4>d:\programs\doxygen\doxygen-.distr\doxygen-788\src\\..\src\vhdlparser.y:327: Skipping to next % 4>d:\programs\doxygen\doxygen-.distr\doxygen-788\src\\..\src\vhdlparser.y:367: invalid input: ; 4>d:\programs\doxygen\doxygen-.distr\doxygen-788\src\\..\src\vhdlparser.y:379: type clash (`' `qstr') on default action ...... 4>d:\programs\doxygen\doxygen-.distr\doxygen-788\src\\..\src\vhdlparser.y:1956: type clash (`' `qstr') on default action 4>Project : error PRJ0002 : Error result 1 returned from 'C:\Windows\SysWow64\cmd.exe'. No doxygen.exe is created (doxytag.exe was created). There were no problems with older versions of Doxygen (783 and earlier). Looks like the bison version of on the UnxUtils is a bit outdated (version 1.28; cygwin 2.4.2) Best Regards, Albert On Sat, Nov 19, 2011 at 14:44, Jens Schleusener < Jen...@t-...> wrote: > Hi Dimitri, > > > On Nov 19, 2011, at 12:31 , Jens Schleusener wrote: >> >> Hi Dimitri, >>> >>> On Nov 18, 2011, at 18:58 , Jens Schleusener wrote: >>>> >>>>> On Thu, 17 Nov 2011, Dimitri van Heesch wrote: >>>>> >>>>> >>>>> The "redesigned VHDL parser" makes compile problems: >>>>> >>>>> g++ -c -pipe -fno-exceptions -fno-rtti -D_LARGEFILE_SOURCE -Wall -W >>>>> -fno-exceptions -O2 -I../qtools -I../libmd5 -o ../objects/vhdlparser.o >>>>> vhdlparser.cpp >>>>> vhdlparser.cpp: In function ‘void createFunction(QCString, int, >>>>> QCString)’: >>>>> vhdlparser.cpp:316:8: error: ‘t_PROCEDURE’ was not declared in this >>>>> scope >>>>> vhdlparser.cpp:321:8: error: ‘t_FUNCTION’ was not declared in this >>>>> scope >>>>> vhdlparser.cpp:326:8: error: ‘t_PROCESS’ was not declared in this scope >>>>> >>>>> Used gcc version 4.5.1 20101208 [gcc-4_5-branch revision 167585] (SUSE >>>>> Linux) and bison (GNU Bison) 2.4.1. >>>>> >>>>> Any ideas? >>>>> >>>> >>>> No, this is rather strange. I don't see this myself using the same >>>> version of bison on my Linux box. >>>> Can you try to manually delete src/vhdlparser.cpp and src/vhdlparser.h >>>> and run make again? >>>> >>> >>> That didn't help. But there was only a src/vhdlparser.cpp file and no >>> src/vhdlparser.h file. Maybe that is the real problem. >>> >>> If that also don't help, please send me the generated >>>> src/vhdlparser.cpp file for analysis. >>>> >>> >>> I will sent it to you in a PM. >>> >> >> Thanks, I found the problem and updated SVN. Let me know if compiles now. >> > > Great, it compiles now well (and after compilation I found now also a > src/vhdlparser.h). > > Thanks for your quick help > > Jens > > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure > contains a definitive record of customers, application performance, > security threats, fraudulent activity, and more. Splunk takes this > data and makes sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-novd2d > _______________________________________________ > Doxygen-users mailing list > Dox...@li... > https://lists.sourceforge.net/lists/listinfo/doxygen-users > > |
From: Dimitri V. H. <do...@gm...> - 2011-11-19 15:16:32
|
On Nov 19, 2011, at 15:33 , Albert wrote: > Hi Dimitri, > > Just checked out version 788 from svn. Tried to compile it on windows. With cygwin no problem, with Visiual C 2008 express I get the error messages: > > 4>Executing Lex for d:\Programs\Doxygen\Doxygen-.distr\doxygen-788\src\/vhdlcode.cpp ... > 4>Running bison on vhdlparser.y > 4>d:\programs\doxygen\doxygen-.distr\doxygen-788\src\\..\src\vhdlparser.y:324: unrecognized: %debug > 4>d:\programs\doxygen\doxygen-.distr\doxygen-788\src\\..\src\vhdlparser.y:324: Skipping to next % > 4>d:\programs\doxygen\doxygen-.distr\doxygen-788\src\\..\src\vhdlparser.y:327: unrecognized: %initial_action > 4>d:\programs\doxygen\doxygen-.distr\doxygen-788\src\\..\src\vhdlparser.y:327: Skipping to next % > 4>d:\programs\doxygen\doxygen-.distr\doxygen-788\src\\..\src\vhdlparser.y:367: invalid input: ; > 4>d:\programs\doxygen\doxygen-.distr\doxygen-788\src\\..\src\vhdlparser.y:379: type clash (`' `qstr') on default action > ..... > 4>d:\programs\doxygen\doxygen-.distr\doxygen-788\src\\..\src\vhdlparser.y:1956: type clash (`' `qstr') on default action > 4>Could Not Find d:\Programs\Doxygen\Doxygen-.distr\doxygen-788\src\vhdlparser.c > 4>d:\programs\doxygen\doxygen-.distr\doxygen-788\src\\..\src\vhdlparser.y:324: unrecognized: %debug > 4>d:\programs\doxygen\doxygen-.distr\doxygen-788\src\\..\src\vhdlparser.y:324: Skipping to next % > 4>d:\programs\doxygen\doxygen-.distr\doxygen-788\src\\..\src\vhdlparser.y:327: unrecognized: %initial_action > 4>d:\programs\doxygen\doxygen-.distr\doxygen-788\src\\..\src\vhdlparser.y:327: Skipping to next % > 4>d:\programs\doxygen\doxygen-.distr\doxygen-788\src\\..\src\vhdlparser.y:367: invalid input: ; > 4>d:\programs\doxygen\doxygen-.distr\doxygen-788\src\\..\src\vhdlparser.y:379: type clash (`' `qstr') on default action > ...... > 4>d:\programs\doxygen\doxygen-.distr\doxygen-788\src\\..\src\vhdlparser.y:1956: type clash (`' `qstr') on default action > 4>Project : error PRJ0002 : Error result 1 returned from 'C:\Windows\SysWow64\cmd.exe'. > > No doxygen.exe is created (doxytag.exe was created). > > There were no problems with older versions of Doxygen (783 and earlier). Looks like the bison version of on the UnxUtils is a bit outdated (version 1.28; cygwin 2.4.2) Indeed that seems to be related to this problem. Can you try this one: http://gnuwin32.sourceforge.net/packages/bison.htm and let me know if that helps? Regards, Dimitri |
From: Albert <alb...@gm...> - 2011-11-19 15:51:40
|
Hi Dimitri, Specified error is gone but a new ones appeared: 3>d:\programs\doxygen\doxygen-.distr\doxygen-788\src\vhdlscanner.l(281) : error C2065: 'vhdlScanYYtext' : undeclared identifier 3>d:\programs\doxygen\doxygen-.distr\doxygen-788\src\vhdlscanner.cpp(1265) : error C2065: 'vhdlScanYYleng' : undeclared identifier 4>d:\programs\doxygen\doxygen-.distr\doxygen-788\src\vhdlscanner.l(381) : error C2065: 'vhdlScanYYleng' : undeclared identifier 3>d:\programs\doxygen\doxygen-.distr\doxygen-788\src\vhdlscanner.l(713) : error C3861: 'vhdlScanYYlex': identifier not found 3>d:\programs\doxygen\doxygen-.distr\doxygen-788\src\vhdlscanner.l(749) : error C2065: 'vhdlScanYYin' : undeclared identifier 3>d:\programs\doxygen\doxygen-.distr\doxygen-788\src\vhdlscanner.l(749) : error C3861: 'vhdlScanYYrestart': identifier not found (some multiple times) So I installed flex from: http://gnuwin32.sourceforge.net/packages/flex.htmbut this didn't help either. Best Regards, Albert On Sat, Nov 19, 2011 at 16:16, Dimitri Van Heesch <do...@gm...> wrote: > > On Nov 19, 2011, at 15:33 , Albert wrote: > > > Hi Dimitri, > > > > Just checked out version 788 from svn. Tried to compile it on windows. > With cygwin no problem, with Visiual C 2008 express I get the error > messages: > > > > 4>Executing Lex for > d:\Programs\Doxygen\Doxygen-.distr\doxygen-788\src\/vhdlcode.cpp ... > > 4>Running bison on vhdlparser.y > > > 4>d:\programs\doxygen\doxygen-.distr\doxygen-788\src\\..\src\vhdlparser.y:324: > unrecognized: %debug > > > 4>d:\programs\doxygen\doxygen-.distr\doxygen-788\src\\..\src\vhdlparser.y:324: > Skipping to next % > > > 4>d:\programs\doxygen\doxygen-.distr\doxygen-788\src\\..\src\vhdlparser.y:327: > unrecognized: %initial_action > > > 4>d:\programs\doxygen\doxygen-.distr\doxygen-788\src\\..\src\vhdlparser.y:327: > Skipping to next % > > > 4>d:\programs\doxygen\doxygen-.distr\doxygen-788\src\\..\src\vhdlparser.y:367: > invalid input: ; > > > 4>d:\programs\doxygen\doxygen-.distr\doxygen-788\src\\..\src\vhdlparser.y:379: > type clash (`' `qstr') on default action > > ..... > > > 4>d:\programs\doxygen\doxygen-.distr\doxygen-788\src\\..\src\vhdlparser.y:1956: > type clash (`' `qstr') on default action > > 4>Could Not Find > d:\Programs\Doxygen\Doxygen-.distr\doxygen-788\src\vhdlparser.c > > > 4>d:\programs\doxygen\doxygen-.distr\doxygen-788\src\\..\src\vhdlparser.y:324: > unrecognized: %debug > > > 4>d:\programs\doxygen\doxygen-.distr\doxygen-788\src\\..\src\vhdlparser.y:324: > Skipping to next % > > > 4>d:\programs\doxygen\doxygen-.distr\doxygen-788\src\\..\src\vhdlparser.y:327: > unrecognized: %initial_action > > > 4>d:\programs\doxygen\doxygen-.distr\doxygen-788\src\\..\src\vhdlparser.y:327: > Skipping to next % > > > 4>d:\programs\doxygen\doxygen-.distr\doxygen-788\src\\..\src\vhdlparser.y:367: > invalid input: ; > > > 4>d:\programs\doxygen\doxygen-.distr\doxygen-788\src\\..\src\vhdlparser.y:379: > type clash (`' `qstr') on default action > > ...... > > > 4>d:\programs\doxygen\doxygen-.distr\doxygen-788\src\\..\src\vhdlparser.y:1956: > type clash (`' `qstr') on default action > > 4>Project : error PRJ0002 : Error result 1 returned from > 'C:\Windows\SysWow64\cmd.exe'. > > > > No doxygen.exe is created (doxytag.exe was created). > > > > There were no problems with older versions of Doxygen (783 and earlier). > Looks like the bison version of on the UnxUtils is a bit outdated (version > 1.28; cygwin 2.4.2) > > Indeed that seems to be related to this problem. Can you try this one: > http://gnuwin32.sourceforge.net/packages/bison.htm > and let me know if that helps? > > Regards, > Dimitri > > |
From: Albert <alb...@gm...> - 2011-11-19 16:22:13
|
Hi Dimitri, Looks like it has to do something with uppercase and lowercase of the name vhdlScanYYtext versus vhdlscanYYtext Best Regards, Albert On Sat, Nov 19, 2011 at 16:51, Albert <alb...@gm...> wrote: > Hi Dimitri, > > Specified error is gone but a new ones appeared: > 3>d:\programs\doxygen\doxygen-.distr\doxygen-788\src\vhdlscanner.l(281) : > error C2065: 'vhdlScanYYtext' : undeclared identifier > 3>d:\programs\doxygen\doxygen-.distr\doxygen-788\src\vhdlscanner.cpp(1265) > : error C2065: 'vhdlScanYYleng' : undeclared identifier > 4>d:\programs\doxygen\doxygen-.distr\doxygen-788\src\vhdlscanner.l(381) : > error C2065: 'vhdlScanYYleng' : undeclared identifier > 3>d:\programs\doxygen\doxygen-.distr\doxygen-788\src\vhdlscanner.l(713) : > error C3861: 'vhdlScanYYlex': identifier not found > 3>d:\programs\doxygen\doxygen-.distr\doxygen-788\src\vhdlscanner.l(749) : > error C2065: 'vhdlScanYYin' : undeclared identifier > 3>d:\programs\doxygen\doxygen-.distr\doxygen-788\src\vhdlscanner.l(749) : > error C3861: 'vhdlScanYYrestart': identifier not found > (some multiple times) > > So I installed flex from: > http://gnuwin32.sourceforge.net/packages/flex.htm but this didn't help > either. > > Best Regards, > > Albert > > > On Sat, Nov 19, 2011 at 16:16, Dimitri Van Heesch <do...@gm...>wrote: > >> >> On Nov 19, 2011, at 15:33 , Albert wrote: >> >> > Hi Dimitri, >> > >> > Just checked out version 788 from svn. Tried to compile it on windows. >> With cygwin no problem, with Visiual C 2008 express I get the error >> messages: >> > >> > 4>Executing Lex for >> d:\Programs\Doxygen\Doxygen-.distr\doxygen-788\src\/vhdlcode.cpp ... >> > 4>Running bison on vhdlparser.y >> > >> 4>d:\programs\doxygen\doxygen-.distr\doxygen-788\src\\..\src\vhdlparser.y:324: >> unrecognized: %debug >> > >> 4>d:\programs\doxygen\doxygen-.distr\doxygen-788\src\\..\src\vhdlparser.y:324: >> Skipping to next % >> > >> 4>d:\programs\doxygen\doxygen-.distr\doxygen-788\src\\..\src\vhdlparser.y:327: >> unrecognized: %initial_action >> > >> 4>d:\programs\doxygen\doxygen-.distr\doxygen-788\src\\..\src\vhdlparser.y:327: >> Skipping to next % >> > >> 4>d:\programs\doxygen\doxygen-.distr\doxygen-788\src\\..\src\vhdlparser.y:367: >> invalid input: ; >> > >> 4>d:\programs\doxygen\doxygen-.distr\doxygen-788\src\\..\src\vhdlparser.y:379: >> type clash (`' `qstr') on default action >> > ..... >> > >> 4>d:\programs\doxygen\doxygen-.distr\doxygen-788\src\\..\src\vhdlparser.y:1956: >> type clash (`' `qstr') on default action >> > 4>Could Not Find >> d:\Programs\Doxygen\Doxygen-.distr\doxygen-788\src\vhdlparser.c >> > >> 4>d:\programs\doxygen\doxygen-.distr\doxygen-788\src\\..\src\vhdlparser.y:324: >> unrecognized: %debug >> > >> 4>d:\programs\doxygen\doxygen-.distr\doxygen-788\src\\..\src\vhdlparser.y:324: >> Skipping to next % >> > >> 4>d:\programs\doxygen\doxygen-.distr\doxygen-788\src\\..\src\vhdlparser.y:327: >> unrecognized: %initial_action >> > >> 4>d:\programs\doxygen\doxygen-.distr\doxygen-788\src\\..\src\vhdlparser.y:327: >> Skipping to next % >> > >> 4>d:\programs\doxygen\doxygen-.distr\doxygen-788\src\\..\src\vhdlparser.y:367: >> invalid input: ; >> > >> 4>d:\programs\doxygen\doxygen-.distr\doxygen-788\src\\..\src\vhdlparser.y:379: >> type clash (`' `qstr') on default action >> > ...... >> > >> 4>d:\programs\doxygen\doxygen-.distr\doxygen-788\src\\..\src\vhdlparser.y:1956: >> type clash (`' `qstr') on default action >> > 4>Project : error PRJ0002 : Error result 1 returned from >> 'C:\Windows\SysWow64\cmd.exe'. >> > >> > No doxygen.exe is created (doxytag.exe was created). >> > >> > There were no problems with older versions of Doxygen (783 and >> earlier). Looks like the bison version of on the UnxUtils is a bit outdated >> (version 1.28; cygwin 2.4.2) >> >> Indeed that seems to be related to this problem. Can you try this one: >> http://gnuwin32.sourceforge.net/packages/bison.htm >> and let me know if that helps? >> >> Regards, >> Dimitri >> >> > |
From: Dimitri V. H. <do...@gm...> - 2011-11-19 16:30:49
|
On Nov 19, 2011, at 17:22 , Albert wrote: > Hi Dimitri, > > Looks like it has to do something with uppercase and lowercase of the name vhdlScanYYtext versus vhdlscanYYtext Indeed. The scanner prefix seems to have changed from vhdlscanYYtest to vhdlScanYYtext, but this change was not done for Doxygen.vcproj. I've updated it now. You may need to manually delete src/vhdlscanner.cpp Regards, Dimitri |
From: Albert <alb...@gm...> - 2011-11-19 16:50:36
|
Hi Dimitri, Thanks, compiles and links now (I'm using the gnuWin32 flex and bison now, especially tye bison is necessay I think, so I think the manual also need an small update). Best Regards, Albert On Sat, Nov 19, 2011 at 17:30, Dimitri Van Heesch <do...@gm...> wrote: > > On Nov 19, 2011, at 17:22 , Albert wrote: > > > Hi Dimitri, > > > > Looks like it has to do something with uppercase and lowercase of the > name vhdlScanYYtext versus vhdlscanYYtext > > Indeed. The scanner prefix seems to have changed from vhdlscanYYtest to > vhdlScanYYtext, but this change was not done for > Doxygen.vcproj. I've updated it now. You may need to manually delete > src/vhdlscanner.cpp > > Regards, > Dimitri > > |