[llvm-dev] [RFC] LLVM Directory Structure Changes (was Re: [PATCH] D20992: [CMake] Add LLVM runtimes directory)

Craig, Ben via llvm-dev llvm-dev at lists.llvm.org
Tue Jun 14 11:07:37 PDT 2016

On 6/14/2016 11:40 AM, Chris Bieneman via llvm-dev wrote:
> The problem comes from that fact that generally builds are structured as configure -> build. What we actually need is "configure some" -> "build some" -> "configure some more" -> "build some more" -> repeat until done.

> ***Generally speaking, you cannot *configure* a project until all the tools and libraries your build system is running tests against are built.***
My crazy, totally unrealistic take is that this is a terrible work flow 
that the world has bought in to anyway.  I would much rather tell the 
build system what to do, as opposed to having it guess these values 
based on the environment.  When you get down to first principles, the 
build process is mostly just a series of shell commands.  The build 
scripts / cmake process is generally responsible for constructing, 
choosing, and sequencing these commands.  However, this is mostly just 
unproductive whining, as I don't know of any general purpose build 
systems that make mixed cross-compiles easy.  It's difficult enough to 
convince conventional build systems to add or remove a compiler flag.

Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project

More information about the llvm-dev mailing list