Displaying 6 results from an estimated 6 matches for "compilecommonopt".
Did you mean:
compilecommonopts
2004 Oct 23
1
[LLVMdev] UPDATE: Makefile.rules Changes (IMPORTANT)
...= -L$(LIBDIR) -L$(LLVMLIBDIR)
> -
> -#------------------------------------------------------------------------------
> +#----------------------------------------------------------
> # Options To Invoke Tools
> +#----------------------------------------------------------
>
> CompileCommonOpts := -Wall -W -Wwrite-strings -Wno-unused
>
> +LDFLAGS += -L$(LIBDIR) -L$(LLVMLIBDIR)
> CPPFLAGS += -I$(BUILD_OBJ_DIR) \
> -I$(BUILD_SRC_DIR) \
> -I$(BUILD_SRC_ROOT)/include \
> @@ -198,54 +169,57 @@
> -I$(LLVM_SRC_ROOT)/include \
>...
2005 Jan 07
1
[LLVMdev] Shared library building problems on Darwin
...o I tried the same hack I found earlier:
--- Makefile.rules 3 Jan 2005 17:42:57 -0000 1.287
+++ Makefile.rules 7 Jan 2005 02:29:22 -0000
@@ -326,7 +326,7 @@
LTCompile.CXX = $(LIBTOOL) $(LibTool.Flags) --mode=compile $(Compile.CXX)
BCCompile.CXX = $(LLVMGXXWITHPATH) $(CPP.Flags) $(CompileCommonOpts) \
$(CXX.Flags) -c
-Link = $(LIBTOOL) $(LibTool.Flags) --mode=link $(CXX) $(CPP.Flags) \
+Link = $(LIBTOOL) $(LibTool.Flags) --mode=link $(CXX)
-module $(CPP.Flags) \
$(CompileCommonOpts) $(LD.Flags) $(Strip)
Relink = $(LIBTOOL) $(LibTool....
2005 Jan 11
2
[Fwd: Re: [LLVMdev] Shared library building problems on Darwin]
...3 Jan 2005 17:42:57 -0000 1.287
> > > +++ Makefile.rules 7 Jan 2005 02:29:22 -0000
> > > @@ -326,7 +326,7 @@
> > > LTCompile.CXX = $(LIBTOOL) $(LibTool.Flags) --mode=compile $(Compile.CXX)
> > > BCCompile.CXX = $(LLVMGXXWITHPATH) $(CPP.Flags) $(CompileCommonOpts) \
> > > $(CXX.Flags) -c
> > > -Link = $(LIBTOOL) $(LibTool.Flags) --mode=link $(CXX) $(CPP.Flags) \
> > > +Link = $(LIBTOOL) $(LibTool.Flags) --mode=link $(CXX)
> > > -module $(CPP.Flags) \
> > > $(Com...
2005 Jan 11
0
[Fwd: Re: [LLVMdev] Shared library building problems on Darwin]
...42:57 -0000 1.287
> > > > +++ Makefile.rules 7 Jan 2005 02:29:22 -0000
> > > > @@ -326,7 +326,7 @@
> > > > LTCompile.CXX = $(LIBTOOL) $(LibTool.Flags) --mode=compile $(Compile.CXX)
> > > > BCCompile.CXX = $(LLVMGXXWITHPATH) $(CPP.Flags) $(CompileCommonOpts) \
> > > > $(CXX.Flags) -c
> > > > -Link = $(LIBTOOL) $(LibTool.Flags) --mode=link $(CXX) $(CPP.Flags) \
> > > > +Link = $(LIBTOOL) $(LibTool.Flags) --mode=link $(CXX)
> > > > -module $(CPP.Flags) \
> > > &...
2005 May 19
3
[LLVMdev] [Cygwin] llvm 'make install' build errors
Reid,
I think it is the first time it is run that the errors occcur !?
Not sure but that would seem logical.
Aaron
2009 Jan 02
3
[LLVMdev] Private headers and testing
2009/1/2 Chris Lattner <clattner at apple.com>
> On Jan 2, 2009, at 12:21 PM, Misha Brukman wrote:
> Do you have a specific example of a unit test that would need these? I
> really think these should stay private.
>
Let's take lib/Transforms/Utils/CodeExtractor.cpp . The public interface
for it is in include/llvm/Transform/Utils/FunctionUtils.h, with only the
high-level