cross build, so that a native version of clang-tblgen is available.
Should unbreak Clang cross build.

Also disable Polly for the native tool build, since it depends on
external libraries which may not be available, and it isn't required
anyway.

llvm-svn: 141454

This is the first step towards splitting LLVM and Clang's tblgen executables.

llvm-svn: 140951

The problems that llvmc solved have largely been subsumed with the
tasks that the clang driver can accomplish, but llvmc lacks flexibility
and depends too heavily on the EOL'd llvm-gcc.

llvm-svn: 140093

<rdar://problem/9583891>

llvm-svn: 132860

If enabled, this will attempt to use the CC_LOG_DIAGNOSTICS feature I dropped
into Clang to print a log of all the diagnostics generated during an individual
build (from the top-level). Not sure if this will actually be useful, but for
now it is handy for testing the option.

llvm-svn: 129312

llvm-svn: 120298

llvm-svn: 120196

llvm-svn: 118918

llvm-svn: 111094

llvm-svn: 110003

llvmCore for the iOS Simulator.

llvm-svn: 108922

llvm-svn: 108493

and not just for Debug+Asserts builds.

llvm-svn: 107792

who knows how to cover Asserts or Debug separately
please do not hesitate to extend this

llvm-svn: 107779

builds to "Release".  The default build is unchanged (optimization on,
assertions on), however it is now called Release+Asserts.  The intent
is that future LLVM releases released via llvm.org will be Release builds
in the new sense, i.e. will have assertions disabled (currently they have
assertions enabled, for a more than 20% slowdown).  This will bring them
in line with MacOS releases, which ship with assertions disabled.  It also
means that "Release" now means the same things in make and cmake builds:
cmake already disables assertions for "Release" builds AFAICS.

llvm-svn: 107758

llvm-svn: 107334

llvm-svn: 102803

llvm-svn: 102751

cross-build Makefile needs to unset CFLAGS/CXXFLAGS when building the build-side utilities since the flags will be for the cross-compiler.

llvm-svn: 102225

llvm-svn: 99148

--enable-shared is passed to configure.

llvm-svn: 97119

llvm-svn: 96981

the examples shared to make sure the shared library keeps working.

llvm-svn: 96959

llvm-svn: 96907

llvm-svn: 96569

--enable-shared configure flag to have the tools linked shared. (2.7svn is just
$(LLVMVersion) so it'll change to "2.7" in the release.)  Always link the
example programs shared to test that the shared library keeps working.

On my mac laptop, Debug libLLVM2.7svn.dylib is 39MB, and opt (for example) is
16M static vs 440K shared.

Two things are less than ideal here:
1) The library doesn't include any version information. Since we expect to break
the ABI with every release, this shouldn't be much of a problem. If we do
release a compatible 2.7.1, we may be able to hack its library to work with
binaries compiled against 2.7.0, or we can just ask them to recompile. I'm
hoping to get a real packaging expert to look at this for the 2.8 release.
2) llvm-config doesn't yet have an option to print link options for the shared
library. I'll add this as a subsequent patch.

llvm-svn: 96559

llvm-svn: 93958

llvm-svn: 91226

llvm-svn: 89841

Don't build examples by default, use BUILD_EXAMPLES=1 to build them. The only utility of this is testing that we keep the examples up to date, I will just make the buildbots run with this flag.

llvm-svn: 88979

apply to the build tools. If we want to allow build tool flags input, we
should have separate inputs (BUILD_CFLAGS and BUILD_CXXFLAGS, perhaps).

llvm-svn: 85607

llvm-svn: 85606

llvm-svn: 85605

direct inclusion edge from System to Support.

llvm-svn: 85086

llvm-svn: 85082

Now with Clang-compatibility.

llvm-svn: 84872

breaking Clang's Apple-style build.

llvm-svn: 84592

llvm-svn: 84507

Thanks to Chris for heads-up!

llvm-svn: 83613

too.

llvm-svn: 82873