From: Eric Y. K. <eri...@gm...> - 2009-09-02 18:47:14
|
Hi everybody, For those of you not following wxhaskell-devel: Brian Lewis has been doing which could make installing wxHaskell from source (and consequently install wxHaskell-based applications) a lot easier. He has cleaned up our build infrastructure, replacing our configure script, makefile and trivial Cabal wrapper with a 100% Cabal based solution. This includes our wxc layer now specified through the 'c-sources' field in the cabal file. It seems to work for me and Brian. Could somebody else try it out, maybe somebody on Windows? Here's the procedure. 1. Install wxWidgets if you have not done so already. I never managed to use wxHaskell with the wxWidgets that comes with MacOS X Leopard. On the other hand, building one for source works a lot better. (don't forget --enable-unicode). I had a similar experience with Ubuntu Linux too. 2. Update your PATH so that the wx-config from your wxWidgets is in it 3. Download Brian Lewis's work and install it git clone git://github.com/bsl/wxdirect.git git clone git://github.com/bsl/wxcore.git darcs get http://code.haskell.org/wxhaskell cd wxdirect; cabal install; cd .. cd wxcore; cabal install; cd .. cd wxhaskell/wx; cabal install 4. Now try building a sample application and test it. It would also be great if some wxHaskell developers could comment! If this works out it means we get much easier wxHaskell installation. :-) -- Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow> PGP Key ID: 08AC04F9 |
From: Lyle K. <li...@qs...> - 2009-09-03 05:49:33
|
Eric, Thanks to a pointer someone gave me, I found wx-config at: http://wxconfig.googlepages.com/ I followed your instructions, but I assumed that we should run the git lines if we have git, and darcs if we're using darcs. Do I need both git and darcs? I just have darcs installed. I had no problem building wxdirect: PS C:\Users\Lyle\devel\haskell\wxhaskell\wxdirect> cabal install Resolving dependencies... Configuring wxdirect-0.11.1.3... Preprocessing executables for wxdirect-0.11.1.3... Building wxdirect-0.11.1.3... [ 1 of 14] Compiling MultiSet ( src\MultiSet.hs, dist\build\wxdirect\wxdirect-tmp\MultiSet.o ) [ 2 of 14] Compiling HaskellNames ( src\HaskellNames.hs, dist\build\wxdirect\wxdirect-tmp\HaskellNames.o ) [ 3 of 14] Compiling Types ( src\Types.hs, dist\build\wxdirect\wxdirect-tmp\Types.o ) [ 4 of 14] Compiling CompileSTC ( src\CompileSTC.hs, dist\build\wxdirect\wxdirect-tmp\CompileSTC.o ) [ 5 of 14] Compiling ParseEiffel ( src\ParseEiffel.hs, dist\build\wxdirect\wxdirect-tmp\ParseEiffel.o ) [ 6 of 14] Compiling CompileDefs ( src\CompileDefs.hs, dist\build\wxdirect\wxdirect-tmp\CompileDefs.o ) [ 7 of 14] Compiling ParseC ( src\ParseC.hs, dist\build\wxdirect\wxdirect-tmp\ParseC.o ) [ 8 of 14] Compiling Classes ( src\Classes.hs, dist\build\wxdirect\wxdirect-tmp\Classes.o ) [ 9 of 14] Compiling CompileClassInfo ( src\CompileClassInfo.hs, dist\build\wxdirect\wxdirect-tmp\CompileClassInfo.o ) [10 of 14] Compiling DeriveTypes ( src\DeriveTypes.hs, dist\build\wxdirect\wxdirect-tmp\DeriveTypes.o ) [11 of 14] Compiling CompileClassTypes ( src\CompileClassTypes.hs, dist\build\wxdirect\wxdirect-tmp\CompileClassTypes.o ) [12 of 14] Compiling CompileHeader ( src\CompileHeader.hs, dist\build\wxdirect\wxdirect-tmp\CompileHeader.o ) [13 of 14] Compiling CompileClasses ( src\CompileClasses.hs, dist\build\wxdirect\wxdirect-tmp\CompileClasses.o ) [14 of 14] Compiling Main ( src\Main.hs, dist\build\wxdirect\wxdirect-tmp\Main.o ) Linking dist\build\wxdirect\wxdirect.exe ... Installing executable(s) in C:\Program Files\Haskell\bin But I had trouble building wxcore: PS C:\Users\Lyle\devel\haskell\wxhaskell\wxdirect> cd .. PS C:\Users\Lyle\devel\haskell\wxhaskell> cd wxcore PS C:\Users\Lyle\devel\haskell\wxhaskell\wxcore> cabal install Resolving dependencies... Configuring wxcore-0.11.1.3... Preprocessing library wxcore-0.11.1.3... cabal.exe: can't find source for Graphics.UI.WXCore.WxcClassTypes in src, dist\build\autogen cabal.exe: Error: some packages failed to install: wxcore-0.11.1.3 failed during the building phase. The exception was: exit: ExitFailure 1 Do I need git? Thanks, Lyle On Wed, Sep 2, 2009 at 11:47 AM, Eric Y. Kow <eri...@gm...> wrote: > Hi everybody, > > For those of you not following wxhaskell-devel: Brian Lewis has been > doing which could make installing wxHaskell from source (and > consequently install wxHaskell-based applications) a lot easier. > > He has cleaned up our build infrastructure, replacing our configure > script, makefile and trivial Cabal wrapper with a 100% Cabal based > solution. This includes our wxc layer now specified through the > 'c-sources' field in the cabal file. > > It seems to work for me and Brian. Could somebody else try it out, > maybe somebody on Windows? Here's the procedure. > > 1. Install wxWidgets if you have not done so already. > > I never managed to use wxHaskell with the wxWidgets that comes with > MacOS X Leopard. On the other hand, building one for source works a > lot better. (don't forget --enable-unicode). I had a similar > experience with Ubuntu Linux too. > > 2. Update your PATH so that the wx-config from your wxWidgets is in it > > 3. Download Brian Lewis's work and install it > > git clone git://github.com/bsl/wxdirect.git > git clone git://github.com/bsl/wxcore.git > darcs get http://code.haskell.org/wxhaskell > cd wxdirect; cabal install; cd .. > cd wxcore; cabal install; cd .. > cd wxhaskell/wx; cabal install > > 4. Now try building a sample application and test it. > > It would also be great if some wxHaskell developers could comment! If > this works out it means we get much easier wxHaskell installation. :-) > > -- > Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow> > PGP Key ID: 08AC04F9 > > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus > on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > wxhaskell-users mailing list > wxh...@li... > https://lists.sourceforge.net/lists/listinfo/wxhaskell-users > > |
From: Eric Y. K. <eri...@gm...> - 2009-09-03 09:27:31
|
Hi Lyle, On Wed, Sep 02, 2009 at 22:49:24 -0700, Lyle Kopnicky wrote: > Thanks to a pointer someone gave me, I found wx-config at: > > http://wxconfig.googlepages.com/ Interesting. By rights, it really should just ship with wxWidgets. > I followed your instructions, but I assumed that we should run the git lines > if we have git, and darcs if we're using darcs. Do I need both git and > darcs? I just have darcs installed. I had no problem building wxdirect: For the moment, you need both git and darcs. Until we hear back from the wxHaskell team, work on wxcore is taking place on github. If the team respond, I think we should start submitting patches so that the wxHaskell darcs repository catches up. I also think we should upgrade the wxHaskell repository to a hashed darcs repository, which will make it a bit faster to fetch, but that's another story. -- Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow> PGP Key ID: 08AC04F9 |
From: Lyle K. <li...@qs...> - 2009-09-03 06:18:52
|
Hmm... I installed git, and cloned the repositories as requested. Now I can cd to wxdirect and cabal install it, no problem. Then I cd to the wxcore git repository, and cabal install, and it complains that it can't find my wxWidgets installation, to use the --prefix flag or set WXWIN. I tried cabal install with the --prefix flag, but that didn't work either. So I set WXWIN and tried again. No good. Output is below. I'm using Vista 32-bit, PowerShell V2. PS C:\Users\Lyle\devel\haskell\wxcore> $env:WXCFG = "C:\wxWidgets-2.8.10" PS C:\Users\Lyle\devel\haskell\wxcore> cabal install Resolving dependencies... generating: src/haskell/Graphics/UI/WXCore/WxcClassTypes.hs reading class definitions: parsing: src/include/wxc.h parsing: src/include/wxc_types.h parsing: src/include/wxc_glue.h parsing: src/include/db.h parsing: src/include/dragimage.h parsing: src/include/graphicscontext.h parsing: src/include/glcanvas.h parsing: src/include/sound.h parsing: src/include/managed.h parsing: src/include/mediactrl.h parsing: src/include/previewframe.h parsing: src/include/printout.h parsing: src/include/textstream.h parsing: src/include/stc.h parsing: src/include/stc_gen.h generated 539 class definitions. ok. generating: src/haskell/Graphics/UI/WXCore/WxcClassInfo.hs reading class definitions: parsing: src/include/wxc.h parsing: src/include/wxc_types.h parsing: src/include/wxc_glue.h parsing: src/include/db.h parsing: src/include/dragimage.h parsing: src/include/graphicscontext.h parsing: src/include/glcanvas.h parsing: src/include/sound.h parsing: src/include/managed.h parsing: src/include/mediactrl.h parsing: src/include/previewframe.h parsing: src/include/printout.h parsing: src/include/textstream.h parsing: src/include/stc.h parsing: src/include/stc_gen.h generated 381 class info definitions ok. parsing: src/include/wxc.h parsing: src/include/wxc_types.h parsing: src/include/wxc_glue.h parsing: src/include/db.h parsing: src/include/dragimage.h parsing: src/include/graphicscontext.h parsing: src/include/glcanvas.h parsing: src/include/sound.h parsing: src/include/managed.h parsing: src/include/mediactrl.h parsing: src/include/previewframe.h parsing: src/include/printout.h parsing: src/include/textstream.h parsing: src/include/stc.h parsing: src/include/stc_gen.h ignore: parse error : //WXCOLORREF wxColour_GetPixel( TSelf(wxColour) _obj ); generating: src/haskell/Graphics/UI/WXCore/WxcClassesAL.hs reading class definitions: parsing: src/include/wxc.h parsing: src/include/wxc_types.h parsing: src/include/wxc_glue.h parsing: src/include/db.h parsing: src/include/dragimage.h parsing: src/include/graphicscontext.h parsing: src/include/glcanvas.h parsing: src/include/sound.h parsing: src/include/managed.h parsing: src/include/mediactrl.h parsing: src/include/previewframe.h parsing: src/include/printout.h parsing: src/include/textstream.h parsing: src/include/stc.h parsing: src/include/stc_gen.h generated 1565 methods for 121 classes. generating: src/haskell/Graphics/UI/WXCore/WxcClassesMZ.hs generated 2184 methods for 123 classes. generating: src/haskell/Graphics/UI/WXCore/WxcClasses.hs generated 3749 total methods for 244 total classes. ok. parsing: src/eiffel/wxc_defs.e parsing: src/eiffel/wx_defs.e parsing: src/eiffel/stc.e generating: src/haskell/Graphics/UI/WXCore/WxcDefs.hs generated 2439 constant definitions ok. Please use the --prefix flag (as in wx-config --prefix=C:\wxWidgets) or set the environment variable WXWIN (as in WXWIN=C:\wxWidgets) to specify where is your installation of wxWidgets. setup.exe: readProcess: wx-config "--libs" "--cppflags" (exit 1): failed cabal.exe: Error: some packages failed to install: wxcore-0.11.1.3 failed during the configure step. The exception was: exit: ExitFailure 1 |
From: Lyle K. <li...@qs...> - 2009-09-03 06:26:13
|
Sorry folks, I realized I mixed something up in the last one. I set WXCFG instead of WXWIN. When I set WXWIN, it stops complaining about WXWIN, and starts complaining about WXCFG: Please use the --wxcfg flag (as in wx-config --wxcfg=gcc_dll\mswud) or set the environment variable WXCFG (as in WXCFG=gcc_dll\mswud) to specify which configuration exactly you want to use. setup.exe: readProcess: wx-config "--libs" "--cppflags" (exit 1): failed cabal.exe: Error: some packages failed to install: wxcore-0.11.1.3 failed during the configure step. The exception was: exit: ExitFailure 1 PS C:\Users\Lyle\devel\haskell\wxcore> I tried setting WXCFG to vc_dll\msw, but that doesn't help. I also tried setting it to "build\msw", or putting the full path in front. I still get that error. I can't figure out what kind of value it wants. Any ideas? Thanks, Lyle |
From: Lyle K. <li...@qs...> - 2009-09-03 06:38:26
|
Oh, I finally figured it out! I had to type: PS C:\Users\Lyle\devel\haskell\wxcore> $env:WXCFG = "vc_lib\mswd" And then I was able to run cabal install without the previous error. Why mswd and not msw, I have no idea. When I run wx-config without parameters, it tells me WXCFG should point to the "relative path of build.cfg". Relative to what, who knows? So I had to try things until I figured it out. So, it built a bunch of classes, but then it started spewing out a bunch of errors. It couldn't find things: [23 of 23] Compiling Graphics.UI.WXCore ( src\haskell\Graphics\UI\WXCore.hs, dist\build\Graphics\UI\WXCore.o ) In file included from src\cpp\apppath.cpp:1:0: src\include\wrapper.h:20:19: wx/wx.h: No such file or directory <sigh> So close... It spit out a bunch of "no such file or directory" errors, then started varying them: In file included from src\cpp\apppath.cpp:1:0: src\include\wrapper.h:77:0: error: expected initializer before '*' token src\include\wrapper.h:96:0: error: `wxString' has not been declared src\include\wrapper.h:96:0: error: ISO C++ forbids declaration of `src' with no type src\include\wrapper.h:107:0: error: expected class-name before '{' token ... src\include\wrapper.h:388:0: error: class `ELJServer' does not have any field named `wxTCPServer' src/include/wrapper.h: At global scope: src\include\wrapper.h:398:0: error: expected class-name before '{' token src\include\wrapper.h:404:0: error: ISO C++ forbids declaration of `wxConnectionBase' with no type src\include\wrapper.h:404:0: error: `wxConnectionBase' declared as a `virtual' field src\include\wrapper.h:404:0: error: expected `;' before '*' token src/include/wrapper.h: In constructor `ELJClient::ELJClient(void*, void*)': And so on... - Lyle |
From: anty <ma...@an...> - 2009-09-03 10:10:18
Attachments:
signature.asc
|
Hi, I tried to follow your steps on WindowsXP. I'm now stuck at setting the WXCFG environment variable to be able to compile wxcore. I can't find a build.cfg so I don't know what path I should set. Any ideas? BTW: wx-config.exe is not included in the 2.8.10 install-version, nor in the source package. You have to download it from http://wxconfig.googlepages.com/ Eric Y. Kow wrote: > Hi everybody, > > For those of you not following wxhaskell-devel: Brian Lewis has been > doing which could make installing wxHaskell from source (and > consequently install wxHaskell-based applications) a lot easier. > > He has cleaned up our build infrastructure, replacing our configure > script, makefile and trivial Cabal wrapper with a 100% Cabal based > solution. This includes our wxc layer now specified through the > 'c-sources' field in the cabal file. > > It seems to work for me and Brian. Could somebody else try it out, > maybe somebody on Windows? Here's the procedure. > > 1. Install wxWidgets if you have not done so already. > > I never managed to use wxHaskell with the wxWidgets that comes with > MacOS X Leopard. On the other hand, building one for source works a > lot better. (don't forget --enable-unicode). I had a similar > experience with Ubuntu Linux too. > > 2. Update your PATH so that the wx-config from your wxWidgets is in it > > 3. Download Brian Lewis's work and install it > > git clone git://github.com/bsl/wxdirect.git > git clone git://github.com/bsl/wxcore.git > darcs get http://code.haskell.org/wxhaskell > cd wxdirect; cabal install; cd .. > cd wxcore; cabal install; cd .. > cd wxhaskell/wx; cabal install > > 4. Now try building a sample application and test it. > > It would also be great if some wxHaskell developers could comment! If > this works out it means we get much easier wxHaskell installation. :-) > > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > ------------------------------------------------------------------------ > > _______________________________________________ > wxhaskell-users mailing list > wxh...@li... > https://lists.sourceforge.net/lists/listinfo/wxhaskell-users > |
From: Brian L. <br...@lo...> - 2009-09-04 04:32:09
|
I'll check out the situation in Windows tonight. |
From: Brian L. <br...@lo...> - 2009-09-04 14:01:00
|
I didn't get it to work, but maybe I made some progress. I installed wxWidgets by installing wxPack, a binary distribution. I did it that way just because I didn't know what else to do. Like Lyle Kopnicky mentioned, wx-config(1) doesn't come with wxWidgets. I attribute it to the fundamental theorem of Windows, that everything in Windows has to be nasty. I just dropped it somewhere in PATH. The first bad news you'll see if you do 'cabal configure' is that cabal seems unable to find the Windows or wx libraries. Actually, the problem seems to be that cabal checks for the existence of the libraries by compiling a dummy main() {} type program, specifying -lwhatever, but it also specifies -Wno-attributes, a parameter gcc 3.4.5 doesn't seem to understand. cabal interprets gcc's error exit code to mean that the library isn't there, which is wrong. I created a ticket about it: http://hackage.haskell.org/trac/hackage/ticket/580 Even though 'cabal configure' seems busted, you can still build. The first error I got was that gcc couldn't find <string>. To fix that, I added an include directory. The next error was an inability to find c++config.h. I fixed it the same way. Is it reasonable for ghc to be having this problem? It runs its own copy of gcc. Then, for some reason, some wx includes (at least in wxPack), are off by themselves in some contrib/. So, I added that include directory, too. cabal configure --extra-include-dirs=/c/brian/tools/ghc-6.10.4/include/mingw/c++/3.4.5 --extra-include-dirs=/c/brian/tools/ghc-6.10.4/include/mingw/c++/3.4.5/mingw32/ --extra-include-dirs=/c/SourceCode/Libraries/wxWidgets2.8/contrib/include cabal build There seem to be a lot of warnings, but the build seems to finish. After that, though, 'cabal install' doesn't work because of the issue about not being able to verify that the presence of the required libraries. Hopefully the cabal devs will fix this soon. I normally don't do anything in Windows. If you do, please take a few minutes to try to improve this process. I'm probably not doing stuff very well because it's unfamiliar territory. Thank you. |
From: Jeremy O'D. <jer...@gm...> - 2009-09-07 13:04:44
|
Eric Y. Kow wrote: > For the moment, you need both git and darcs. > > Until we hear back from the wxHaskell team, work on wxcore is taking > place on github. If the team respond, I think we should start > submitting patches so that the wxHaskell darcs repository catches up. > Eric, I'll try to get this fixed and turned into darcs patches over the next couple of weeks. I agree that it's a very good idea, and although I haven't looked in detail, a quick glance suggests that Brian has done a very thorough job. ... better go off and learn how to use git, I suppose... Regards Jeremy |
From: Eric Y. K. <eri...@gm...> - 2009-09-07 13:07:50
|
On Mon, Sep 07, 2009 at 14:04:30 +0100, Jeremy O'Donoghue wrote: > > Until we hear back from the wxHaskell team, work on wxcore is taking > > place on github. If the team respond, I think we should start > > submitting patches so that the wxHaskell darcs repository catches up. > > > Eric, I'll try to get this fixed and turned into darcs patches over the > next couple of weeks. I agree that it's a very good idea, and although I > haven't looked in detail, a quick glance suggests that Brian has done a > very thorough job. Thanks! I've sent a very small fragment of Brian's work (not the bits that matter, unfortunately) to wxhaskell-devel but they got stuck in the moderation queue. Also: I'd like to help you guys with darcs a little bit, but I'll talk about that in a separate mail. -- Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow> PGP Key ID: 08AC04F9 |
From: Eric Y. K. <eri...@gm...> - 2009-09-18 06:09:34
|
On Mon, Sep 07, 2009 at 14:04:30 +0100, Jeremy O'Donoghue wrote: > Eric, I'll try to get this fixed and turned into darcs patches over the > next couple of weeks. I agree that it's a very good idea, and although I > haven't looked in detail, a quick glance suggests that Brian has done a > very thorough job. > > ... better go off and learn how to use git, I suppose... Sounds great. Can I nudge you a bit on this? It sounds like the two main issues are 1. getting this into the main repository 2. figuring out what to do about Windows Shelarcy, are you around by any chance to look into the #1? Thanks! PS. wxHaskell is looking a little unloved lately, with very little contact from the team, mails going unmoderated, etc. Where is everybody? :-) -- Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow> PGP Key ID: 08AC04F9 |