Thanks for your prompt reply.
I'm sorry to bother you again, but the wish to use wxHaskell exceeds the
reluctance to steal your time you with my ignorance.
I did check the package.conf and everything is allright
(directly and using your "decribe"-trick).
The directories and libraries are there and the registration succeeded
perfectly (for path-names without spaces, so the directory "program
files" is off limits). Changing drives, directories, even library-names
did not change anything: Still GHCi complains about not being able to
load the .dll for wxc-msw2.6.4-0.10.3, (not about finding it)
I hope you or any of the other readers of this message can solve this
problem. (it is also mentioned on the fa.haskell "forum", directly after
you announcing the new wxHaskell being released.)
On Thu, 2008-04-17 at 18:54 +0100, Jeremy O'Donoghue wrote:
> Dear Jaap,
> On Thu, 17 Apr 2008 13:25:43 +0200, "Woude, J.C.S.P. van der"
> <J.C.S.P.v.d.Woude@...> said:
> > After some trouble with paths with spaces in their names I got it
> > registered
> > But...Ghci cannot find the library for wxc-msw2.... Etc (screenshot
> > included)
> > What can I do to make it work properly?
> This is probably an installation issue. This is how to start to
> Type the following at a command prompt: ghc-pkg describe wxcore
> You should get something like (less important lines for this
> investigation have been deleted):
> name: wxcore
> version: 0.10.3
> import-dirs: C:\utils\wxhaskell-0.10.3\lib\imports
> library-dirs: C:\utils\wxhaskell-0.10.3\lib
> hs-libraries: wxcore wxcore0 wxcore1 wxcore2
> extra-libraries: wxc-msw2.6.4-0.10.3
> The key parts are the lines starting 'library-dirs:', 'extra-libraries'
> and 'hs-libraries', which describe where the libraries are loaded from
> by GHC, and which libraries are loaded. The 'extra-libraries:' are DLLs
> loaded by GHCi and/or any generated executable.
> In my case, what this says is that the extra library wxc-msw2.6.4-0.10.3
> (which is actually called wxc-msw2.6.4-0.10.3
> .dll) will be loaded from library directory
> C:\utils\wxhaskell-0.10.3\lib. The first thing you need to do is to
> check that a DLL of the correct name is in the library-dirs directory
> you have selected.
> If this is not the case, the simplest thing would be to move the DLL to
> wherever GHCi is expecting it, although it would be cleaner to
> the package with the details corrected to match your installation.
> If this doesn't help to fix the problem, please feel free to mail back.
> I'd recommend including wxhaskell-users@... in the CC
> on mail as others may have come across the same problem as you.
> Good luck, and thank you for trying wxHaskell.
> Best regards
Jaap van der Woude <j.c.s.p.v.d.woude@...>