# aeva superbuild configure warning

**URL:** https://discourse.kitware.com/t/aeva-superbuild-configure-warning/616
**Category:** Software Process
**Created:** [March 13, 2021, 7:36pm UTC](https://discourse.kitware.com/t/aeva-superbuild-configure-warning/616 "2021-03-13T19:36:35Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![dcthomp](https://discourse.kitware.com/user_avatar/discourse.kitware.com/dcthomp/32/10_2.png) [@dcthomp](https://discourse.kitware.com/u/dcthomp)
#### Post date: [March 13, 2021, 7:36pm UTC](https://discourse.kitware.com/t/aeva-superbuild-configure-warning/616/1 "2021-03-13T19:36:35Z")

</div>

Hi all, has the `superbuild_add_project()` macro been changed by the recent bump to common-superbuild? Or maybe the CI runners are using a different CMake with a bug? There is a [new warning](https://open.cdash.org/build/7094730/configure):

```auto
Instructing ITK to accept all compilers
CMake Warning (dev) at superbuild/cmake/SuperbuildMacros.cmake:210 (message):
  Optional dependencies for itk not found: PROCESS_ENVIRONMENT,
  ITK_ACCEPT_ALL_COMPILERS, 1
Call Stack (most recent call first):
  projects/itk.cmake:8 (superbuild_add_project)
  superbuild/cmake/SuperbuildMacros.cmake:1054 (include)
  superbuild/CMakeLists.txt:159 (superbuild_process_dependencies)
This warning is for project developers. Use -Wno-dev to suppress it.

```

that has appeared recently. The relevant call is here:

```auto
superbuild_add_project(itk
  DEPENDS cxx11
  DEPENDS_OPTIONAL hdf5 vxl png zlib eigen
  ${environment}
  CMAKE_ARGS ...

```

where `${environment}` expands to `PROCESS_ENVIRONMENT ITK_ACCEPT_ALL_COMPILERS 1`. So, it looks like either `PROCESS_ENVIRONMENT` was deprecated/removed or cmake is mistakenly lumping it in with the `DEPENDS_OPTIONAL` parameters.

---

<div class="post-metadata">

### Author: ![ben.boeckel](https://discourse.kitware.com/letter_avatar_proxy/v4/letter/b/ea5d25/32.png) [@ben.boeckel](https://discourse.kitware.com/u/ben.boeckel)
#### Post date: [March 14, 2021, 6:39pm UTC](https://discourse.kitware.com/t/aeva-superbuild-configure-warning/616/2 "2021-03-14T18:39:29Z")

</div>

`common-superbuild` did change some stuff here, but why is Windows not warning? Does reordering the arguments fix it? That is, moving it to be away from the other bit. And looking into what would be the cause if that worked…see [https://gitlab.kitware.com/paraview/common-superbuild/-/merge\_requests/402](https://gitlab.kitware.com/paraview/common-superbuild/-/merge_requests/402).