[llvm-commits] [llvm] r86955 - in /llvm/trunk: Makefile.config.in autoconf/configure.ac configure include/llvm/Config/config.h.in

[Óscar Fuentes]

Rafael Espindola
<rafael.espindola at gmail.com> writes:

> URL: http://llvm.org/viewvc/llvm-project?rev=86955&view=rev
> Log:
> Add the --with-c-include-dirs to llvm's configure.
> The clang patch is next.
>
>
> Modified:
>     llvm/trunk/Makefile.config.in
>     llvm/trunk/autoconf/configure.ac
>     llvm/trunk/configure
>     llvm/trunk/include/llvm/Config/config.h.in

Do you (the LLVM devs) consider that it is really okay to use the LLVM
config.h file for stuff specific of clang (or any other project that is
not LLVM proper)?

I understand that right now this is forced by the build infraestructure,
but isn't the Right Thing to move clang outside LLVM or, at least,
provide it with its own config mechanism, as gcc does with libstdc++,
for instance?

As far as the CMake build is concerned, it is perfectly feasible to move
clang away and use LLVM as a clang component (the opposite scenario of
we have now). Is it too hard to do this for config&make build?

-- 
Óscar