# OpenSSL issue when building SlicerCAT in Debug mode

**URL:** <https://discourse.slicer.org/t/openssl-issue-when-building-slicercat-in-debug-mode/17546>\
**Category:** Development\
**Created:** [May 10, 2021, 2:08pm UTC](https://discourse.slicer.org/t/openssl-issue-when-building-slicercat-in-debug-mode/17546 "2021-05-10T14:08:27Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![keri](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/keri/32/11618_2.png) [@keri](https://discourse.slicer.org/u/keri)\
**Post date:** [June 26, 2021, 10:56am UTC](https://discourse.slicer.org/t/openssl-issue-when-building-slicercat-in-debug-mode/17546/7 "2021-06-26T10:56:10Z")

</div>

Probably making an extension is the right decision. Thank you

> [@lassoan](#):
>
> By the way, there seems to beany options for running Python code from Julia. Have you looked into those? The simplest is probably to implement a CLI module in Julia, the same way as the Slicer MatlabBridge works.

For now I rely on [pyjulia](https://github.com/JuliaPy/pyjulia) abilities. I remember we had an [conversation on that](https://discourse.slicer.org/t/use-julia-with-slicer/16765/5). I will refer to that later when I work with julia staff more closely

---

_[View the full topic](https://discourse.slicer.org/t/openssl-issue-when-building-slicercat-in-debug-mode/17546)._