12-13-2018, 09:48 AM
It sounds like your first cmake didn't actually succeed.
The first cmake is like "./configure" for traditional compilation.
It is checking for libraries, dependencies, and certain scripts and bin tools.
If it doesn't succeed, it won't create the Makefile for the second cmake step.
You will need to install whatever it is complaining about, then run the first cmake step again, and keep installing the things it's complaining about until it actually succeeds.
I simply did 'apt install' of 90% of the things it asked for and it was fine.
(Unfortunately, I didn't make a list of those things, would have made this a lot easier.)
The problem with multi-threaded building (-j parameter with a number, like -j10), is that the errors get nested so deep you can't read them because of the multiple jobs running.
When any cmake step fails, switch to not using the -j parameter just so you can more easily see what is wrong.
The first cmake is like "./configure" for traditional compilation.
It is checking for libraries, dependencies, and certain scripts and bin tools.
If it doesn't succeed, it won't create the Makefile for the second cmake step.
You will need to install whatever it is complaining about, then run the first cmake step again, and keep installing the things it's complaining about until it actually succeeds.
I simply did 'apt install' of 90% of the things it asked for and it was fine.
(Unfortunately, I didn't make a list of those things, would have made this a lot easier.)
The problem with multi-threaded building (-j parameter with a number, like -j10), is that the errors get nested so deep you can't read them because of the multiple jobs running.
When any cmake step fails, switch to not using the -j parameter just so you can more easily see what is wrong.