search for: makefileguid

Hi, http://llvm.org/docs/MakefileGuide.html says Override Variables ============== Override variables can be used to override the default values provided by the LLVM makefile system. These variables can be set in several ways: In the environment (e.g. setenv, export) -- not recommended. On the make command line -- recommended. On the...

...that is the problem? Aparna On Mon, Apr 13, 2009 at 5:16 PM, Milos Puzovic <milos.puzovic at gmail.com>wrote: > In order to generate shared libraries you need to have SHARED_LIBRARY > and LOADABLE_MODULE defined in the Makefile. See here for more > details: http://llvm.org/docs/MakefileGuide.html#libraries > > On 13 Apr 2009, at 20:46, aparna kotha wrote: > > > I am trying to run the LLVM hello world pass. I observe that in the > > OUPUT_DIR/lib the LLVMHello.a and LLVMHello.la libraries are > > generated. But I am confused as to how to generate the .so libr...

...tive names are concatenated in some cases. I'd like to see TOOL_NAME instead of TOOLNAME and LIBRARY_NAME instead of LIBRARYNAME. Its easier for *me* to read, but I'd like some feedback on this one as its as "gratuitous" change. 7. The documentation in MakefileGuide.html is lacking a tutorial on how to use the LLVM Makefile system for projects (as opposed to LLVM itself). I think its time to add one. There are things in the configure.ac file that are needed to support the makefile system. Those need to be documented as well....

In order to generate shared libraries you need to have SHARED_LIBRARY and LOADABLE_MODULE defined in the Makefile. See here for more details: http://llvm.org/docs/MakefileGuide.html#libraries On 13 Apr 2009, at 20:46, aparna kotha wrote: > I am trying to run the LLVM hello world pass. I observe that in the > OUPUT_DIR/lib the LLVMHello.a and LLVMHello.la libraries are > generated. But I am confused as to how to generate the .so library > file from her...

...in some cases. I'd like to > see TOOL_NAME instead of TOOLNAME and LIBRARY_NAME instead of > LIBRARYNAME. Its easier for *me* to read, but I'd like some > feedback on this one as its as "gratuitous" change. Likewise. > 7. The documentation in MakefileGuide.html is lacking a tutorial on > how to use the LLVM Makefile system for projects (as opposed to > LLVM itself). I think its time to add one. There are things in > the configure.ac file that are needed to support the makefile > system. Those need to be docum...

I am trying to run the LLVM hello world pass. I observe that in the OUPUT_DIR/lib the LLVMHello.a and LLVMHello.la libraries are generated. But I am confused as to how to generate the .so library file from here. I am kinda new to compilers and hence the question I know is basic , but couldnt figure the answer out myself. Thanks a lot for your help. Regards -- -- Aparna Kotha Research

...gt; > Aparna > > On Mon, Apr 13, 2009 at 5:16 PM, Milos Puzovic > <milos.puzovic at gmail.com> wrote: > In order to generate shared libraries you need to have SHARED_LIBRARY > and LOADABLE_MODULE defined in the Makefile. See here for more > details: http://llvm.org/docs/MakefileGuide.html#libraries > > On 13 Apr 2009, at 20:46, aparna kotha wrote: > > > I am trying to run the LLVM hello world pass. I observe that in the > > OUPUT_DIR/lib the LLVMHello.a and LLVMHello.la libraries are > > generated. But I am confused as to how to generate the .so libr...

...isterPass(const llvm::PassInfo&): > Assertion `Inserted && "Pass registered multiple times!"' failed. > Aborted > > I "fixed" this by replacing the LLVMLIBS line in the Makefile with > LINK_COMPONENTS according to this tutorial http://llvm.org/docs/MakefileGuide.html#LoadableModules > and was able to build/run my pass properly. > > -shu > > On Jul 17, 11:48am, Chuck Zhao <cz... at eecg.toronto.edu> wrote: > >> While learning to write LLVM passes and following the precise >> instructions underhttp://llvm.org/docs/Writ...

I suspect my change adding --enable-shared broke you, since that configure option didn't exist before last week (r97119). SHARED_LIBRARY is not one of the variables you're supposed to be able to set on make's command line (http://llvm.org/docs/MakefileGuide.html#variables). What are you using it for? What happens if you remove it? On Tue, Mar 2, 2010 at 1:35 PM, James Williams <junk at giantblob.com> wrote: > Hi, > > Until recently I've been building LLVM with SHARED_LIBRARY=1. However, sith > current svn, build now fails with...

Hi Mike, Sounds like an interesting project. Here's some ideas for you on the LLVM Makefile System. If you haven't, I *strongly* suggest you read the makefile and project documentation (docs/MakefileGuide.html and docs/Projects.html). There is much information there that you need to understand. LLVM is set up so that a single directory builds a single result. Since your source code is fairly large, I would suggest that you allow LLVM to recurse into subdirectories and build archive libraries f...

...>::PassRegistrar::RegisterPass(const llvm::PassInfo&): Assertion `Inserted && "Pass registered multiple times!"' failed. Aborted I "fixed" this by replacing the LLVMLIBS line in the Makefile with LINK_COMPONENTS according to this tutorial http://llvm.org/docs/MakefileGuide.html#LoadableModules and was able to build/run my pass properly. -shu On Jul 17, 11:48 am, Chuck Zhao <cz... at eecg.toronto.edu> wrote: > While learning to write LLVM passes and following the precise > instructions underhttp://llvm.org/docs/WritingAnLLVMPass.html, > <http://ll...

...workout how to do > non-debug builds as that would speed up the linking, which is particularly > slow. Yeah, cygwin's a bit of a pig. To do a release build, just do: make ENABLE_RELEASE=1 that's all there is to it. You might want to take a gander at http://llvm.cs.uiuc.edu/docs/MakefileGuide.html > > I don't want to be a slave driver but any thoughts on the groff error ???:) Nope, because I haven't seen it on the list. Can you repost? Reid -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature...

Hi, Until recently I've been building LLVM with SHARED_LIBRARY=1. However, sith current svn, build now fails with unresolved symbols building opt. I've done a clean checkout, configure and make so it's not down to any local changes I've made. I'm building with: ./configure --enable-assertions \ --enable-expensive-checks=no \ --enable-pic \ --enable-targets=host-only \

...tenated in some cases. I'd like to > see TOOL_NAME instead of TOOLNAME and LIBRARY_NAME instead of > LIBRARYNAME. Its easier for *me* to read, but I'd like some > feedback on this one as its as "gratuitous" change. > 7. The documentation in MakefileGuide.html is lacking a tutorial on > how to use the LLVM Makefile system for projects (as opposed to > LLVM itself). I think its time to add one. There are things in > the configure.ac file that are needed to support the makefile > system. Those need to be d...

First I'd like to let you know I've started working on porting gcjx to llvm. Some other intrested people may help but I've just started the project. My first question is I'm porting gcjx over to use the llvm build system I've successfully created a number of libraries but gcjx uses a number of sub directories for its source and I'd like the .o files for all of them to

While learning to write LLVM passes and following the precise instructions under http://llvm.org/docs/WritingAnLLVMPass.html, <http://llvm.org/docs/WritingAnLLVMPass.html> I got this error when loading the hello pass to run the test program: opt -load ./Release/lib/Hello.so -hello < test/test.bc > /dev/null Error opening './Release/lib/Hello.so': ./Release/lib/Hello.so:

...tenated in some cases. I'd like to > see TOOL_NAME instead of TOOLNAME and LIBRARY_NAME instead of > LIBRARYNAME. Its easier for *me* to read, but I'd like some > feedback on this one as its as "gratuitous" change. > 7. The documentation in MakefileGuide.html is lacking a tutorial on > how to use the LLVM Makefile system for projects (as opposed to > LLVM itself). I think its time to add one. There are things in > the configure.ac file that are needed to support the makefile > system. Those need to be d...

...s. I'd like to > > see TOOL_NAME instead of TOOLNAME and LIBRARY_NAME instead of > > LIBRARYNAME. Its easier for *me* to read, but I'd like some > > feedback on this one as its as "gratuitous" change. > > 7. The documentation in MakefileGuide.html is lacking a tutorial on > > how to use the LLVM Makefile system for projects (as opposed to > > LLVM itself). I think its time to add one. There are things in > > the configure.ac file that are needed to support the makefile > > system...

...the following line: > > #LLVMLIBS = LLVMCore.a LLVMSystem.a LLVMSupport.a > > I guess the tutorial needs some update, as with release 2.5 things might > have changed a bit. Yea, I commented out LLVMLIBS at first as well before I came across the documentation at http://llvm.org/docs/MakefileGuide.html#LoadableModules . I think LLVMLIBS is supposed to be ignored when compiling a shared library but somehow isn't. I'm new to LLVM so I could be way off. Best of luck! -shu

The LLVM Makefile Guide is available for review/commentary/use. New developers are advised to read it if they are uncertain how the makefile system workse. http://llvm.cs.uiuc.edu/docs/MakefileGuide.html Reid