Eric Kow <eric.kow@...> writes: > Is the issue something related to the wxdirect executable not being > available in the sandbox environment?
Yes - executables built in cabal-dev aren't on the path (which is different for each sandbox). If wxdirect only built an executable, I could install it outside of the sandboxes, and it would be available in the path for later use. A similar issue arises with wxc - what exactly is it building, and why is an environment variable needed to find it later? Is it creating a Haskell library, or just creating come C files for use by wxcore? ------------------------------------------------------------------------------ Get 100% visibility into Java/.NET code with AppDynamics Lite It's a free troubleshooting tool designed for production Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap2 _______________________________________________ wxhaskell-devel mailing list wxhaskell-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wxhaskell-devel
