public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: saifi.khan@nishan.io
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: top-level build target that triggers 'make doc-html-doxygen'
Date: Sun, 13 Nov 2022 09:29:51 +0000	[thread overview]
Message-ID: <CAH6eHdQvnfhu9+6ua0o80FQvUtBRPxu0XdTHeK3GosLifsSubg@mail.gmail.com> (raw)
In-Reply-To: <0c19c7b6ff9e933532c5ed5630d2527a@nishan.io>

[-- Attachment #1: Type: text/plain, Size: 2698 bytes --]

On Sun, 13 Nov 2022, 09:11 Saifi Khan, <saifi.khan@nishan.io> wrote:

> 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 your reply Jonathan.
>
> Since, i am doing a 'out-of-source-tree' build, the layout looks like
> this
>
> /opt/gcc
> ├── build
> └── src
>
> Given the layout, the build/b02.sh (configure script) is as follows
>
> DIR_SRC=/opt/gcc/src
> DIR_DST=/opt/gcc
> DIR_ISL=/opt/isl
>    CFLAGS="-O2 -pipe"
> CXXFLAGS="${CFLAGS}"
>
> ${DIR_SRC}/configure                        \
>            --prefix=${DIR_DST}               \
>            --exec-prefix=${DIR_DST}          \
>            --datarootdir=${DIR_DST}/doc/share   \
>            --datadir=${DIR_DST}/doc          \
>            --docdir=${DIR_DST}/doc           \
>            --htmldir=${DIR_DST}/doc          \
>            --mandir=${DIR_DST}/doc/man       \
>            --infodir=${DIR_DST}/doc/info     \
>            --with-isl=${DIR_ISL}             \
>            --enable-languages=c,jit,c++      \
>            --enable-bootstrap                \
>   <snipped>
>
> Post build/b04.sh ie. 'make -j4', there is one directory created for
> libstdc++
>
> build/x86_64-pc-linux-gnu/libstdc++-v3
>
> Now, if i execute the command that you suggested, the doxygen html build
> goes through (which is what i was did prior to posting on gcc-help).
>
> Unfortunately, on executing build/b08.sh script file ie. 'make install'
> errors out !
>
> That leaves only one option and that first perform 'make install' and
> then 'make -C */libstdc++-v3 doc-html-doxygen'.
>

You can replace the * with the correct path, which is the
x86_64-pc-linux-gnu one for your case.


> Does that seem like a sensible thing to do ?
>
> In addition, i observed that the html documentation for the various lib*
> also doesn't get copied as part of 'make install', wich means that a
> custom script will be required to recursively copy the 'html'
> directories from all 'lib*' including 'libstdc++-v3'.
>

There is a doc-install-html target in the $target/libstdc++-v3 dir, but
that will also try to build the main manual as well as the doxygen pages.



> Is that how the online gcc docs are getting updated ?
>

A script that copies them to the web server directory after building them.
They are not "installed" by the makefile.



> warm regards
> Saifi.
>

  reply	other threads:[~2022-11-13  9:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2022-11-14 16:24       ` Saifi Khan
2022-11-14 16:56         ` Jonathan Wakely
2022-11-14 17:10           ` Saifi Khan
2022-11-22 14:04 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=CAH6eHdQvnfhu9+6ua0o80FQvUtBRPxu0XdTHeK3GosLifsSubg@mail.gmail.com \
    --to=jwakely.gcc@gmail.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=saifi.khan@nishan.io \
    /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).