DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Varghese, Vipin" <Vipin.Varghese@amd.com>
To: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
Cc: Thomas Monjalon <thomas@monjalon.net>,
	"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 12:29:11 +0000	[thread overview]
Message-ID: <MN2PR12MB308520F6E8614AD15810F1D0821D9@MN2PR12MB3085.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20220328123438.0f8bb44e@sovereign>

[AMD Official Use Only]

Hi Dmitry,

Thanks for inputs, please find my question below

<snip>

2022-03-28 03:02 (UTC+0000), Varghese, Vipin:
> [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)
> ```

This line never searches for "echo" command, e8c90926bdde ("doc: fix build on Windows with Meson 0.58") introduced "echo" variable precisely to avoid this.
Can you give the full log?

> > 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.

If something is explicitly requested but not supported, there should be a failure.
By the way, -Denable_docs=true works when cross-compiling for Windows, so disabling docs for this target is not right.
I think we should sort out what's causing an issue with "echo" for you (it shouldn't happen), then fix the scripts to fully enable docs.

Are you recommending 

Windows libraries and binaries should be cross build from linux (where all dependencies and shell script works)?

Or 

let us enhance the check for windows native build, if yes for option `-Denable_docs=true, we can stop the build for docs`.

If the latter is suggestion I will share v2 patch to check the same.

  reply	other threads:[~2022-03-28 12:29 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
2022-03-28  9:34     ` Dmitry Kozlyuk
2022-03-28 12:29       ` Varghese, Vipin [this message]
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=MN2PR12MB308520F6E8614AD15810F1D0821D9@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).