Documentation | waf: Fix singlehtml output (!104)

[ita2048 ita2048 (@ita2048)]

ita2048 ita2048 commented on a discussion: https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/104#note_120086


Thank you for confirming the behavior above.

The inliner application will always attempt to read from its input channel, and then outputs nothing if no bytes are read. This can be reproduced by running `inliner user.html < /dev/null`

The build process uses inter-process communication, and provides such channels. The following is a possible workaround:

```python
r = task.exec_command(cmd, stdout = so, stderr = se, stdin=None)
```

If the above is unclear to you, consider the following alternative with a more modern alternative to `os.popen()` which also preserves the error log file:

```python
        import subprocess
        proc = subprocess.Popen(cmd, shell=True, stdout=so, stderr=se)
        proc.communicate()
        r = proc.returncode
```

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/104#note_120086
You're receiving this email because of your account on gitlab.rtems.org.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/bugs/attachments/20250219/695b2f9e/attachment.htm>