search for: llvm_tools_binary_dir

...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?id=12157 three months passed, There is indeed a problem with the value assigned to LLVM_TOOLS_BINARY_DIR in LLVMConfig.cmake.in because such value is valid for an uninstalled build, but not for an installed one, because on installing, LLVM_TOOLS_BINARY_DIR is not upated. As both build types should be usable for clients, the solution is to detect in LLVMConfig.cmake if it is being processed on an insta...

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.

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

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

...sure if this a bug or an artifact of using Visual Studio but some of the paths specified in LLVMConfig.cmake are not real paths because they contain ``$(Configuration)``. ``` set(LLVM_BUILD_LIBRARY_DIR "C:/Users/alexander.APRELEV/Documents/halide/llvm-build/$(Configuration)/lib") ... set(LLVM_TOOLS_BINARY_DIR "C:/Users/alexander.APRELEV/Documents/halide/llvm-build/$(Configuration)/bin") ``` The problem is that I was trying to check if ${LLVM_TOOLS_BINARY_DIR}/clang${CMAKE_EXECUTABLE_SUFFIX} exists at configure time (which works on OSX and Linux) but this fails when using Visual Studio becau...

On 06/18/2015 06:46 PM, Dan Liew wrote: >> The issue is the that that generated LLVMExports.cmake file has this in it >> INTERFACE_LINK_LIBRARIES "LLVMObject;LLVMSupport;C:\Program Files (x86)\Microsoft Visual Studio 14.0\DIA SDK\lib\diaguids.lib" > > Hmm actually this might be a bug in the > ``/lib/DebugInfo/PDB/CMakeLists.txt`` file. CC'ing Zach Turner seeing

*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@)

...gt; -set(LLVM_LIBRARY_DIRS ${LLVM_INSTALL_PREFIX}/lib) > + > +get_filename_component(LLVM_CURRENT_LIST_DIR CMAKE_CURRENT_LIST_FILE PATH) > +set(LLVM_INCLUDE_DIRS ${LLVM_CURRENT_LIST_DIR}/../../../include) > +set(LLVM_LIBRARY_DIRS ${LLVM_CURRENT_LIST_DIR}/../../../lib) > + What about LLVM_TOOLS_BINARY_DIR ? Have you checked that CMAKE_CURRENT_LIST_FILE is available for CMake 2.8.0 ? > set(LLVM_DEFINITIONS "-D__STDC_LIMIT_MACROS" "-D__STDC_CONSTANT_MACROS") > > # We try to include using the current setting of CMAKE_MODULE_PATH, > @@ -47,5 +50,7 @@ > ${CMAKE...

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

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 purpose is to make it really relocatable, > eg, when installed under /lib/llvm I just later need to move t...