llvm dev - Nov 2011 - [LLVMdev] [cfe-dev] RFC: Upcoming Build System Changes

Daniel,
        I read this to mean that pretty much everything you want is  
already
in CMakeLists.txt, but you don't like its style/syntax so you are re- 
inventing
the wheel rather than extract the information that is already there.

how about writing a c++ program (rather than perl or python) to extract
the information from CMakeList.txt files, rather than creating yet- 
another
specification language requiring yet more processing tools.


-Peter Lawrence.


On Oct 28, 2011, at 7:10 AM, llvmdev-request at cs.uiuc.edu wrote:
> What This Means For Jane "LLVM Developer" Doe
> ---------------------------------------------
>
> In practice, this means:
>
>  * LLVM requires Python to build.
>
>  * When you add a file to LLVM, you will need to edit LLVMBuild.txt  
> instead of
>   CMakeLists.txt, which will be in a slightly different, but  
> otherwise totally
>   obvious format.
>
>   If you forget to do this, your file will not be built (which will  
> most likely
>   cause a link error eventually). This is better than it being  
> built by Make,
>   but causing CMake build failures when you check in.
>
>  * When you add a new library requirement to an existing component,  
> you will be
>   required to edit LLVMBuild.txt instead of CMakeLists.txt, which  
> will be in a
>   slightly different, but otherwise totally obvious (hopefully)  
> format.
>
>   If you forget to do this, you will either get a link error or a test
>   failure. This is better than library you need transparently  
> getting linked in
>   (with make) because it forces you to think about whether you  
> actually should
>   be adding that dependency.
>
>   The goal is that this also ensures that if LLVM links and passes  
> tests on
>   your system, then it should for everyone else as well.
>
>  * Developers not actively touching the build system should never  
> need to touch
>   a Makefile or a CMake file.
>
> Overall, I believe this should be a quality of life improvement for  
> the
> developer community. The only downside is having to deal with a new  
> non-standard
> LLVM specific format, but I plan to solve this through documentation.
>
> Comments?
>
>  - Daniel
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20111106/1f79cd58/attachment.html>