Displaying 2 results from an estimated 2 matches for "llvmbasepath".
2006 Mar 14
0
[LLVMdev] Getting Started with LLVM
...ult. But this is still pretty fragile, and needs be done
> once for every supported platform.
Ok. This is a reasonable way to do it. FWIW, I have a similar problem in
the new llvm-gcc, which links to LLVM optimizations and native targets.
The makefile goop I have looks like this:
ifneq ($(LLVMBASEPATH),)
ifdef CHECKING_ENABLED
BUILDMODE=Debug
else
BUILDMODE=Release
endif
LLVMLIBPATH = $(LLVMBASEPATH)/$(BUILDMODE)/lib
# Pick the right LLVM backend based on the target triple.
LLVMTARGETOBJCMD := case $(target) in \
alpha-*-*) echo LLVMAlpha.o;; \
ia64-*...
2006 Mar 10
2
[LLVMdev] Getting Started with LLVM
On Mar 10, 2006, at 2:57 PM, Martin Pärtel wrote:
> I'm currently using the "make install"-ed version of LLVM in an
> autoconf/automake project. Setting it up wasn't that bad really.
> The .a
> libraries can be statically linked with the -l flag and .o
> libraries are
> simply linked in as normal object files (without -l). All the
> libraries got
>