# CMAKE\_MAKE\_PROGRAM 3.19 issue?

**URL:** https://discourse.cmake.org/t/cmake-make-program-3-19-issue/2213
**Category:** Usage
**Tags:** gen:ninja
**Created:** [November 20, 2020, 10:25pm UTC](https://discourse.cmake.org/t/cmake-make-program-3-19-issue/2213 "2020-11-20T22:25:15Z")
**Posts on this page:** 1
**Showing post:** 17

<div class="post-metadata">

### Author: ![YMba9g8j9CJp0wLoQf5y](https://discourse.cmake.org/user_avatar/discourse.cmake.org/ymba9g8j9cjp0wloqf5y/32/1244_2.png) [@YMba9g8j9CJp0wLoQf5y](https://discourse.cmake.org/u/YMba9g8j9CJp0wLoQf5y)
#### Post date: [January 12, 2021, 8:54pm UTC](https://discourse.cmake.org/t/cmake-make-program-3-19-issue/2213/17 "2021-01-12T20:54:14Z")

</div>

I’ve created the sample project and reproducible example:

> [@FetchContent / CMAKE\_MAKE\_PROGRAM issue](https://discourse.cmake.org/t/fetchcontent-cmake-make-program-issue/2522):
>
> I’ve created a GitHub repo to show a minimal reproducible example as requested by @craig.scott in the other thread: Basically the intent is to have a way to be in control of the version of Ninja my developers on my team use. And ideally not have them have to download/set Ninja themselves. I want the experience as seemless as possible. Currently this type of workflow works fine since we just have our cmake modules inside our project. The problem arises in separating the cmake code in it’s …

---

_[View the full topic](https://discourse.cmake.org/t/cmake-make-program-3-19-issue/2213)._