# ModelingToolkit takes forever to precompile on Windows 11

**URL:** <https://discourse.julialang.org/t/modelingtoolkit-takes-forever-to-precompile-on-windows-11/114492>\
**Category:** Package Management\
**Created:** [May 21, 2024, 7:08am UTC](https://discourse.julialang.org/t/modelingtoolkit-takes-forever-to-precompile-on-windows-11/114492 "2024-05-21T07:08:28Z")\
**Posts on this page:** 1\
**Showing post:** 91

<div class="post-metadata">

**Author:** ![mkitti](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/mkitti/32/12459_2.png) [@mkitti](https://discourse.julialang.org/u/mkitti)\
**Post date:** [May 25, 2024, 4:53pm UTC](https://discourse.julialang.org/t/modelingtoolkit-takes-forever-to-precompile-on-windows-11/114492/91 "2024-05-25T16:53:42Z")

</div>

Let’s discuss this `Pkg` usage in the other thread, please.

> [@Pkg & activation](https://discourse.julialang.org/t/pkg-activation/114723/3):
>
> OK – Pkg.status() tells me that I’m in the local directory!! C:\Users\Bernt\OneDrive\...\Notebooks\Project.toml` (empty project) This is so, even though I did not do Pkg.activate(".")!! So this implies that (at least when I run Jupyter Notebooks in VSCode), command Pkg.activate(".") is not needed – it will always first search for the \*.toml files locally! If there is no \*.toml files locally, it will go to the global environment and use the \*.toml files there. This also implies that I can no…

---

_[View the full topic](https://discourse.julialang.org/t/modelingtoolkit-takes-forever-to-precompile-on-windows-11/114492)._