search for: build_arch

...estMain/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 @@ LEVEL := ../../.. include $(LEVEL)/Makefile.config...

...teModulePassManager() so I can add my pass to standard passes. It all works if I add all my files in the lib/Transforms/IPO directory. But I want to keep them away in the lib/Transforms/Obfuscation directory. This is my Makefile: LEVEL = ../../.. LIBRARYNAME = LLVMobfuscation LOADABLE_MODULE = 1 BUILD_ARCHIVE = 1 include $(LEVEL)/Makefile.common My CMakeListes.txt add_llvm_library(LLVMobfuscation Cgf.cpp CgfFunction.cpp Flattening.cpp ) add_dependencies(LLVMobfuscation intrinsics_gen) and my LLVMBuild.txt [component_0] type = Library name = Obfuscation parent = Transforms library_name =...

...hich will want an archive or shared library. If a relinked library is needed, something link RELINKED_LIBRARY=1 should be specified so that it documents in the makefile what is getting built. 5. Some of the names of the directives are a little confusing. We have BUILD_ARCHIVE to specify building an archive. But, we have SHARED_LIBRARY to specify building a shared library. I think these should all be named BUILD_<thing_to_build> so we'd have BUILD_ARCHIVE_LIBRARY and BUILD_SHARED_LIBRARY and BUILD_RELINKD_LIBRARY and BUILD_TOO...

...errors while trying to create one). So I have it working with CMake on windows but when I try to run the same code base on mac I get unresolved externals. Here is what I have done so far in the build system: Within lib/Transforms/MyPass I have: Makefile: LEVEL = ../../.. LIBRARYNAME = LLVMMyPass BUILD_ARCHIVE = 1 include $(LEVEL)/Makefile.common CMakeLists.txt add_llvm_library(LLVMMyPass MyPass.cpp) And within the Transforms directory I added my directory to the list of PARALLEL_DIRS within the Makefile there. In the root llvm directory's CMakeLists.txt I added a call to add_subdirectory(lib/T...

On Fri, 2005-05-27 at 18:10 -0400, Alexander Friedman wrote: > On May 26, Reid Spencer wrote: > > Alexander, > > > > Yes, a patch like that would be accepted. Fewer dependencies = good :) > > > > Some notes on doing this: > > > > (1) Please make sure you use the std c++ iostream libraries for doing > > I/O. No native calls (we end up with

...library. If a relinked library is needed, something link > RELINKED_LIBRARY=1 should be specified so that it documents in > the makefile what is getting built. I think this is fine. > 5. Some of the names of the directives are a little confusing. We > have BUILD_ARCHIVE to specify building an archive. But, we have > SHARED_LIBRARY to specify building a shared library. I think > these should all be named BUILD_<thing_to_build> so we'd have > BUILD_ARCHIVE_LIBRARY and BUILD_SHARED_LIBRARY and > BUILD_RELINKD_LIBRA...

...or shared > library. If a relinked library is needed, something link > RELINKED_LIBRARY=1 should be specified so that it documents in > the makefile what is getting built. > 5. Some of the names of the directives are a little confusing. We > have BUILD_ARCHIVE to specify building an archive. But, we have > SHARED_LIBRARY to specify building a shared library. I think > these should all be named BUILD_<thing_to_build> so we'd have > BUILD_ARCHIVE_LIBRARY and BUILD_SHARED_LIBRARY and > BUILD_RELINKD_L...

...or shared > library. If a relinked library is needed, something link > RELINKED_LIBRARY=1 should be specified so that it documents in > the makefile what is getting built. > 5. Some of the names of the directives are a little confusing. We > have BUILD_ARCHIVE to specify building an archive. But, we have > SHARED_LIBRARY to specify building a shared library. I think > these should all be named BUILD_<thing_to_build> so we'd have > BUILD_ARCHIVE_LIBRARY and BUILD_SHARED_LIBRARY and > BUILD_RELINKD_L...

...library. If a relinked library is needed, something link > > RELINKED_LIBRARY=1 should be specified so that it documents in > > the makefile what is getting built. > > 5. Some of the names of the directives are a little confusing. We > > have BUILD_ARCHIVE to specify building an archive. But, we have > > SHARED_LIBRARY to specify building a shared library. I think > > these should all be named BUILD_<thing_to_build> so we'd have > > BUILD_ARCHIVE_LIBRARY and BUILD_SHARED_LIBRARY and > >...

> You'll better investigate why exception support is required for MSYS > while all other configure-based builds work fine without it. Surely it's required for any system that uses lib/System/Win32/Signals.inc, because there's code in that file that uses try/catch. MingW is the only system I know of that uses that file; Cygwin pretends to be Unix-like, so it uses

...objects from a particular library in to a tool, e.g., opt, which needs to link in all optimizations, even those which it does not explicitly reference. There's nothing wrong with building .a versions of all libraries, we just don't do that right now. Check out the Makefile.rules BUILD_ARCHIVE option. 4) The GNU linker is very, very slow, mostly because it has not been tuned for performance by its developers. Some improvements may be forthcoming in the current CVS version of binutils; you may want to try it out. -Brian -- gaeke at uiuc.edu ----- End forwarded message -----...

On 9/2/06, Chris Lattner <sabre at nondot.org> wrote: > > Make sure to add it to Codegen/LinkAllCodegenComponents.h. I'm sure I did. I did so from the first time and I also needed to add my library .a file to the USEDLIBS variable within llc makefile to build llc. I wonder how lli links with all the rest LLVM as it seems to include no lib within its makefile. May be I need to

On Sat, 2 Sep 2006, Anton Vayvod wrote: > I'm sure I did. I did so from the first time and I also needed to add my > library .a file to the USEDLIBS variable within llc makefile to build llc. > I wonder how lli links with all the rest LLVM as it seems to include no lib > within its makefile. May be I need to include/link my lib somewhere else? Ah, that's probably it. Try

...pying: "<<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 MParSchedule.a #LIBS += -lMParSc...

...====================================== RCS file: /home/vadve/shared/PublicCVS/llvm/runtime/libpng/Makefile,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- Makefile 20 Feb 2004 21:26:46 -0000 1.2 +++ Makefile 26 Mar 2004 17:04:53 -0000 1.3 @@ -11,6 +11,7 @@ BUILD_ARCHIVE=1 DONT_BUILD_RELINKED=1 LIBRARYNAME=png +CPPFLAGS += -I../zlib Source = png.c pngset.c pngget.c pngrutil.c pngtrans.c pngwutil.c \ pngread.c pngrio.c pngwio.c pngwrite.c pngrtran.c \ This is fixed in CVS. You might consider upgrading to LLVM CVS, especially if you are inte...

...s the ability to do something like: link a.obj b.obj c.obj /out abc.obj (pardon my lack of knowledge on the MS linker) note that the output file is .obj not .exe. If the linker can do that, then you want to build every library this way. If the "Makefile" in a lib directory says "BUILD_ARCHIVE = 1" then you also want to build a regular library (.lib). If it says "SHARED_LIBRARY = 1" then you want to build a DLL from it (might not be possible, DLLs have some code requirements we don't support, I think .. e.g. export/import ). Reid. -------------- next part ---------...

> > yesterday I got new SuSE 9.1 DVD, so i am going to enter this > > river again. Perhaps, this time all will be fine. > > Sounds great, please let me know how it goes. SuSE 9.1 is running OK. after 30 minute of compilation i get first errors: ********************* make[2]: Leaving directory `/pool/tmp/llvm/runtime/libtrace' make[2]: Entering directory

Hallo and Merry Christmas to all! I need the rpm-files of samba 3.3 or later for opensuse 10.2. The repo isn?t available any more, so can anybody help me here? Thanks in advance! Peter

Hi George, > This is the seg fault I am getting. > > dyld: lazy symbol binding failed: Symbol not found: > __ZN4llvm13IRBuilderBase18CreateGlobalStringEPKcRKNS_5TwineE > Referenced from: > /Users/georgebaah/llvm_dir/llvm-2.8/Debug+Asserts/lib/LLVMArrayBoundsCheck.dylib > Expected in: flat namespace > > dyld: Symbol not found:

On May 26, Reid Spencer wrote: > Alexander, > > Yes, a patch like that would be accepted. Fewer dependencies = good :) > > Some notes on doing this: > > (1) Please make sure you use the std c++ iostream libraries for doing > I/O. No native calls (we end up with portability problems). If you need > something that must be ported, please add it to lib/System Sure. What