Henk-Jan van Tuyl hjgtuyl@... writes:
Have you tried placing your DLLs in a directory without spaces in the path?
Yes. I should probably give up on WxHaskell until someone who knows what
they're doing (i.e. not me) takes up maintenance for the Windows port. Even
if I eventually get it to work
Henk-Jan van Tuyl hjgtuyl@... writes:
I have a 32 bit system, the DLLs are working, so the DLLs must be 32 bit.
Since the HP for Windows is only 32 bit, that must be right for me as well?
--
This SF.net email is
On Tue, 18 Jun 2013 09:03:04 +0200, harry volderm...@hotmail.com wrote:
Henk-Jan van Tuyl hjgtuyl@... writes:
I have a 32 bit system, the DLLs are working, so the DLLs must be 32
bit.
Since the HP for Windows is only 32 bit, that must be right for me as
well?
Have you tried placing
wxdirect does not support conditional compilation, I'm afraid. It's a large
part of the reason why there are separate branches for wxWidgets 2.8 and
2.9.
Adding a real C preprocessor to wxdirect is a pretty large task.
The usual approach we have used in the past is:
* Define function in the
Henk-Jan van Tuyl hjgtuyl@... writes:
Searching for uuid: %1 is not a valid Win32 application leads to the
causes:
- space in the path to the DLL
- mixup of 32/64 bit
Your google is a lot better than mine, I couldn't find anything!
Is the one you uploaded 32 bit? Maybe that's the
On Mon, 17 Jun 2013 20:03:28 +0200, harry volderm...@hotmail.com wrote:
Henk-Jan van Tuyl hjgtuyl@... writes:
Searching for uuid: %1 is not a valid Win32 application leads to the
causes:
- space in the path to the DLL
- mixup of 32/64 bit
Your google is a lot better than mine, I
Charles the Hawk charlesthehawk@... writes:
I can compile wx now, but linking it into an application gives
Loading package wxc-0.90.0.4 ... ghc.exe: uuid: The specified module could
not be found.
command line: can't load .so/.DLL for: uuid.dll (addDLL: could not load DLL)
Any idea what it
Hmm, apparently somebody's been down a similar path
http://www.haskell.org/haskellwiki/WxHaskell/Windows
(search uuid.dll - not sure where it comes from though)
On 16 June 2013 15:01, harry volderm...@hotmail.com wrote:
Charles the Hawk charlesthehawk@... writes:
I can compile wx now, but
Eric Kow eric.kow@... writes:
Hmm, apparently somebody's been down a similar path
http://www.haskell.org/haskellwiki/WxHaskell/Windows
(search uuid.dll - not sure where it comes from though)
I tried that, uuid.dll isn't there. Google isn't much help either.
harry voldermort@... writes:
I tried that, uuid.dll isn't there. Google isn't much help either.
If anyone's got wxhaskell working on Windows, could they upload the dll
somewhere pretty please?
--
This SF.net email is
On 06/10/2013 10:21 AM, harry wrote:
Charles the Hawk charlesthehawk@... writes:
At first I installed the 90.0.1 from the older site. I had to modify
wxdirect to do an import Foreign.C.Types to get rid of the arg type
errors and change the pointer assignment in eljpen.cpp that others have
I used this repo: https://github.com/atzedijkstra/wxHaskell
Using wxWidgets 2.9.4, and GHC 7.6.3 the only change needed is in
wxc/src/cpp/eljdc.cpp line 214 (the #if wxCHECK_VERSION(2,9,5) should be
commented out - or at least had to be on my setup.
Then a simple: cabal install ./wxdirect ./wxc
Blair Archibald mrblairarchibald@... writes:
I used this repo: https://github.com/atzedijkstra/wxHaskell
Using wxWidgets 2.9.4, and GHC 7.6.3 the only change needed is in
wxc/src/cpp/eljdc.cpp line 214 (the #if wxCHECK_VERSION(2,9,5) should be
commented out - or at least had to be on my setup.
At first I installed the 90.0.1 from the older site. I had to modify
wxdirect to do an import Foreign.C.Types to get rid of the arg type
errors and change the pointer assignment in eljpen.cpp that others have
mentioned. It was working fine so I installed the 90.1 from Atze's repo
into a
14 matches
Mail list logo
