# Missing Relocatability of Tulip

**URL:** <https://discourse.julialang.org/t/missing-relocatability-of-tulip/94886>\
**Category:** General Usage\
**Tags:** package-compiler\
**Created:** [February 19, 2023, 5:16pm UTC](https://discourse.julialang.org/t/missing-relocatability-of-tulip/94886 "2023-02-19T17:16:16Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![ellocco](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ellocco/32/31331_2.png) [@ellocco](https://discourse.julialang.org/u/ellocco)\
**Post date:** [February 22, 2023, 11:03am UTC](https://discourse.julialang.org/t/missing-relocatability-of-tulip/94886/9 "2023-02-22T11:03:46Z")

</div>

@fredrikekre & @mkitti  
First of all thank you for your help! 🙂  
It was haphazardly that I included the function `Tulip. __init__ ()` in my minimal example  
and it was not obvious to me that this was already the part of the `Tulip`-code that causes the trouble.

Ok, I understand the root cause of my problem. Consistently, I have added my local clone of `Tulip.jl` as development package to the primary environment, but this does not cure the problem ☹  
During package compilation the standard `Tulip.jl` is taken to build the library “sys.dll”.  
Is there a way to specify the local `Tulip.jl`-package to be utilized during package compilation?

---

_[View the full topic](https://discourse.julialang.org/t/missing-relocatability-of-tulip/94886)._