search for: llvmlibdir

...to me. 2. I don't think the change to CPP.Flags is right. It won't find the LLVM header files 3. Removing the .PRECIOUS line will interfere with correct operation of parallel (make -j N) builds. 4. I don't understand why LLVMUsedLibs and other variables should only be set if LLVMLibDir is defined. Before this change is committed, you need to test that all our scenarios, in each combination: 1. Both with and without OBJ_DIR == SRC_DIR 2. Single and Parallel builds 3. Building LLVM versus building a project (and now building from installed) Reid. Vladimir Merzliakov wrote: &g...

>> Patch attached. >> >> This patch with header installation patch ( >> http://mail.cs.uiuc.edu/pipermail/llvmdev/2005-February/003300.html ) >> let external project (I am test it at my YAFL frontend for LLVM) build >> using installed LLVM version instead using LLVM obj/src dirs. > > I think the patch looks basically sane. The one wierd thing I notice

...bug in LLVM_OBJ_ROOT case in proposed patch :( + LLVMIncDirs := $(LLVM_OBJ_ROOT)/$(BuildMode)/include instead + LLVMIncDirs := $(LLVM_OBJ_ROOT)/include > 3. Removing the .PRECIOUS line will interfere with correct operation of > parallel (make -j N) builds. When external project build $(LLVMLibDir)/.dir $(LLVMToolDir)/.dir $(LLVMExmplDir)/.dir files and directories already exist and then using .PRECIOUS redundent in this case (as i think). In time LLVM build this files and directories listed in line: .PRECIOUS: $(ObjDir)/.dir $(LibDir)/.dir $(ToolDir)/.dir $(ExmplDir)/.dir I will test patch...

...MExmplDir:= $(LLVM_OBJ_ROOT)/$(BuildMode)/examples #-------------------------------------------------------------------- +# Locations of shared libraries +#-------------------------------------------------------------------- + +SharedPrefix := lib +SharedDir := $(LibDir) +LLVMSharedDir := $(LLVMLibDir) + +# Win32.DLL prefers to be located on the "PATH" of binaries. +ifeq ($(HOST_OS), $(filter $(HOST_OS), Cygwin MingW)) + SharedPrefix := + SharedDir := $(ToolDir) + LLVMSharedDir := $(LLVMToolDir) +endif + +ifeq ($(HOST_OS),Cygwin) + SharedPrefix := cyg +endif + +#-------------...

Hi Takumi, > Any feedbacks are welcome. > Have fun! This seems to be pretty useful addition to LLVM on windows! And it seems the only painless way to make plugins working, yay! For me the patch looks pretty good. One minor thing: could you please rename SharedDir => SharedLibDir Thanks! -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg

...:= $(LLVM_OBJ_ROOT)/$(BuildMode)/examples #-------------------------------------------------------------------- +# Locations of shared libraries +#-------------------------------------------------------------------- + +SharedPrefix := lib +SharedLibDir := $(LibDir) +LLVMSharedLibDir := $(LLVMLibDir) + +# Win32.DLL prefers to be located on the "PATH" of binaries. +ifeq ($(HOST_OS), $(filter $(HOST_OS), Cygwin MingW)) + SharedLibDir := $(ToolDir) + LLVMSharedLibDir := $(LLVMToolDir) + + ifeq ($(HOST_OS),Cygwin) + SharedPrefix := cyg + else + SharedPrefix := + endif +e...

...------------ > # Directory locations > +#-------------------------------------------------------------------- > OBJDIR := $(BUILD_OBJ_DIR)/$(CONFIGURATION) > LIBDIR := $(BUILD_OBJ_ROOT)/lib/$(CONFIGURATION) > TOOLDIR := $(BUILD_OBJ_ROOT)/tools/$(CONFIGURATION) > LLVMLIBDIR := $(LLVM_OBJ_ROOT)/lib/$(CONFIGURATION) > LLVMTOOLDIR := $(LLVM_OBJ_ROOT)/tools/$(CONFIGURATION) > > -#------------------------------------------------------------------------------ > +#-------------------------------------------------------------------- > # Full Paths To Compi...

Reid, I think it is the first time it is run that the errors occcur !? Not sure but that would seem logical. Aaron

On Thu, 3 Feb 2005, Vladimir Merzliakov wrote: >> Doing it this way >> allows you to re-use the LLVM build system, as opposed to building your >> own set of Makefiles. > I have pre-LLVM projects in C++ with often used at Unix C++ source file > extention .cc > I modify LLVM build system (original LLVM Makefile.rules already partly > support .cc extention, > for

...r else if LLVM_ROOT set project use for build installed LLVM dir or else project can use only LLVM tools in PATHs if installed LLVM dir added to PATH Also i remove LLVMExmplDir (i not found any it uses in llvm, llvm-java, llvm-test CVS modules) And remove redundent line (as i think): .PRECIOUS: $(LLVMLibDir)/.dir $(LLVMToolDir)/.dir $(LLVMExmplDir)/.dir Any comments? Vladimir -------------- next part -------------- A non-text attachment was scrubbed... Name: Makefile.rules.patch Type: application/octet-stream Size: 6145 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/atta...

> Doing it this way > allows you to re-use the LLVM build system, as opposed to building your > own set of Makefiles. I have pre-LLVM projects in C++ with often used at Unix C++ source file extention .cc I modify LLVM build system (original LLVM Makefile.rules already partly support .cc extention, for example, in Sources and FakeSources make vars setup code). Is attached patch

On Thu, 2007-07-19 at 21:03 -0700, Chris Lattner wrote: > On Thu, 19 Jul 2007, Reid Spencer wrote: > > With the pending reorganization of the software, I have some questions > > about how developers set their PATH and LD_LIBRARY_PATH variables when > > working with LLVM. This is a bit long winded, but bear with me. > > ok :) > > > We're planning to break