public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Saifi Khan <saifi.khan@nishan.io>
To: Gcc Help <gcc-help@gcc.gnu.org>
Subject: Re: top-level build target that triggers 'make doc-html-doxygen'
Date: Tue, 22 Nov 2022 14:04:10 +0000	[thread overview]
Message-ID: <8ce56557e645b13982ec5f0e01b65ea8@nishan.io> (raw)

On 2022-11-13 08:29, Jonathan Wakely via Gcc-help wrote:
> On Sun, 13 Nov 2022 at 07:29, Saifi Khan <saifi.khan@nishan.io> wrote:
>> 
>> Does anyone know what is the top-level Makefile build target that
>> triggers 'make doc-html-doxygen' in libstdc++ ?
>> 
> make -C */libstdc++-v3 doc-html-doxygen will work
> 

Thanks for the help Jonathan, much appreciated !

i also tweaked the libstdc++-v3/doc/doxygen/user.cfg.in to generate more 
detailed documentation with UML diagrams cross-referenced with the 
source code. Here is the result,

https://softwarehub.sourceforge.io/

i hope this will help onboard more newbies, beginners and enthusiastic 
learners to modern C++20/23 and also project externally the wonderful 
work of so many compiler hackers and free software contributors.

warm regards
Saifi.

             reply	other threads:[~2022-11-22 14:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-22 14:04 Saifi Khan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-11-13  7:28 Saifi Khan
2022-11-13  8:29 ` Jonathan Wakely
2022-11-13  9:10   ` Saifi Khan
2022-11-13  9:29     ` Jonathan Wakely
2022-11-14 16:24       ` Saifi Khan
2022-11-14 16:56         ` Jonathan Wakely
2022-11-14 17:10           ` Saifi Khan

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=8ce56557e645b13982ec5f0e01b65ea8@nishan.io \
    --to=saifi.khan@nishan.io \
    --cc=gcc-help@gcc.gnu.org \
    /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).