search for: cmake_current_list_dir

...FIX and CMAKE_MODULE_PATH) does not need such corrections, as the former is precisely the *intended* location for an installed build and the later needs modification only for uninstalled builds, as the comment above the IF hints. Apart from that, your patch seems wrong for me because you are using CMAKE_CURRENT_LIST_DIR. Such method only gives the desired result for uninstalled, in-source builds. > I'am I bit > familiar with cmake, so if there tasks pending for absence of developer, > I'd like to join. Chandler is doing a great job at maintaining the CMake scripts, but I'm sure he will welco...

...ed. 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 without re-run cmake and the time-boring build/install process, and this is especially convinient on Windows. Use CMAKE_CURRENT_LIST_DIR while not the absolute predefined LLVM_INSTALL_PREFIX is just to give the freedom to this, if just installed and not moved, this will work identical to the value original absolute LLVM_INSTALL_PREFIX points. CMAKE_MODULE_PATH should be corrected for installed version, it's still points to the...

.../llvm without re-run cmake and the > time-boring build/install process, and this is especially convinient on > Windows. 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. > Use CMAKE_CURRENT_LIST_DIR while not the absolute predefined > LLVM_INSTALL_PREFIX is just to give the freedom to this, if just installed and > not moved, this will work identical to the value original absolute > LLVM_INSTALL_PREFIX points. I've never heard CMAKE_CURRENT_LIST_DIR until now. In fact, it was intr...

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

...P_INCLUDE_DIRS ${SPEEXDSP_INCLUDE_DIR}) +endif (SPEEXDSP_FOUND) + +mark_as_advanced(SPEEXDSP_INCLUDE_DIR SPEEXDSP_LIBRARY) diff --git a/cmake/SpeexConfig.cmake b/cmake/SpeexConfig.cmake new file mode 100644 index 0000000..dbc99e8 --- /dev/null +++ b/cmake/SpeexConfig.cmake @@ -0,0 +1 @@ +include (${CMAKE_CURRENT_LIST_DIR}/SpeexTargets.cmake) diff --git a/cmake/TestVarArrays.cmake b/cmake/TestVarArrays.cmake new file mode 100644 index 0000000..11f413f --- /dev/null +++ b/cmake/TestVarArrays.cmake @@ -0,0 +1,22 @@ +include(CheckCSourceCompiles) + +macro(TEST_VARARRAYS VARIABLE) + if(NOT DEFINED ${VARIABLE}) + check_...