search for: humeafo

hume npx <humeafo at gmail.com> writes: > *hi,Óscar:* > * > * > *so following patch should address both the relocation problem and > uninstall tree problem, not fully tested just for discussion.* > * > * > Index: LLVMConfig.cmake.in > ===================================================...

On Jan 22, 2008, at 2:10 AM, humeafo wrote: > I am a newbie to LLVM, so I have to say sorry if I asked the > question in the wrong place. > In some cases when I generate LLVM IR from machine assembly(with > limited type information) I have to convert the pointers to I32, > after the standard mem2reg pass there st...

hume npx <humeafo at gmail.com> writes: Sorry for commenting the bug report here, but I can't loging to bugzilla right now. > Using cmake should be the right thing if you'd like to support windows, but > it seems that no enough effort on this build system, eg > http://llvm.org/bugs/show_bug.cgi...

Using cmake should be the right thing if you'd like to support windows, but it seems that no enough effort on this build system, eg http://llvm.org/bugs/show_bug.cgi?id=12157 three months passed, I'am I bit familiar with cmake, so if there tasks pending for absence of developer, I'd like to join. cmake is not perfect but it's open, but many improvements maybe merged upstream.

*hi,Óscar:* * * *so following patch should address both the relocation problem and uninstall tree problem, not fully tested just for discussion.* * * Index: LLVMConfig.cmake.in =================================================================== --- LLVMConfig.cmake.in (revision 159425) +++ LLVMConfig.cmake.in (working copy) @@ -32,8 +32,11 @@ set(LLVM_ON_WIN32 @LLVM_ON_WIN32@)

hi, Óscar: bugzilla updated, please review. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20120630/57716e17/attachment.html>

> > *hi,Óscar:* > * * > >Why? Please describe a case. > > >I need to do some futher experiment and to see whether I have been > wrong. > Since I touch this problem several months ago, so I did some test using the 3.2svn, the reason why uninstalled build 'cmake not work lies in set(LLVM_INSTALL_PREFIX @LLVM_INSTALL_PREFIX@) set(LLVM_INCLUDE_DIRS

Hi, Óscar: nice to hear some voice on this. about LLVM_TOOLS_BINARY_DIR, yes, it made the installed version work only, if you'd like the uninstalled version to work, it should be detected as you suggested. about LLVM_INSTALL_PREFIX the purpose is to make it really relocatable, eg, when installed under /lib/llvm I just later need to move the installation tree to /lusr/local/lib/llvm

On 28 Jun 2012, at 08:58, Jean-Daniel Dupas wrote: > It's a chicken and egg problems. Xcode users don't use cmake because it > generates poor Xcode projects. So what *do* XCode users do (to build llvm/clang)? Do they somehow set up XCode to build using the autoconf build system? Do they build llvm/clang outside of XCode? If the answer to either of the last two questions is

hume npx <humeafo at gmail.com> writes: > Hi, Óscar: > nice to hear some voice on this. about LLVM_TOOLS_BINARY_DIR, yes, it > made the installed version work only, if you'd like the uninstalled version > to work, it should be detected as you suggested. > > about LLVM_INSTALL_PREFIX the...

*hi,Óscar:* * * >LLVM_INSTALL_PREFIX is supposed to contain the value of > >CMAKE_INSTALL_PREFIX when you configured LLVM. Using it for setting > >other variables is just a convenience. > > Ok, I understood your point, so I'd like to develop another patch to make > it relocatable and respect the original meanings. > > >CMAKE_CURRENT_LIST_FILE can be