summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorVedant Paranjape <vedantparanjape160201@gmail.com>2021-03-31 12:46:00 +0530
committerPaul Elder <paul.elder@ideasonboard.com>2021-04-05 13:42:49 +0900
commit76a5861f3ef0950d9b57e54668c9059ed7bddd89 (patch)
treeb84f3f6f8feb5ad6a7bbf251e750b580969581b6
parentc85b6c849f61349129c2ac549017316f60ae5e07 (diff)
Add alternative meson install command
While installing meson using pip3 install --user meson, due to python path issues, build.ninja can't be located by ninja. meson generates ninja files fine, but then when you run ninja, it is unable to find meson's build.ninja python module due to path issues. It gives the following error on ninja -C build install: ninja: Entering directory `build' ninja: error: loading 'build.ninja': No such file or directory After uninstalling meson using pip3 and installing it again using pip without --user argument solved the issue. Add a troubleshooting section to the readme to describe this issue and suggest possible solutions. Signed-off-by: Vedant Paranjape <vedantparanjape160201@gmail.com> Reviewed-by: Paul Elder <paul.elder@ideasonboard.com> Signed-off-by: Paul Elder <paul.elder@ideasonboard.com>
-rw-r--r--README.rst21
1 files changed, 21 insertions, 0 deletions
diff --git a/README.rst b/README.rst
index 1427c714..391c7a5f 100644
--- a/README.rst
+++ b/README.rst
@@ -104,3 +104,24 @@ onto the default video display element on your system.
gst-launch-1.0 libcamerasrc camera-name="Camera 1" ! videoconvert ! autovideosink
.. section-end-getting-started
+
+Troubleshooting
+~~~~~~~~~~~~~~~
+
+Several users have reported issues with meson installation, crux of the issue
+is a potential version mismatch between the version that root uses, and the
+version that the normal user uses. On calling `ninja -C build`, it can't find
+the build.ninja module. This is a snippet of the error message.
+
+::
+
+ ninja: Entering directory `build'
+ ninja: error: loading 'build.ninja': No such file or directory
+
+This can be solved in two ways:
+
+1) Don't install meson again if it is already installed system-wide.
+
+2) If a version of meson which is different from the system-wide version is
+already installed, uninstall that meson using pip3, and install again without
+the --user argument.