From: "Martin Liška" <mliska@suse.cz>
To: David Malcolm <dmalcolm@redhat.com>, gcc-patches@gcc.gnu.org
Cc: Jeff Law <law@redhat.com>
Subject: Re: [PATCH] Port Doxygen support script from Perl to Python; add unittests
Date: Wed, 31 May 2017 14:13:00 -0000 [thread overview]
Message-ID: <05315c85-b294-45d8-a0bf-e67108244ebc@suse.cz> (raw)
In-Reply-To: <329c72e0-cb17-178b-3858-d080b5b27457@suse.cz>
[-- Attachment #1: Type: text/plain, Size: 23 bytes --]
..adding missing patch
[-- Attachment #2: 0001-Doxygen-add-default-location-for-filters-and-output-.patch --]
[-- Type: text/x-patch, Size: 4098 bytes --]
From 3021b695a8111e1552176529ab3342cdd2ae3a43 Mon Sep 17 00:00:00 2001
From: marxin <mliska@suse.cz>
Date: Wed, 3 May 2017 11:42:41 +0200
Subject: [PATCH] Doxygen: add default location for filters and output folder.
contrib/ChangeLog:
2017-05-03 Martin Liska <mliska@suse.cz>
* gcc.doxy: Add default location for filters and output folder.
* filter_gcc_for_doxygen_new: Rename to filter_gcc_for_doxygen.
* filter_params.pl: Remove.
---
contrib/filter_gcc_for_doxygen | 6 +++---
contrib/filter_gcc_for_doxygen_new | 12 ------------
contrib/filter_params.pl | 14 --------------
contrib/gcc.doxy | 8 ++------
4 files changed, 5 insertions(+), 35 deletions(-)
delete mode 100755 contrib/filter_gcc_for_doxygen_new
delete mode 100755 contrib/filter_params.pl
diff --git a/contrib/filter_gcc_for_doxygen b/contrib/filter_gcc_for_doxygen
index 3787eebbf0e..d1109a50c88 100755
--- a/contrib/filter_gcc_for_doxygen
+++ b/contrib/filter_gcc_for_doxygen
@@ -1,12 +1,12 @@
#!/bin/sh
# This filters GCC source before Doxygen can get confused by it;
-# this script is listed in the doxyfile. The output is not very
+# this script is listed in the doxyfile. The output is not very
# pretty, but at least we get output that Doxygen can understand.
#
-# $1 is a source file of some kind. The source we wish doxygen to
+# $1 is a source file of some kind. The source we wish doxygen to
# process is put on stdout.
dir=`dirname $0`
-perl $dir/filter_params.pl < $1 | perl $dir/filter_knr2ansi.pl
+python $dir/filter_params.py $1
exit 0
diff --git a/contrib/filter_gcc_for_doxygen_new b/contrib/filter_gcc_for_doxygen_new
deleted file mode 100755
index d1109a50c88..00000000000
--- a/contrib/filter_gcc_for_doxygen_new
+++ /dev/null
@@ -1,12 +0,0 @@
-#!/bin/sh
-
-# This filters GCC source before Doxygen can get confused by it;
-# this script is listed in the doxyfile. The output is not very
-# pretty, but at least we get output that Doxygen can understand.
-#
-# $1 is a source file of some kind. The source we wish doxygen to
-# process is put on stdout.
-
-dir=`dirname $0`
-python $dir/filter_params.py $1
-exit 0
diff --git a/contrib/filter_params.pl b/contrib/filter_params.pl
deleted file mode 100755
index 22dae6cc561..00000000000
--- a/contrib/filter_params.pl
+++ /dev/null
@@ -1,14 +0,0 @@
-#!/usr/bin/perl
-
-# Filters out some of the #defines used throughout the GCC sources:
-# - GTY(()) marks declarations for gengtype.c
-# - PARAMS(()) is used for K&R compatibility. See ansidecl.h.
-
-while (<>) {
- s/^\/\* /\/\*\* \@verbatim /;
- s/\*\// \@endverbatim \*\//;
- s/GTY[ \t]*\(\(.*\)\)//g;
- s/[ \t]ATTRIBUTE_UNUSED//g;
- s/PARAMS[ \t]*\(\((.*?)\)\)/\($1\)/sg;
- print;
-}
diff --git a/contrib/gcc.doxy b/contrib/gcc.doxy
index 7a284e754aa..a8eeb03c9a0 100644
--- a/contrib/gcc.doxy
+++ b/contrib/gcc.doxy
@@ -11,16 +11,12 @@
# Values that contain spaces should be placed between quotes (" ")
-#-----------------------------------------------------------------------------
-# NOTE: YOU MUST EDIT THE FOLLOWING HARDWIRED PATHS BEFORE USING THIS FILE.
-#-----------------------------------------------------------------------------
-
# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute)
# base path where the generated documentation will be put.
# If a relative path is entered, it will be relative to the location
# where doxygen was started. If left blank the current directory will be used.
-OUTPUT_DIRECTORY = @OUTPUT_DIRECTORY@
+OUTPUT_DIRECTORY = gcc-doxygen
# The INPUT_FILTER tag can be used to specify a program that doxygen should
# invoke to filter for each input file. Doxygen will invoke the filter program
@@ -30,7 +26,7 @@ OUTPUT_DIRECTORY = @OUTPUT_DIRECTORY@
# to standard output. If FILTER_PATTERNS is specified, this tag will be
# ignored.
-INPUT_FILTER = @INPUT_FILTER@
+INPUT_FILTER = contrib/filter_gcc_for_doxygen
#-----------------------------------------------------------------------------
--
2.12.2
next prev parent reply other threads:[~2017-05-31 14:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-31 22:11 [PATCH] Support multiline GTY markers in Doxygen filter; " David Malcolm
2013-11-01 15:16 ` Diego Novillo
2017-03-17 1:21 ` [PATCH 1/2] Port Doxygen support script from Perl to Python; " David Malcolm
2017-03-17 1:21 ` [PATCH 2/2] filter_params.py: GTY fix and other cleanups David Malcolm
2017-04-28 12:25 ` [PATCH 1/2] Port Doxygen support script from Perl to Python; add unittests Martin Liška
2017-05-03 9:49 ` [PATCH] Doxygen: add default location for filters and output folder Martin Liška
2017-05-31 12:43 ` [PATCH 1/2] Port Doxygen support script from Perl to Python; add unittests Martin Liška
2017-04-28 12:30 ` [PATCH 1/2] Change comment style to one we normally use Martin Liška
2017-04-28 12:41 ` [PATCH 2/2] Doxygen: transform ENUM_BITFIELD and comments starting with '/**' Martin Liška
2017-04-29 2:57 ` [PING] Re: [PATCH 1/2] Port Doxygen support script from Perl to Python; add unittests David Malcolm
2017-05-19 9:14 ` Martin Liška
2017-05-26 19:35 ` [PING^2] " David Malcolm
2017-05-31 14:07 ` [PATCH] " Martin Liška
2017-05-31 14:10 ` Martin Liška
2017-05-31 14:13 ` Martin Liška [this message]
2017-06-22 12:45 ` Martin Liška
2017-06-28 4:41 ` Jeff Law
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=05315c85-b294-45d8-a0bf-e67108244ebc@suse.cz \
--to=mliska@suse.cz \
--cc=dmalcolm@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=law@redhat.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).