search for: librarynam

...sFile) @@ -1025,6 +1068,8 @@ endif endif +endif + ############################################################################### # Library Build Rules: Four ways to build a library ############################################################################### @@ -1097,10 +1142,10 @@ ifdef LIBRARYNAME LIBRARYNAME := $(strip $(LIBRARYNAME)) ifdef LOADABLE_MODULE LibName.A := $(LibDir)/$(LIBRARYNAME).a -LibName.SO := $(LibDir)/$(LIBRARYNAME)$(SHLIBEXT) +LibName.SO := $(SharedDir)/$(LIBRARYNAME)$(SHLIBEXT) else LibName.A := $(LibDir)/lib$(LIBRARYNAME).a -LibName.SO := $(LibDir)/lib$(LIBRARY...

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

...sFile) @@ -1025,6 +1069,8 @@ endif endif +endif + ############################################################################### # Library Build Rules: Four ways to build a library ############################################################################### @@ -1097,10 +1143,10 @@ ifdef LIBRARYNAME LIBRARYNAME := $(strip $(LIBRARYNAME)) ifdef LOADABLE_MODULE LibName.A := $(LibDir)/$(LIBRARYNAME).a -LibName.SO := $(LibDir)/$(LIBRARYNAME)$(SHLIBEXT) +LibName.SO := $(SharedLibDir)/$(LIBRARYNAME)$(SHLIBEXT) else LibName.A := $(LibDir)/lib$(LIBRARYNAME).a -LibName.SO := $(LibDir)/lib$(LIBR...

...> done > + > +$(sysconfdir): > + $(MKDIR) $(sysconfdir) > + > endif > > -########################################################################### > -# Library Build Rules: > -# > -#--------------------------------------------------------- > -# Handle the LIBRARYNAME option - used when building libs... > -#--------------------------------------------------------- > -# > -# When libraries are built, they are allowed to optionally define the > -# DONT_BUILD_RELINKED make variable, which, when defined, prevents a .o file > -# from being built fo...

...;%s"' % dep diff --git a/utils/unittest/UnitTestMain/Makefile b/utils/unittest/UnitTestMain/Makefile index 3082779..7bcb724 100644 --- a/utils/unittest/UnitTestMain/Makefile +++ b/utils/unittest/UnitTestMain/Makefile @@ -11,7 +11,7 @@ LEVEL = ../../.. include $(LEVEL)/Makefile.config -LIBRARYNAME = UnitTestMain +LIBRARYNAME = gtest_main BUILD_ARCHIVE = 1 REQUIRES_RTTI = 1 diff --git a/utils/unittest/googletest/Makefile b/utils/unittest/googletest/Makefile index 21b29ff..22c8f36 100644 --- a/utils/unittest/googletest/Makefile +++ b/utils/unittest/googletest/Makefile @@ -11,7 +11,7 @@ LE...

Hi, some discussion below. Reid wrote: > 3. Fix your Makefile to build a shared library properly. You have set > TOOLNAME which is for building an executable tool not a shared > library. You need to set LIBRARYNAME=..., not TOOLNAME=... I remember having failed to build a functioning Python extension module with LIBRARYNAME and SHARED_LIBRARY flags. Anyway, I cannot remember the details now so will try again. > 4. Fix the name of your project. It currently builds "llvm.so" which > is no...

...did tweak the line (127, incidentally) of code. <http://r.789695.n4.nabble.com/R-Problem-with-sas-get-function-in-Hmisc-td81 4367.html> http://r.789695.n4.nabble.com/R-Problem-with-sas-get-function-in-Hmisc-td814 367.html However, I get the following error message: > sas.get(libraryName="D:/Docs/tmp", member="SES", formats=F) Error in sas.get(libraryName = "D:/Docs/tmp", member = "SES", : SAS job failed with status 127 I suspected some problem related to formats or variable names, and reduced the data to a bare minimum, and still...

...rary13PIP_Tree_Node2OKEv > -load request ignored. Let me explain how I get to this point. To make simpler my explanation I took the "Hello World" pass provided in the directory llvm/lib/Transforms/Hello/Hello.cpp. I compiled Hello.cpp using the Makefile: > LEVEL=../../../.. > LIBRARYNAME=MyAnalysis > LOADABLE_MODULE=1 > SHARED_LIBRARY=1 > include $(LEVEL)/Makefile.common and then: clang test.c -c -emit-llvm -o test.bc opt -load /home/jorge/SvnReps/Systems/llvm/build/Debug+Asserts/lib/MyAnalysis.so -hello -stats test.bc > Hello: modulo > ===----------------------...

...OS: Win98 Submission from: (NULL) (134.95.43.165) Using libraries "spatstat" and "sm" on R.2.0.1. under Windows 98 bug 1) the libraries "spatstat" and "sm" are not properly identified by the "library()" command on R.2.0.1. (R for Windows98). the libraryname is shown in upper case ("SPATSTAT") although the original name is in lower case ("spatstat") and no good commentary is available - instead the returned commentary in both cases reads "**No title available (pre-2.0.0.install?)". i suppose the following problem to be...

...libgcc_s.so.1 => /lib/i386-linux-gnu/libgcc_s.so.1 (0xb778d000) libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xb7611000) /lib/ld-linux.so.2 (0xb78cf000) libm.so.6 => /lib/i386-linux-gnu/libm.so.6 (0xb75e7000) So I guess, my problem is in LD.Flags ? >> LEVEL=../../../.. >> LIBRARYNAME=MyAnalysis >> LOADABLE_MODULE=1 >> SHARED_LIBRARY=1 >> include $(LEVEL)/Makefile.common >> >> # These two lines are new: >> CXX.Flags += -I/home/jorge/include -fexceptions -Wno-variadic-macros >> LD.Flags += -L/home/jorge/lib -lppl -lgmp >> Ciao...

...ll help you set up a project. You might also find the Projects section of http://llvm.cs.uiuc.edu/docs/MakefileGuide.html useful. 3. Fix your Makefile to build a shared library properly. You have set TOOLNAME which is for building an executable tool not a shared library. You need to set LIBRARYNAME=..., not TOOLNAME=... 4. Fix the name of your project. It currently builds "llvm.so" which is not correct by our naming standards. It should result to something like "libLLVMpy.so" which will be obtained if you set LIBRARYNAME to "LLVMpy" 5. Consider waiting...

...Duncan. > > Let me explain how I get to this point. > > To make simpler my explanation I took the "Hello World" pass provided > in the directory llvm/lib/Transforms/Hello/Hello.cpp. > > I compiled Hello.cpp using the Makefile: > >> LEVEL=../../../.. >> LIBRARYNAME=MyAnalysis >> LOADABLE_MODULE=1 >> SHARED_LIBRARY=1 >> include $(LEVEL)/Makefile.common > > and then: > > clang test.c -c -emit-llvm -o test.bc > opt -load /home/jorge/SvnReps/Systems/llvm/build/Debug+Asserts/lib/MyAnalysis.so -hello -stats test.bc > >> He...

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

...nents UsedLibs = $(shell $(LLVM_CONFIG) --libs $(UsedComponents)) UsedLibNames = $(shell $(LLVM_CONFIG) --libnames $(UsedComponents)) endif # Tools OCAMLCFLAGS += -I $(OcamlDir) -I $(ObjDir) ifneq ($(ObjectsO),) OCAMLAFLAGS += $(patsubst %,-cclib %, \ $(filter-out -L$(LibDir),-l$(LIBRARYNAME) \ $(shell $(LLVM_CONFIG) -- ldflags)) \ $(UsedLibs)) else OCAMLAFLAGS += $(patsubst %,-cclib %, \ $(filter-out -L$(LibDir),$(shell $(LLVM_CONFIG) -- ldflags)) \...

Hi, I've updated the Python LLVM bindings for LLVM 1.5 (attached). I also thought of setting up a CVS repository for this, but before I do that I thought I'd ask if you want to take the Python bindings to the main LLVM CVS? I noticed that the C language bindings would be maintained there. Changes in Python-LLVM: - Updated to match LLVM 1.5 API - Added Windows build support (created

I have an issue with the OCaml build system and the ExecutionEngine. PR2128 has a patch to change the Interpreter to use libffi. This breaks test/Bindings/Ocaml/executionengine.ml because OCaml doesn't try to link with libffi, even though llvm-config knows that we should: $ Debug/bin/llvm-config --ldflags interpreter -L/home/nicholas/llvm-commit/Debug/lib -lpthread -lffi -ldl -lm

Hello, I have a question about how to set up a Makefile that generate a .so that I can load into opt without getting duplicate symbols. Here's what I have right now: LIBRARYNAME=previrt SHARED_LIBRARY=previrt LINK_COMPONENTS := transformUtils LINK_LIBS_IN_SHARED=1 include $(LEVEL)/Makefile.common LIBS += -lprotobuf CPPFLAGS += -I${HOME}/.root/usr/include -DGOOGLE_PROTOBUF_NO_RTTI LDFLAGS += -Wl,-L${HOME}/.root/usr/lib/ PROTOC=${HOME}/.root/usr/bin/protoc I'm prett...

...I used "make" command instead of "gmake", could it be the problem? Or maybe I just type (copy) something wrong? Could someone take a look of my files and point my errors out? Thanks in advance, Juan Carlos ***************** *** Makefile *** ***************** LEVEL = ../../.. LIBRARYNAME = MyPass LOADABLE_MODULE = 1 LLVMLIBS = LLVMCore.a LLVMSupport.a LLVMSystem.a include $(LEVEL)/Makefile.common ********************** *** MyPass.cpp *** ********************** #include "llvm/Pass.h" #include "llvm/Function.h" #include "llvm/Support/raw_ostream.h" us...

...├── mypass.c └── sub ├── basic.cpp ├── basic.h └── Makefile The problem is that basic.cpp will never be compiled into the loadable module which mypass.c symbols lies in. And LLVMLIBS USEDLIBS doesn't work either. Here is mypass/Makefile LEVEL = ../../.. DIRS = sub LIBRARYNAME = mypass LOADABLE_MODULE = 1 include $(LEVEL)/Makefile.common And mypass/sub/Makefile LEVEL = ../../../.. # LIBRARYNAME = test_sub # ARCHIVE_LIBRARY = 1 # LOADABLE_MODULE = 1 include $(LEVEL)/Makefile.common When mypss/sub/Makefile uses LOADABLE_MODULE = 1 with another library...

...cerr<<"Copying: "<<j->getName()<<" "<<InstructionList.size()<<endl; ...... ...... } RegisterPass<MParSchedule> X("MParSchedule","MParSchedule"); ------------------------ Makefile MParschedule LEVEL = ../../../.. LIBRARYNAME= MParSchedule BUILD_ARCHIVE=1 SHARED_LIBRARY = 1 LOADABLE_MODULE= 1 include $(LEVEL)/Makefile.common ------------------------- Makefile MyBackend LEVEL = ../../.. LIBRARYNAME = MyBackend PARALLEL_DIRS = MParSchedule USEDLIBS = MParSchedule.o LLVMLIBS = LLVMCore.a LLVMSupport.a LLVMSystem.a MParS...