ninja: error: loading 'build.ninja': No such file or directory
Not enough information. What system, what did you execute exactly?
Followed these steps mentioned in the wiki
sudo apt install ffmpeg libsdl2-2.0.0
# client build dependencies
sudo apt install make gcc pkg-config meson \
libavcodec-dev libavformat-dev libavutil-dev \
libsdl2-dev
# server build dependencies
sudo apt install openjdk-8-jdk
Clone the project:
git clone https://github.com/Genymobile/scrcpy
cd scrcpy
Then, build:
meson x --buildtype release --strip -Db_lto=true
cd x
ninja # --> **gives this error**
_I am using Ubuntu 16.04_
What was the output of:
meson x --buildtype release --strip -Db_lto=true
What is the content of the x directory after this command?
ls x
ls x ---> meson-logs meson-private
meson x --buildtype release --strip -Db_lto=true ---->Meson version is 0.29.0 but project requires >= 0.37.
its not worked that way so i used
pip3 install meson
its not worked that way so i used
pip3 install meson
Then, it worked?
No... now i am facing this issue....
On Wed, Apr 18, 2018 at 6:27 PM, Romain Vimont notifications@github.com
wrote:
its not worked that way so i used pip3 install meson
Then, it worked?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Genymobile/scrcpy/issues/126#issuecomment-382377035,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AXRhvTOr5au2Fddk2owOmm_le9lDAJG3ks5tpzgngaJpZM4TZZpZ
.
Once you installed a newer meson via pip3, what was the result of:
meson x --buildtype release --strip -Db_lto=true
?
I have already mentioned that before.. it gives this ---> Meson version is 0.29.0 but project requires >= 0.37. ERROR
The version from pip3 should not be 0.29.
sudo apt-get remove meson
sudo pip3 install meson
sudo apt-get remove meson
sudo pip3 install meson
after this
if we do -------->meson x --buildtype release --strip -Db_lto=true
gives this error

If we do -----> cd x----------> ninja gives this error

If meson fails, this is a problem, do not even try to execute the next commands.
So you installed meson via pip3, but meson does not exist… Did pip3 install meson worked as expected?
Does meson.py exists instead?
meson.py x --buildtype release --strip -Db_lto=true
Did pip3 install meson worked as expected? I dont Know I have shown already what i got as result...
meson.py: command not found
Does meson.py exists instead? NO
Did pip3 install meson worked as expected? I dont Know I have shown already what i got as result
I think you did not post the output of:
sudo pip3 install meson
The directory '/home/varun/.cache/pip/http' or its parent directory is not
owned by the current user and the cache has been disabled. Please check the
permissions and owner of that directory. If executing pip with sudo, you
may want sudo's -H flag.
The directory '/home/varun/.cache/pip' or its parent directory is not owned
by the current user and caching wheels has been disabled. check the
permissions and owner of that directory. If executing pip with sudo, you
may want sudo's -H flag.
Requirement already satisfied (use --upgrade to upgrade): meson in
/usr/local/lib/python3.5/dist-packages
You are using pip version 8.1.1, however version 10.0.0 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
This is what getting now..
On Thu, Apr 19, 2018 at 4:21 PM, Romain Vimont notifications@github.com
wrote:
Did pip3 install meson worked as expected? I dont Know I have shown
already what i got as resultI think you did not post the output of:
sudo pip3 install meson
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Genymobile/scrcpy/issues/126#issuecomment-382692439,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AXRhvTnB2K1wEZNzbdNyNY-YAMCjf2Kfks5tqGwUgaJpZM4TZZpZ
.
try
$ sudo ninja
instead of
$ ninja
Any luck with this procedure? I'm planning to do an Ubuntu build tonight and hoping to use this thread as a guide. Last time I tried I ran into similar issues. I think the official build instructions would be clearer if separated into just showing the full build procedure for each OS/Distro.
Do you still have the problem?