# \`\`import std\`\` doesn't work on windows

**URL:** https://discourse.cmake.org/t/import-std-doesnt-work-on-windows/14268
**Category:** Usage
**Tags:** os:windows, gen:ninja
**Created:** [June 20, 2025, 8:57am UTC](https://discourse.cmake.org/t/import-std-doesnt-work-on-windows/14268 "2025-06-20T08:57:25Z")
**Posts on this page:** 1
**Showing post:** 29

<div class="post-metadata">

### Author: ![ClausKlein](https://discourse.cmake.org/user_avatar/discourse.cmake.org/clausklein/32/352_2.png) [@ClausKlein](https://discourse.cmake.org/u/ClausKlein)
#### Post date: [July 9, 2025, 4:28pm UTC](https://discourse.cmake.org/t/import-std-doesnt-work-on-windows/14268/29 "2025-07-09T16:28:48Z")

</div>

> [@No SOURCES given to target: \_\_CMAKE\_\_CXX26 on ubuntu 25.04](https://discourse.cmake.org/t/no-sources-given-to-target-cmake-cxx26-on-ubuntu-25-04/14240/17):
>
> Whoever packaged the compiler. If the packagers need support for their use case from the compiler, ex, they need to be able to tell the compiler “I’m going to put these files here” to make -print-file-name work, then it is on the packagers to communicate that the various compiler upstreams. The compiler upstreams can decide on a case-by-case basis if they want to support the packagers conventions, or if it is on the packagers to align themselves with the compiler’s expectations. CMake’s invol…

---

_[View the full topic](https://discourse.cmake.org/t/import-std-doesnt-work-on-windows/14268)._