# Possible to compile against a conda install ITK?

**URL:** https://discourse.itk.org/t/possible-to-compile-against-a-conda-install-itk/4319
**Category:** Engineering
**Created:** [August 6, 2021, 1:53pm UTC](https://discourse.itk.org/t/possible-to-compile-against-a-conda-install-itk/4319 "2021-08-06T13:53:05Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![imikejackson](https://discourse.itk.org/user_avatar/discourse.itk.org/imikejackson/32/35_2.png) [@imikejackson](https://discourse.itk.org/u/imikejackson)
#### Post date: [August 6, 2021, 2:24pm UTC](https://discourse.itk.org/t/possible-to-compile-against-a-conda-install-itk/4319/2 "2021-08-06T14:24:41Z")

</div>

Just to add a bit more to this I _think_ the issue is that conda-forge is not using Xcode to compile but and external LLVM/Clang toolkit. When this is used ITK will generate the following code from a macro:

```auto
# if ITK_COMPILER_IS_Clang

# include "compilers/ITK_COMPILER_INFO_Clang_CXX.h"

# else
# error Unsupported compiler
# endif

```

but then we come along and are trying to compile with Xcode and we error out. If we actually had compiled ITK with Xcode then the following code is produced:

```auto

# if ITK_COMPILER_IS_AppleClang

# include "compilers/ITK_COMPILER_INFO_AppleClang_CXX.h"

# else
# error Unsupported compiler
# endif

```

We can’t even just forcibly define ITK\_COMPILER\_IS\_Clang because that gets wiped out at the top of the itk\_compiler\_detection.h file. So thoughts on this? Should I file some sort of a bug? Can I compile the anaconda package version of ITK myself and install it into my conda environment so I can get the proper defines?

Thanks

---

_[View the full topic](https://discourse.itk.org/t/possible-to-compile-against-a-conda-install-itk/4319)._
