Having some trouble with bootstrapping Boost to use LLVM
I changed the project-config.jam file in my Boost source tree to have Boost.Build use LLVM, but then when I used "bootstrap" command after, I saw that it was still using MSVC. When I looked at the project-config.jam file again at that point, I saw that its content had been reverted back to the default one for building with MSVC. What's going on? What do I need to do? Is there an argument I need to provide to the bootstrap command here so that it'll keep the configuration file content that I want it to? And is there no help command that would let me see what arguments, if any, I can pass to the tool? Another thing I want to ask is whether or not I need to have Boost.Built emit library files with a .bc extension to be able to link them with code I want to build using the Emscripten compiler. I ask because Emscripten needs compiled libraries to have been compiled to LLVM bitcode, and when Emscripten itself does this it adds the .bc extension instead of the .lib one.
On 20/12/2018 12:23, Osman Zakir wrote:
I changed the project-config.jam file in my Boost source tree to have Boost.Build use LLVM, but then when I used "bootstrap" command after, I saw that it was still using MSVC. When I looked at the project-config.jam file again at that point, I saw that its content had been reverted back to the default one for building with MSVC. What's going on? What do I need to do? Is there an argument I need to provide to the bootstrap command here so that it'll keep the configuration file content that I want it to? And is there no help command that would let me see what arguments, if any, I can pass to the tool?
The bootstrap script builds Boost.Build (b2) and a default project-config.jam file. It doesn't really matter which compiler this uses (other than it selecting the same one as the default for project-config.jam), as long as it's one that works on your system. If you're customising project-config.jam afterwards, just don't run bootstrap again, and start with running b2.
Oh, okay, thanks for the info. What about the extension for the bitcode file? Should I somehow force it to generate LLVM bitcode with .bc extension?
participants (2)
-
Gavin Lambert -
Osman Zakir