From: "Varghese, Vipin" <Vipin.Varghese@amd.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: "dmitry.kozliuk@gmail.com" <dmitry.kozliuk@gmail.com>,
"david.marchand@redhat.com" <david.marchand@redhat.com>,
"Tummala, Sivaprasad" <Sivaprasad.Tummala@amd.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [PATCH] meson: update doc logic for Windows
Date: Mon, 28 Mar 2022 03:02:53 +0000 [thread overview]
Message-ID: <MN2PR12MB3085A3D0DFEDBE2DBFD9AC78821D9@MN2PR12MB3085.namprd12.prod.outlook.com> (raw)
In-Reply-To: <2037084.bB369e8A3T@thomas>
[AMD Official Use Only]
Hi Thomas,
<snipp>
Thank you for looking at this problem.
26/03/2022 03:59, Vipin Varghese:
> Support for shell scripts doxy-html-custom, generate_doxygen and
> generate_examples are absent. The current patch address the same by
> disabling document build notifying the user.
It should not prevent generating guides with sphinx.
We did get error from `doc/meson` stating ` echo command not available on windows` for both cmd and powershell for the line
```
run_target('doc', command: [echo, message, doc_target_names],
depends: doc_targets)
```
> Steps to reproduce the error:
> - Install dependencies doxygen & sphinix build on Windwos server 2019.
> - Build DPDK with option enable_docs=true for API or User Guide.
>
> This produces error
> ```
> FAILED: doc/api/examples.dox
> sh -e dpdk/doc/api/generate_examples.sh dpdk/examples
> doc/api/examples.dox ```
I suppose we could replace shell scripts with Python equivalent.
I am trying to minimize the changes as first step: fix the build error by disabling on windows`.
Next step we can convert to python to make it cross platform independent.
next prev parent reply other threads:[~2022-03-28 3:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-26 2:59 Vipin Varghese
2022-03-26 9:41 ` Thomas Monjalon
2022-03-28 3:02 ` Varghese, Vipin [this message]
2022-03-28 9:34 ` Dmitry Kozlyuk
2022-03-28 12:29 ` Varghese, Vipin
2022-03-28 14:37 ` Varghese, Vipin
2022-03-28 22:51 ` Dmitry Kozlyuk
2022-03-29 5:35 ` Varghese, Vipin
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=MN2PR12MB3085A3D0DFEDBE2DBFD9AC78821D9@MN2PR12MB3085.namprd12.prod.outlook.com \
--to=vipin.varghese@amd.com \
--cc=Sivaprasad.Tummala@amd.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=dmitry.kozliuk@gmail.com \
--cc=thomas@monjalon.net \
/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 NNTP newsgroup(s).