Thread: [Doxygen-users] plugin / filter not behaving as expected
Brought to you by:
dimitri
From: Clayton <cla...@gm...> - 2015-10-10 07:41:49
Attachments:
syntax.cpp
syntax.css
|
Hi all, I am prototyping a plugin a la http://www.stack.nl/~dimitri/doxygen/helpers.html for html / js / css (GitHub repos tagged as "html") to use Doxygen to analyze certain aspects of this kind of code. As a for-instance, attached is an actual syntax.css file pulled from a repo, and the corresponding syntax.cpp output after I pass it through my filter. g++ reports no syntax issues with syntax.cpp, and Doxygen, with a default Doxyfile, processes syntax.cpp and produces a list of classes as expected. BUT.... If I configure Doxyfile with my css filter: INPUT_FILTER = /path/to/plugins/webplugin/web2doxy.pl FILE_PATTERNS = *.css absolutely nothing happens. No output, no errors, nothing. (Note that I have already seen this working sometimes with some other filters built by other people.) Any ideas about what might be missing in my simple configuration above? Assuming Doxygen is presenting syntax.css to stdin of my filter unmodified, the filter should be giving Doxygen back exactly the content of syntax.cpp on it's stdout. But why the different behavior? Thanks for any insights, Clayton |
From: Albert <alb...@gm...> - 2015-10-10 08:31:13
|
Clayton, I assume you caught the output of the perl script into a cpp fie and tried to process that with doxygen and this is working. One thing that comes quickly into my mind is: is EXTENSION_MAPPING set so that css file are handled as cpp files? (see the output of the doxygen command if the css files are listed in the files processed) Albert On Sat, Oct 10, 2015 at 9:40 AM, Clayton <cla...@gm...> wrote: > Hi all, > > I am prototyping a plugin a la > > http://www.stack.nl/~dimitri/doxygen/helpers.html > > for html / js / css (GitHub repos tagged as "html") to use Doxygen to > analyze certain aspects of this kind of code. As a for-instance, > attached is an actual syntax.css file pulled from a repo, and the > corresponding syntax.cpp output after I pass it through my filter. g++ > reports no syntax issues with syntax.cpp, and Doxygen, with a default > Doxyfile, processes syntax.cpp and produces a list of classes as > expected. > > BUT.... If I configure Doxyfile with my css filter: > > INPUT_FILTER = /path/to/plugins/webplugin/web2doxy.pl > FILE_PATTERNS = *.css > > absolutely nothing happens. No output, no errors, nothing. (Note that I > have already seen this working sometimes with some other filters built > by other people.) > > Any ideas about what might be missing in my simple configuration above? > Assuming Doxygen is presenting syntax.css to stdin of my filter > unmodified, the filter should be giving Doxygen back exactly the > content of syntax.cpp on it's stdout. > > But why the different behavior? > > Thanks for any insights, > Clayton > > ------------------------------------------------------------------------------ > > _______________________________________________ > Doxygen-users mailing list > Dox...@li... > https://lists.sourceforge.net/lists/listinfo/doxygen-users > > |
From: Clayton <cla...@gm...> - 2015-10-12 09:02:27
|
Hi Albert, On Sat, 10 Oct 2015 10:31:07 +0200 Albert <alb...@gm...> wrote: > I assume you caught the output of the perl script into a cpp fie and > tried to process that with doxygen and this is working. Yes indeed, that worked and works. > One thing that comes quickly into my mind is: is EXTENSION_MAPPING > set so that css file are handled as cpp files? Bingo! That is the missing piece. And I think that was also the problem in my e-mail of some time ago about issues with Visual Basic as well. This explains a lot. Thanks a lot for the suggestion!!! > (see the output of the doxygen command if the css files are listed in > the files processed) They actually were being listed as being parsed, ie. Parsing files Reading /tmp/temp/syntax.css... Even with EXTENSION_MAPPING undefined. And then nothing happened, no errors either, which was confusing. Thanks again, Clayton |
From: Albert <alb...@gm...> - 2015-10-14 14:01:58
|
I've just pushed an update to github (pull request 404) with an extra note in the Doxyfile / documentation On Mon, Oct 12, 2015 at 11:01 AM, Clayton <cla...@gm...> wrote: > Hi Albert, > > On Sat, 10 Oct 2015 10:31:07 +0200 > Albert <alb...@gm...> wrote: > > > I assume you caught the output of the perl script into a cpp fie and > > tried to process that with doxygen and this is working. > > Yes indeed, that worked and works. > > > One thing that comes quickly into my mind is: is EXTENSION_MAPPING > > set so that css file are handled as cpp files? > > Bingo! That is the missing piece. And I think that was also the problem > in my e-mail of some time ago about issues with Visual Basic as well. > This explains a lot. Thanks a lot for the suggestion!!! > > > (see the output of the doxygen command if the css files are listed in > > the files processed) > > They actually were being listed as being parsed, ie. > > Parsing files > Reading /tmp/temp/syntax.css... > > Even with EXTENSION_MAPPING undefined. And then nothing happened, no > errors either, which was confusing. > > Thanks again, > Clayton > > > ------------------------------------------------------------------------------ > _______________________________________________ > Doxygen-users mailing list > Dox...@li... > https://lists.sourceforge.net/lists/listinfo/doxygen-users > |