You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When building wxHaskell (after checking out the wx sources) with cabal-dev by:
cabal-dev install ./wxdirect ./wxc ./wxcore ./wx
the built wxdirect is not subsequently used, but instead the global one is used, even after hiding the globally installed one and moving its executable. It is (of course) possible to work around it by globally changing the shell search path, but this is not a flexible sandboxing solution.
The text was updated successfully, but these errors were encountered:
When building wxHaskell (after checking out the wx sources) with cabal-dev by:
cabal-dev install ./wxdirect ./wxc ./wxcore ./wx
the built wxdirect is not subsequently used, but instead the global one is used, even after hiding the globally installed one and moving its executable. It is (of course) possible to work around it by globally changing the shell search path, but this is not a flexible sandboxing solution.
The text was updated successfully, but these errors were encountered: