# \`export(EXPORT)\` does not work for windows?

**URL:** <https://discourse.cmake.org/t/export-export-does-not-work-for-windows/10109>\
**Category:** Code\
**Tags:** os:windows\
**Created:** [February 15, 2024, 7:52pm UTC](https://discourse.cmake.org/t/export-export-does-not-work-for-windows/10109 "2024-02-15T19:52:46Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![Lecris](https://discourse.cmake.org/user_avatar/discourse.cmake.org/lecris/32/3193_2.png) [@Lecris](https://discourse.cmake.org/u/Lecris)\
**Post date:** [February 15, 2024, 8:47pm UTC](https://discourse.cmake.org/t/export-export-does-not-work-for-windows/10109/5 "2024-02-15T20:47:09Z")

</div>

> [@ClausKlein](#):
>
> This is **not** quite easy!  
> see [CppCon 2019: Deep CMake For Library Authors - Crascit](https://crascit.com/2019/10/16/cppcon-2019-deep-cmake-for-library-authors/)

Not sure what you mean by that link:

- I have opened a discussion about the design of [`GenerateExportHeader`](https://discourse.cmake.org/t/generateexportheader-and-multi-compiler-support/10102)
- Most of the contents I am already implementing. Currently working on [this](https://github.com/spglib/spglib/pull/437) if more context is helpful
- The issue here is more along the line of how `export(EXPORT)` creates the targets for build so that an executable can be run. Alex’s SO approach with `TARGET_RUNTIME_DLL_DIRS` is indeed very, although it is cumbersome to implement

---

_[View the full topic](https://discourse.cmake.org/t/export-export-does-not-work-for-windows/10109)._