search for: cmakes

On 6 July 2015 at 10:34, Ben Pope <benpope81 at gmail.com> wrote: > On 7 July 2015 at 01:12, Dan Liew <dan at su-root.co.uk> wrote: >> >> >> @Ben Pope: Your uploaded binary tarball is the odd one out. Any idea >> as to why the CMake files are missing and why the root directory name >> inside the tarball is not consistent with the uploaded tarballs for

The cmake files generated when building LLVM (including LLVMConfig.cmake) are to support cmake's find_package() [1] function. In the build dir the generated files are placed in <build-dir>/share/llvm/cmake. After install, in <prefix>/lib/llvm/share/llvm/cmake. CMake is not able to find them without a hint. CMake searches these paths on Unix: - <prefix>/lib/llvm/cmake -

Hi Ben, Thanks for taking the time to look at this. >> It's not necessary for CMake to be installed when building with the >> Autoconf/Makefile build system. If you look in the build directory >> after a build has been performed you should see in cmake/modules >> >> ``` >> LLVMBuildExports.cmake LLVMConfig.cmake LLVMConfigVersion.cmake >>

Hi all, CMake seems to have broken in the last few days - or is it just me? tcare:llvm-release tcare$ make -j4 -- Target triple: x86_64-apple-darwin10.5.0 -- Native target architecture is X86 -- Threads enabled. -- Building with -fPIC -- Targeting X86 CMake Error at cmake/modules/LLVMConfig.cmake:90 (message): Library LLVMARMAsmParser not found in list of llvm libraries. Call Stack (most

> > Replicating ExternalProject would be a lot of work... > One approach commonly used with CMake modules that change frequently upstream is for the project to keep a local copy and have a check in place to use CMake's version if new enough. For instance, in llvm's source tree: cmake/modules/ExternalProject.cmake: if(CMAKE_VERSION VERSION_LESS "3.5.1")

It came up on another thread that our current minimum required CMake version 2.8.8, has some bugs that cause issues when building with MSVC + Ninja, and one potential solution was to raise the minimum required version of CMake. CMake 3.0 is now 6 months old and CMake 3.1 has been released. I would like to propose moving our minimum required CMake version to 3.0. I’ve attached patches to enforce

At the LLVM Developer Meeting on October 23rd we held a CMake roundtable. One of the items we discussed was adopting a more regular timeline for CMake upgrades. During the roundtable there was overwhelming support for upgrading CMake, and support for treating CMake differently than how we treat upgrading host compilers. Historically we've taken into account recent versions of Visual Studio,

On 24.02.2015 17:45, Tobias Grosser wrote: > On 09.02.2015 20:12, Chris Bieneman wrote: >> It came up on another thread that our current minimum required CMake >> version 2.8.8, has some bugs that cause issues when building with MSVC >> + Ninja, and one potential solution was to raise the minimum required >> version of CMake. >> >> CMake 3.0 is now 6 months

...ease that is a little bit older. > > > > Ok, how about the following policy: > > > > After every release branch, we bump the CMake version to whatever version of CMake is 12 months old. > > > > This is simple, straightforward, and it gives a full year of old CMakes being supported. If we did this right now, this would take us to CMake 3.14.0, released around March 14th, 2019 (https://github.com/Kitware/CMake/releases/tag/v3.14.0 <https://github.com/Kitware/CMake/releases/tag/v3.14.0>). I believe the expectation should be that recent CMakes are upgraded...

> On Feb 24, 2015, at 8:45 AM, Tobias Grosser <tobias at grosser.es> wrote: > > On 09.02.2015 20:12, Chris Bieneman wrote: >> It came up on another thread that our current minimum required CMake version 2.8.8, has some bugs that cause issues when building with MSVC + Ninja, and one potential solution was to raise the minimum required version of CMake. >> >> CMake

Hello, I work on CMake upstream. I'd like to find out in what ways CMake upstream does not fit the needs of llvm/clang, and then fill those gaps. The recent update of the minimum version to CMake 2.8.8 is a good start. Before being able to assess what is missing, it should be ensured that the current codebase is as modern as the minimum version allows, and it needs to be cleaned up. 1)

So, we’ve had this conversation a few times, and I wanted to coalate a status report for all the interested parties. Here's the outstanding work and my (not necissarily correct) view of the status and importance of each one: * Bug 12157 - llvmconfig.cmake.in make cmake installations not relocatable - There are patches on the bug that we should review, test, and land * Bug 14109 - CMake

...really new to settle on a release that is a little bit older. > > Ok, how about the following policy: > > After every release branch, we bump the CMake version to whatever version of CMake is 12 months old. > > This is simple, straightforward, and it gives a full year of old CMakes being supported. If we did this right now, this would take us to CMake 3.14.0, released around March 14th, 2019 (https://github.com/Kitware/CMake/releases/tag/v3.14.0). I believe the expectation should be that recent CMakes are upgraded using some package manager or download from the site -- we can...

Hi dear list, I tried to build llvm+clang on an OpenSuse BuildServer for ARM. The build was carried out with CMake 2.8.11. In the installation step I got the following error: > [26815s] -- Installing: /home/abuild/rpmbuild/BUILDROOT/llvm-3.4.99-336.1.arm/usr/lib/libLLVMSupport.so > [26815s] CMake Error at lib/Support/cmake_install.cmake:45 (FILE): > [26815s] file RPATH_CHANGE could

hi, i am wondering if this link is still updated? http://www.llvm.org/docs/CMake.html#developing-llvm-pass-out-of-source i follow the instruction from the link, and create in my ~/test/ directory the CMakeLists.txt with following content: $cat test/CMakeLists.txt find_package(LLVM) # Define add_llvm_* macro's. include(AddLLVM) add_definitions(${LLVM_DEFINITIONS})

...nux distro Y ships that version. The reason for wanting to upgrade is evidently the use of new features that would simplify and clean up the build system quite a bit. I can't speak for other projects, but libc++ and libc++abi are suffering a lot from the lack of e.g. compile_features in recent CMakes. > > Anybody who has ever needed to build something on some ancient version of CentOS because work refuses to upgrade will thank you. Honestly, CMake is so easy to install that I have a hard time relating: curl -L https://github.com/Kitware/CMake/releases/download/v3.17.0/cmake-3.17.0-...

...ake/SpeexConfig.cmake create mode 100644 cmake/TestVarArrays.cmake create mode 100644 config.h.cmake diff --git a/.gitignore b/.gitignore index 7c30999..99a35e5 100644 --- a/.gitignore +++ b/.gitignore @@ -43,3 +43,13 @@ src/speexdec src/speexenc stamp-* patches + +CMakeCache.txt +CMakeFiles +CMakeScripts +Testing +Makefile +cmake_install.cmake +install_manifest.txt +compile_commands.json +CTestTestfile.cmake diff --git a/.travis.yml b/.travis.yml index ff85bc3..2bc028b 100644 --- a/.travis.yml +++ b/.travis.yml @@ -1,11 +1,25 @@ language: c +sudo: false +dist: trusty +addons: + apt: + pa...

> On Feb 24, 2015, at 11:13 AM, Mehdi Amini <mehdi.amini at apple.com> wrote: > >> >> On Feb 24, 2015, at 9:33 AM, Chris Bieneman <beanz at apple.com> wrote: >> >>> >>> On Feb 24, 2015, at 8:45 AM, Tobias Grosser <tobias at grosser.es> wrote: >>> >>> On 09.02.2015 20:12, Chris Bieneman wrote: >>>> It

Hi all, Time for another update on the status of the CMake build system. Completed: * Bug 18496 - [cmake] .S assembly files not compiled by cmake in libclang_rt.ARCH * Bug 22725 - lldb build with cmake fails with "Program error: Invalid parameters entered, -h for help. " * Update GettingStarted to prefer CMake Still Outstanding: * Bug 14109 - CMake build for compiler-rt should use

My list of useful features in newer CMake versions, that I would like to see used: CMake 2.8.10 * INTERFACE_LIBRARY (we already use this by hacking around the CMake version) CMake 2.8.11 * Targets can now have dependencies that are arbitrary files instead of just link dependencies (http://community.kde.org/Frameworks/Epics/CMake_target_usage_requirements