[cmake-developers] Revitalize --find-package mode?

Hi! I’m currently struggling with trying to build GNOME projects using meson, but depending on CMake-built libraries, either in the wild or inside a package manager. I have managed to uncover that the way Meson is trying to invoke CMake

Re: [cmake-developers] cmake-file-api and CTest

for this summer project, but it seems that’s the first step. Cheers, Máté Feladó: Kyle Edwards Elküldve: 2019. július 8., hétfő 15:56 Címzett: Nagy-Egri Máté Ferenc; CMake fejlesztők Tárgy: Re: [cmake-developers] cmake-file-api and CTest On Sun, 2019-07-07 at 09:04 +, Nagy-Egri Máté Ferenc via cmake

Re: [cmake-developers] cmake-file-api and CTest

Tárgy: Re: [cmake-developers] cmake-file-api and CTest On Sun, 2019-07-07 at 09:04 +, Nagy-Egri Máté Ferenc via cmake- developers wrote: > Hi! > > I am trying to cook a CTest back-end to the Test Explorer UI > extension for VS Code as a summer project and I thought of using the

[cmake-developers] cmake-file-api and CTest

Hi! I am trying to cook a CTest back-end to the Test Explorer UI extension for VS Code as a summer project and I thought of using the new cmake-file-api for it. The docs however are understandably scarce and I could not muster how to obtain tests and not targets. Is it possible with this

[cmake-developers] Custom script invocation from imported target

Hi! I am trying to improve the developer experience of SYCL users for both those using triSYCL and ComputeCpp alike. (TL;DR: SYCL is CUDA of OpenCL, triSYCL being a non-conforming playground implementation built atop OpenMP, while ComputeCpp is the first (and only) conforming GPU-accelerated

Re: [cmake-developers] C++ IDE

ttp://www.jcelerier.name On Fri, Aug 18, 2017 at 12:04 PM, Nagy-Egri Máté Ferenc via cmake-developers <cmake-developers@cmake.org> wrote: Impressed with VSCode?? If I saw this post anywhere else than the CMake mailing list, I’d understand, but VSCode with CMake is horrible. The fact that in 201

Re: [cmake-developers] C++ IDE

Impressed with VSCode?? If I saw this post anywhere else than the CMake mailing list, I’d understand, but VSCode with CMake is horrible. The fact that in 2017 I have to set include directories, compiler definitions and target paths manually to have proper IntelliSense (Code navigation and

Re: [cmake-developers] CMake PCH Prototype

I just wanted to note that big thumbs up for both the effort and the design. Eagerly awaiting the time I can use it in my projects. As soon as it lands, I’ll imbue the triSYCL CMake scripts to make use of it. Sidenote/question: Is it possible for multiple targets to share the same PCH? This

Re: [cmake-developers] Proposed Feature: automatic search prefixes forfind modules

I think it’s a good idea. Having PackageConfig.cmake files for all projects would be better, but unfortunately, many projects don’t support CMake to that extent (or to any extent to be precise). I still consume SFML like this, even though the project itself builds with CMake, so they could’ve

Re: [cmake-developers] Splitting CMakeLib

Hi Egor! This thread very much resembles my suggestion from two years ago, when I proposed there should be an intermediate representation of the CMake scripts so generators can be implemented against a stable IR as opposed to bare C++ constructs. (Google „CMake IR”) My main motive too was to

[cmake-developers] CMake IR

Dear CMake devs/users, I wanted to ask your opinion on something that has been troubling me since… well, ever since I started using CMake. I have not found a single person alive who would have said: “The script language of CMake is nice, intuitive and productive. Authoring scripts is easy,