# GSoC '25: stdlib filesystem

**URL:** <https://fortran-lang.discourse.group/t/gsoc-25-stdlib-filesystem/9798>\
**Category:** GSoC-2025\
**Created:** [May 26, 2025, 5:02pm UTC](https://fortran-lang.discourse.group/t/gsoc-25-stdlib-filesystem/9798 "2025-05-26T17:02:23Z")\
**Posts on this page:** 1\
**Showing post:** 18

<div class="post-metadata">

**Author:** ![davidpfister](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/davidpfister/32/3949_2.png) [@davidpfister](https://fortran-lang.discourse.group/u/davidpfister)\
**Post date:** [June 19, 2025, 12:30pm UTC](https://fortran-lang.discourse.group/t/gsoc-25-stdlib-filesystem/9798/18 "2025-06-19T12:30:41Z")

</div>

> [@hkvzjal](#):
>
> compile-time constant

Just another thing that came to my mind. AFAIK unlike ifort/ifx, gfortran does not define macros like `_WIN32` depending on the platform you compile on. So, if you use fpm as a build system you have to supply it in the toml file:

```toml
[preprocess]
cpp.suffixes = ["F90", "f90"]
cpp.macros = ["_WIN32"]

```

which makes the fpm.toml platform-dependent, unless you use [profiles](https://fortran-lang.discourse.group/t/fpm-platform-specific-instructions-to-linker-on-fpm-toml/7296/13) as discussed here.

---

_[View the full topic](https://fortran-lang.discourse.group/t/gsoc-25-stdlib-filesystem/9798)._