Re: [wxhaskell-devel] Compile problems
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 on my machine, I can't expect any users to go through all this. -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ wxhaskell-devel mailing list wxhaskell-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wxhaskell-devel
Re: [wxhaskell-devel] Compile problems
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 sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ wxhaskell-devel mailing list wxhaskell-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wxhaskell-devel
Re: [wxhaskell-devel] Compile problems
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 your DLLs in a directory without spaces in the path? Regards, Henk-Jan van Tuyl -- Folding@home What if you could share your unused computer power to help find a cure? In just 5 minutes you can join the world's biggest networked computer and get us closer sooner. Watch the video. http://folding.stanford.edu/ http://Van.Tuyl.eu/ http://members.chello.nl/hjgtuyl/tourdemonad.html Haskell programming -- -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ wxhaskell-devel mailing list wxhaskell-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wxhaskell-devel
Re: [wxhaskell-devel] Compile problems
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 header read by wxdirect
* Define a 'NULL' implementation as well as the correct one, e.g.
In wxc_glue.h
int wxSomeClass_GetSomeParam( TSelf(wxSomeClass), int param1, int param2);
in SomeClass.cpp
EWXWEXPORT(int,wxSomeClass_GetSomeParam)(wxSomeClass* self, int param1, int
param2)
{
#if (wxVERSION_NUMBER 2900)
return 0;
#else
// Do the real wrapping
#endif
}
This is far from ideal, but it is the simplest workaround to get things
compiling. You can use wxCHECK_VERSION above as well - I think the logic is
inverted, but the code is otherwise similar.
Jeremy
On 9 June 2013 21:52, Charles the Hawk charlestheh...@yahoo.com wrote:
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 sandbox as described in the wiki. I thought I changed the path
to use the 90.1 wxdirect but it's possible the older modified wxdirect
was running. I'll try to play around with it some tomorrow and make
sure my modified wxdirect isn't being run. But I definitely had to
change all the CHECK_VERSIONs to 2,9,4 or they could be commented out as
Blair suggested.
I think we need to decide what to do on conditional compiles. Either 1)
modify wxdirect to handle them (way over my head), 2) no conditionals in
the headers wxdirect processes which also means to leave out any new
function not in a specific lower version, or 3) require a specific
higher version. It seems to me that #2 is probably the simplest and
thus best way to go as that should work on more installs without
requiring modifications unless it turns out that SetDeviceClippingRegion
is actually required in 2.9.4 installs.
On 06/09/2013 07:31 PM, harry wrote:
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.
Then a simple: cabal install ./wxdirect ./wxc ./wxcore ./wx
Should hopefully get you up and running, let me know how it goes.
I used that one as well, and got a ton of Unacceptable argument type in
foreign declaration errors, perhaps related to
http://hackage.haskell.org/trac/ghc/ticket/5610.
--
How ServiceNow helps IT people transform IT departments:
1. A cloud service to automate IT design, transition and operations
2. Dashboards that offer high-level views of enterprise services
3. A single system of record for all IT processes
http://p.sf.net/sfu/servicenow-d2d-j
___
wxhaskell-devel mailing list
wxhaskell-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wxhaskell-devel
--
How ServiceNow helps IT people transform IT departments:
1. A cloud service to automate IT design, transition and operations
2. Dashboards that offer high-level views of enterprise services
3. A single system of record for all IT processes
http://p.sf.net/sfu/servicenow-d2d-j
___
wxhaskell-devel mailing list
wxhaskell-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wxhaskell-devel
--
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev___
wxhaskell-devel mailing list
wxhaskell-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wxhaskell-devel
Re: [wxhaskell-devel] Compile problems
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 problem, I'm on a 64 bit system. But the perl dll is probably 32 bit, and I don't know what the other stuff it's being linked with is - I'm over my head now. -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ wxhaskell-devel mailing list wxhaskell-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wxhaskell-devel
Re: [wxhaskell-devel] Compile problems
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 couldn't find anything! Is the one you uploaded 32 bit? Maybe that's the problem, I'm on a 64 bit system. But the perl dll is probably 32 bit, and I don't know what the other stuff it's being linked with is - I'm over my head now. I have a 32 bit system, the DLLs are working, so the DLLs must be 32 bit. Regards, Henk-Jan van Tuyl -- Folding@home What if you could share your unused computer power to help find a cure? In just 5 minutes you can join the world's biggest networked computer and get us closer sooner. Watch the video. http://folding.stanford.edu/ http://Van.Tuyl.eu/ http://members.chello.nl/hjgtuyl/tourdemonad.html Haskell programming -- -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ wxhaskell-devel mailing list wxhaskell-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wxhaskell-devel
Re: [wxhaskell-devel] Compile problems
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 wants? -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ wxhaskell-devel mailing list wxhaskell-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wxhaskell-devel
Re: [wxhaskell-devel] Compile problems
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 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 wants? -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ wxhaskell-devel mailing list wxhaskell-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wxhaskell-devel -- Eric Kow http://erickow.com -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ wxhaskell-devel mailing list wxhaskell-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wxhaskell-devel
Re: [wxhaskell-devel] Compile problems
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. -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ wxhaskell-devel mailing list wxhaskell-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wxhaskell-devel
Re: [wxhaskell-devel] Compile problems
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 sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ wxhaskell-devel mailing list wxhaskell-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wxhaskell-devel
Re: [wxhaskell-devel] Compile problems
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 mentioned. It was working fine so I installed the 90.1 from Atze's repo into a sandbox as described in the wiki. I thought I changed the path to use the 90.1 wxdirect but it's possible the older modified wxdirect was running. I'll try to play around with it some tomorrow and make sure my modified wxdirect isn't being run. But I definitely had to change all the CHECK_VERSIONs to 2,9,4 or they could be commented out as Blair suggested. Could you upload your modified code to Github? You seem to have done a lot of good work to make it compile, it would be great if others could use it. Any noobs out there like me trying to install this and getting reinstall warnings, save yourself some grief and unregister any older versions of the 4 packages (wx, wxc, wxcore, wxdirect) before installing. (ghc-pkg unregister pkgname). I'm using ArchLinux, ghc 7.6.3, wxWidgets 2.9.4, and the current repo (atzedijkstra). The only change I had to make was to change the wxCHECK_VERSION(2,9,5) that refer to SetDeviceClippingRegion to wxCHECK_VERSION(2,9,4) in wxc/src/include/wxc_glue.h and wxc/src/cpp/eljdc.cpp. Atze has them at 2,9,5 for a reason. It will compile but I get link errors without the above change. If you get an error while compiling eljpen.cpp, you probably don't have the latest version. Harry, After discovering the above, Atze's repo compiled fine, so I don't think I should check that mod in. I doubt it would hurt anything but let's not clutter up the code with anything unnecessary. If you still have problems after following the above and want to try it to see if it fixes your problem, edit wxdirect/src/CompileClasses.hs. Line 110 should be something like: , import qualified Data.ByteSTring as B (... Insert before that line: , import Foreign.C.Types In the old repo, it was line 101 so perhaps a change has already been made to fix the problem. It's also possible I changed more than one thing on my system between compiles and this had nothing to do with it working. -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ wxhaskell-devel mailing list wxhaskell-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wxhaskell-devel
Re: [wxhaskell-devel] Compile problems
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 ./wxcore ./wx Should hopefully get you up and running, let me know how it goes. Many thanks, Blair On 9 June 2013 11:17, harry volderm...@hotmail.com wrote: Charles the Hawk charlesthehawk@... writes: Hi, all! I'm new to Haskell and guessing a bit here. I'm using Arch Linux and ghc 7.6.3. The maintenance repo package compiles and installs You're doing better than me if you could install on ghc 7.6.3. Which repo did you get the code from, and did you do anything to make it complile? -- How ServiceNow helps IT people transform IT departments: 1. A cloud service to automate IT design, transition and operations 2. Dashboards that offer high-level views of enterprise services 3. A single system of record for all IT processes http://p.sf.net/sfu/servicenow-d2d-j ___ wxhaskell-devel mailing list wxhaskell-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wxhaskell-devel -- How ServiceNow helps IT people transform IT departments: 1. A cloud service to automate IT design, transition and operations 2. Dashboards that offer high-level views of enterprise services 3. A single system of record for all IT processes http://p.sf.net/sfu/servicenow-d2d-j___ wxhaskell-devel mailing list wxhaskell-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wxhaskell-devel
Re: [wxhaskell-devel] Compile problems
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. Then a simple: cabal install ./wxdirect ./wxc ./wxcore ./wx Should hopefully get you up and running, let me know how it goes. I used that one as well, and got a ton of Unacceptable argument type in foreign declaration errors, perhaps related to http://hackage.haskell.org/trac/ghc/ticket/5610. -- How ServiceNow helps IT people transform IT departments: 1. A cloud service to automate IT design, transition and operations 2. Dashboards that offer high-level views of enterprise services 3. A single system of record for all IT processes http://p.sf.net/sfu/servicenow-d2d-j ___ wxhaskell-devel mailing list wxhaskell-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wxhaskell-devel
Re: [wxhaskell-devel] Compile problems
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 sandbox as described in the wiki. I thought I changed the path to use the 90.1 wxdirect but it's possible the older modified wxdirect was running. I'll try to play around with it some tomorrow and make sure my modified wxdirect isn't being run. But I definitely had to change all the CHECK_VERSIONs to 2,9,4 or they could be commented out as Blair suggested. I think we need to decide what to do on conditional compiles. Either 1) modify wxdirect to handle them (way over my head), 2) no conditionals in the headers wxdirect processes which also means to leave out any new function not in a specific lower version, or 3) require a specific higher version. It seems to me that #2 is probably the simplest and thus best way to go as that should work on more installs without requiring modifications unless it turns out that SetDeviceClippingRegion is actually required in 2.9.4 installs. On 06/09/2013 07:31 PM, harry wrote: 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. Then a simple: cabal install ./wxdirect ./wxc ./wxcore ./wx Should hopefully get you up and running, let me know how it goes. I used that one as well, and got a ton of Unacceptable argument type in foreign declaration errors, perhaps related to http://hackage.haskell.org/trac/ghc/ticket/5610. -- How ServiceNow helps IT people transform IT departments: 1. A cloud service to automate IT design, transition and operations 2. Dashboards that offer high-level views of enterprise services 3. A single system of record for all IT processes http://p.sf.net/sfu/servicenow-d2d-j ___ wxhaskell-devel mailing list wxhaskell-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wxhaskell-devel -- How ServiceNow helps IT people transform IT departments: 1. A cloud service to automate IT design, transition and operations 2. Dashboards that offer high-level views of enterprise services 3. A single system of record for all IT processes http://p.sf.net/sfu/servicenow-d2d-j ___ wxhaskell-devel mailing list wxhaskell-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wxhaskell-devel
