From: Mark Wielaard <mark@klomp.org>
To: Dodji Seketeli <dodji@seketeli.org>
Cc: v <vsochat@gmail.com>,
Ben Woodard via Libabigail <libabigail@sourceware.org>
Subject: Re: Testing Setup - More Tests and Automation?
Date: Tue, 14 Jun 2022 12:05:24 +0200 [thread overview]
Message-ID: <5febb6769f14c3f73376e911ac85c3d230efe2fb.camel@klomp.org> (raw)
In-Reply-To: <87ilpaks6j.fsf@seketeli.org>
Hi Dodji,
On Thu, 2022-06-09 at 13:11 +0200, Dodji Seketeli wrote:
> Mark Wielaard <mark@klomp.org> a écrit:
> > I don't know how the libabigail website is generated, but it would be
> > nice to get that also in git so people can update it if they feel they
> > have a better design.
>
> It's generated by "make doc" and it's in $builddir/doc/website. It's in
> git, thus.
Is there a special way to configure to get this populated?
When I run make doc it does generate several docs, but the website dir
is (nearly) empty:
$ ls doc/*
doc/Makefile doc/Makefile.am doc/Makefile.in doc/suppr-doc.txt
doc/api:
doxygen-warnings.txt html html.doxy libabigail.doxy
doc/html:
bc_s.png dynsections.js menu.js splitbar.png tabs.css
bdwn.png folderclosed.png nav_f.png sync_off.png tab_s.png
closed.png folderopen.png nav_g.png sync_on.png
doc.png index.html nav_h.png tab_a.png
doxygen.css jquery.js open.png tab_b.png
doxygen.png menudata.js search tab_h.png
doc/latex:
doxygen.sty Makefile refman.tex
doc/manuals:
abicompat.rst conf.py kmidiff.rst Makefile.am
abidiff.rst doctrees libabigail-concepts.rst Makefile.in
abidw.rst fedabipkgdiff.rst libabigail-overview.rst man
abilint.rst html libabigail-tools.rst texinfo
abipkgdiff.rst index.rst Makefile
doc/vizualization:
graph layout
doc/website:
libabigail-website.doxy mainpage.txt
Is there a followup step needed?
We could automate updating the website through builder.sourceware.org
if there is a script to update it.
Cheers,
Mark
next prev parent reply other threads:[~2022-06-14 10:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAM=pu++-JdBdizXQ9dj8eUypXg7fpPOTDzN6BL1NY-TFvk++kQ@mail.gmail.com>
2022-04-28 0:55 ` Fwd: " Ben Woodard
2022-04-28 1:57 ` v
2022-04-30 19:55 ` Mark Wielaard
2022-04-30 20:36 ` v
2022-04-30 21:48 ` Mark Wielaard
2022-04-30 22:38 ` v
2022-05-01 22:42 ` Mark Wielaard
2022-05-01 22:46 ` v
2022-06-09 11:31 ` Thinking different (was Re: Testing Setup - More Tests and Automation?) Dodji Seketeli
2022-06-09 19:48 ` v
2022-06-15 14:21 ` Dodji Seketeli
2022-06-09 11:18 ` Testing Setup - More Tests and Automation? Dodji Seketeli
2022-06-09 11:11 ` Dodji Seketeli
2022-06-14 10:05 ` Mark Wielaard [this message]
2022-04-28 8:06 ` Fwd: " Mark Wielaard
2022-04-29 21:13 ` Mark Wielaard
2022-04-29 22:02 ` Mark Wielaard
2022-05-03 19:08 ` Ben Woodard
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=5febb6769f14c3f73376e911ac85c3d230efe2fb.camel@klomp.org \
--to=mark@klomp.org \
--cc=dodji@seketeli.org \
--cc=libabigail@sourceware.org \
--cc=vsochat@gmail.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).