On 31 May 2013 06:34, harry <volderm...@hotmail.com> wrote:
> The first problem is that wxdirect installs both executables and a library -
> why is that necessary, and is there another way to do it?

Could you elaborate on this? I'm not 100% sure I follow.

Is the issue something related to the wxdirect executable not being
available in the sandbox environment?

One issue is that wxdirect is used in the build process of the wxcore Setup.hs

One thing which I think might help matters is if we had a way for the
custom Setup.hs in wxcore to depend on wxdirect.  Now one option would
be for us to just swallow wxdirect directly into wxcore, making it
part of the setup script.  There's no particular reason it has to be
run as an executable.

If not feasible, then we may need something like

Eric Kow <http://erickow.com>

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.
wxhaskell-devel mailing list

Reply via email to