The suggested build commands left out the usual cd after mkdir, so that if you followed them literally, you'd create an arm-runtimes or arm-multilib directory and then ignore it completely and put all your build debris at the level above it.
Also, trying to follow the instructions, I was confused by the semantics of LLVM_BINARY_DIR: given the name, I instinctively pointed it at the actual bin directory, but it turned out I should have aimed one level up. Added some clarifying text, with particular reference to using a full build of this toolchain for a standalone build of one library.
While I'm here, removed some apparently accidental physical tabs, so that all the continuation lines in the long cmake commands line up.
Yes, I guessed that was the sense you meant "binary" in. As you say – it's a valid use, just not the only use, so the clarification seems worth having.
The suggested build commands left out the usual
cd
aftermkdir
, so that if you followed them literally, you'd create anarm-runtimes
orarm-multilib
directory and then ignore it completely and put all your build debris at the level above it.Also, trying to follow the instructions, I was confused by the semantics of
LLVM_BINARY_DIR
: given the name, I instinctively pointed it at the actualbin
directory, but it turned out I should have aimed one level up. Added some clarifying text, with particular reference to using a full build of this toolchain for a standalone build of one library.While I'm here, removed some apparently accidental physical tabs, so that all the continuation lines in the long cmake commands line up.