# Build CMake without curl

**URL:** https://discourse.cmake.org/t/build-cmake-without-curl/14010
**Category:** Development
**Created:** [April 28, 2025, 6:29pm UTC](https://discourse.cmake.org/t/build-cmake-without-curl/14010 "2025-04-28T18:29:07Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![Dave\_Allured](https://discourse.cmake.org/user_avatar/discourse.cmake.org/dave_allured/32/2591_2.png) [@Dave\_Allured](https://discourse.cmake.org/u/Dave_Allured)
#### Post date: [April 28, 2025, 6:29pm UTC](https://discourse.cmake.org/t/build-cmake-without-curl/14010/1 "2025-04-28T18:29:07Z")

</div>

I would like to create a reduced CMake build without curl/libcurl, and with no other internet access. This is to build CMake itself, not some other project.

From bootstrap/help, I see only system and non-system curl options, etc. Is without-curl possible? Is without-nghttp2 possible? I recognize that this will reduce FindPackage capability, which is exactly what I want.

---

<div class="post-metadata">

### Author: ![brad.king](https://discourse.cmake.org/user_avatar/discourse.cmake.org/brad.king/32/11_2.png) [@brad.king](https://discourse.cmake.org/u/brad.king)
#### Post date: [April 29, 2025, 1:45pm UTC](https://discourse.cmake.org/t/build-cmake-without-curl/14010/2 "2025-04-29T13:45:15Z")

</div>

Currently there is no option to build without linking to `libcurl`.

I’m not opposed to adding such an option. Please open an issue to propose one. We can discuss the details there. Depending on how drastic functionality reduction turns out to be then I’ll decide whether to proceed.

---

<div class="post-metadata">

### Author: ![Dave\_Allured](https://discourse.cmake.org/user_avatar/discourse.cmake.org/dave_allured/32/2591_2.png) [@Dave\_Allured](https://discourse.cmake.org/u/Dave_Allured)
#### Post date: [May 12, 2025, 11:20pm UTC](https://discourse.cmake.org/t/build-cmake-without-curl/14010/3 "2025-05-12T23:20:23Z")

</div>

See new issue [#26930](https://gitlab.kitware.com/cmake/cmake/-/issues/26930).
