search for: tooldir

...EXE): $(T_UNSAFE_OBJ) $(CC) $(CFLAGS) $(LDFLAGS) -o $@ $(T_UNSAFE_OBJ) $(LIBS) # I don't like these rules because CVS can skew the timestamps and @@ -157,14 +162,14 @@ test: check # might lose in the future where POSIX diverges from old sh. check: all $(CHECK_PROGS) - POSIXLY_CORRECT=1 TOOLDIR=`pwd` rsync_bin=`pwd`/rsync$(EXEEXT) srcdir="$(srcdir)" $(srcdir)/runtests.sh + POSIXLY_CORRECT=1 TOOLDIR=`pwd` rsync_bin=`pwd`/$(RSYNC_EXE) srcdir="$(srcdir)" $(srcdir)/runtests.sh # This does *not* depend on building or installing: you can use it to # check a version insta...

...r cygwin in future) - I have not checked llvmc. * TODO - check system's stdc++.dll and use it with autoconf. -------------- next part -------------- diff --git a/Makefile.rules b/Makefile.rules index 66666b4..2a2128b 100644 --- a/Makefile.rules +++ b/Makefile.rules @@ -498,6 +498,25 @@ LLVMToolDir := $(LLVM_OBJ_ROOT)/$(BuildMode)/bin LLVMExmplDir:= $(LLVM_OBJ_ROOT)/$(BuildMode)/examples #-------------------------------------------------------------------- +# Locations of shared libraries +#-------------------------------------------------------------------- + +SharedPrefix := lib +Share...

...mpiling a simple +# "clang -fsanitize=(address|undefined) -m32/-m64" work. +# We check that Clang can produce working 32/64-bit binaries by compiling a simple # executable. test_source = $(LLVM_SRC_ROOT)/tools/clang/runtime/compiler-rt/clang_linux_test_input.c +ifeq ($(call TryCompile,$(ToolDir)/clang,$(test_source),-m64),0) +RuntimeLibrary.linux.Configs += $(Runtime64BitConfigs) +endif ifeq ($(call TryCompile,$(ToolDir)/clang,$(test_source),-m32),0) -RuntimeLibrary.linux.Configs += $(Runtime32BitConfigs) +RuntimeLibrary.linux.Configs += $(Runtimex86Configs) +endif +else +RuntimeLibrary....

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

...th best regards, Anton Korobeynikov > Faculty of Mathematics and Mechanics, Saint Petersburg State University > -------------- next part -------------- diff --git a/Makefile.rules b/Makefile.rules index 66666b4..8b50eb6 100644 --- a/Makefile.rules +++ b/Makefile.rules @@ -498,6 +498,26 @@ LLVMToolDir := $(LLVM_OBJ_ROOT)/$(BuildMode)/bin LLVMExmplDir:= $(LLVM_OBJ_ROOT)/$(BuildMode)/examples #-------------------------------------------------------------------- +# Locations of shared libraries +#-------------------------------------------------------------------- + +SharedPrefix := lib +Sh...

....h clean: cleantests - rm -f *~ $(OBJS) rsync $(TLS_OBJ) $(CHECK_PROGS) + rm -f *~ $(OBJS) $(TLS_OBJ) $(CHECK_PROGS) cleantests: rm -rf ./testtmp* @@ -151,14 +153,14 @@ test: check # might lose in the future where POSIX diverges from old sh. check: all $(CHECK_PROGS) - POSIXLY_CORRECT=1 TOOLDIR=`pwd` rsync_bin=`pwd`/rsync srcdir="$(srcdir)" $(srcdir)/runtests.sh + POSIXLY_CORRECT=1 TOOLDIR=`pwd` rsync_bin=`pwd`/rsync$(EXEEXT) srcdir="$(srcdir)" $(srcdir)/runtests.sh # This does *not* depend on building or installing: you can use it to # check a version installed fr...

...g -fsanitize=(address|undefined) -m32/-m64" work. > +# We check that Clang can produce working 32/64-bit binaries by > compiling a simple > # executable. > test_source = > $(LLVM_SRC_ROOT)/tools/clang/runtime/compiler-rt/clang_linux_test_input.c > +ifeq ($(call TryCompile,$(ToolDir)/clang,$(test_source),-m64),0) > +RuntimeLibrary.linux.Configs += $(Runtime64BitConfigs) > +endif > ifeq ($(call TryCompile,$(ToolDir)/clang,$(test_source),-m32),0) > -RuntimeLibrary.linux.Configs += $(Runtime32BitConfigs) > +RuntimeLibrary.linux.Configs += $(Runtimex86Configs) >...

> Vladimir, > > I took a *very quick* look at your patch. I won't be able to look at it in > more detail until this weekend, but perhaps you can address a couple of > concerns: > > 1. I don't understand the need for LLVMToolDirSlash. This seems like a > gratuitous change to me. If LLVM_OBJ_ROOT (with LLVM_SRC_ROOT) and LLVM_ROOT both not set without LLVMToolDirSlash we will have "/gccas$(EXEEXT)", for example. This is not problem for project that not use LLVM tools and libs. But this not permite one useful...

Vladimir, I took a *very quick* look at your patch. I won't be able to look at it in more detail until this weekend, but perhaps you can address a couple of concerns: 1. I don't understand the need for LLVMToolDirSlash. This seems like a gratuitous change 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...

...g quotes R_output = arcpy.GetParameterAsText(2) # polygon input file R_output_RCMD = '"' + data_input + '"' # add the string quotes ########## Get R Tool Directory and Tool Name ########## pyScript = SYS.argv[0] # Get the path for the Python Script toolDir = OS.path.dirname(pyScript) # Get the directory tree for the Python Script rScript = OS.path.join(toolDir, "MyRsemivar.r") # Concatenate the directory with the R script name rScript = '"' + rScript + '"' # add the string quotes ########## Create and...

...gt; +#-------------------------------------------------------------------- > # 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) > > -#------------------------------------------------------------------------------ > +#-------------------------------...

>> 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

...\/,$(BuildMode))/' \ >> temp.sed + $(Verb) $(ECHO) 's/@LLVM_LIBDIR_SUFFIX@/$(subst /,\/,$(LLVM_LIBDIR_SUFFIX))/' \ + >> temp.sed $(Verb) $(SED) -f temp.sed < $< > $@ $(Verb) $(RM) temp.sed $(Verb) cat PerobjDepsInclFinal.txt >> $@ @@ -106,6 +110,8 @@ $(ToolDir)/llvm-config: llvm-config.in $(FinalLibDeps) >> temp.sed $(Verb) $(ECHO) 's/@LLVM_BUILDMODE@/$(subst /,\/,$(BuildMode))/' \ >> temp.sed + $(Verb) $(ECHO) 's/@LLVM_LIBDIR_SUFFIX@/$(subst /,\/,$(LLVM_LIBDIR_SUFFIX))/' \ + >> temp.sed $(Verb) $(SED) -f t...

...elper programs it # should depend on them too. # We try to run the scripts with POSIX mode on, in the hope that will # catch Bash-isms earlier even if we're running on GNU. Of course, we # might lose in the future where POSIX diverges from old sh. check: all $(CHECK_PROGS) POSIXLY_CORRECT=1 TOOLDIR=`pwd` rsync_bin=`pwd`/rsync srcdir="$(srcdir)" $(srcdir)/runtests.sh # This does *not* depend on building or installing: you can use it to # check a version installed from a binary or some other source tree, # if you want. installcheck: $(CHECK_PROGS) POSIXLY_CORRECT=1 TOOLDIR=`pwd` rs...

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

...or the --exec-prefix and --target options supplied to configure. These two values are combined to create the FLAGS_FOR_TARGET variable that gets propagated to the later build phases: The paths are built up as follows (see configure for details) FLAGS_FOR_TARGET=$FLAGS_FOR_TARGET' -B$(build_tooldir)/bin/ -B$(build_tooldir)/lib/ -isystem $(build_tooldir)/include -isystem $(build_tooldir)/sys-include' where: build_tooldir = $tooldir and where: tooldir = '${exec_prefix}'/${target_alias} and finally where: $target_alias = $target 7. It would seem that I might possibly sol...

.... * $(DEST*) variables are gone unless they specifically refer to the installation destination. These conflicted with standard makefile usage * $(BUILD_OBJ_DIR)/$(CONFIGURATION) became $(OBJDIR) to simplify it. This is where object files should go. * $(LIBDIR) is where libraries should go * $(TOOLDIR) is where tools (executables) should go * VERBOSE=1 mode is now even quieter (a few rules were missing $(VERB) * Build messages have been corrected and made more indicative * The "prdirs" target has been replaced with the "printvars" target which prints values for interesting...

...>> temp.sed > + $(Verb) $(ECHO) 's/@LLVM_LIBDIR_SUFFIX@/$(subst /,\/,$(LLVM_LIBDIR_SUFFIX))/' \ > + >> temp.sed > $(Verb) $(SED) -f temp.sed < $< > $@ > $(Verb) $(RM) temp.sed > $(Verb) cat PerobjDepsInclFinal.txt >> $@ > @@ -106,6 +110,8 @@ $(ToolDir)/llvm-config: llvm-config.in $(FinalLibDeps) > >> temp.sed > $(Verb) $(ECHO) 's/@LLVM_BUILDMODE@/$(subst /,\/,$(BuildMode))/' \ > >> temp.sed > + $(Verb) $(ECHO) 's/@LLVM_LIBDIR_SUFFIX@/$(subst /,\/,$(LLVM_LIBDIR_SUFFIX))/' \ > + >> temp.sed...

Clang patch for X32 support. Applies against current trunk. --- ./tools/clang/include/clang/Driver/Options.td.orig 2013-05-16 21:51:51.286129820 +0000 +++ ./tools/clang/include/clang/Driver/Options.td 2013-05-16 21:53:24.875004239 +0000 @@ -841,6 +841,7 @@ HelpText<"Enable hexagon-qdsp6 backward compatibility">; def m3dnowa : Flag<["-"], "m3dnowa">,

...e gone unless they specifically refer to the > installation destination. These conflicted with standard makefile usage > * $(BUILD_OBJ_DIR)/$(CONFIGURATION) became $(OBJDIR) to simplify it. This is > where object files should go. > * $(LIBDIR) is where libraries should go > * $(TOOLDIR) is where tools (executables) should go > * VERBOSE=1 mode is now even quieter (a few rules were missing $(VERB) > * Build messages have been corrected and made more indicative > * The "prdirs" target has been replaced with the "printvars" target which > prints va...