You can subscribe to this list here.
2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(12) |
Aug
(34) |
Sep
(14) |
Oct
(36) |
Nov
(32) |
Dec
(15) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2004 |
Jan
|
Feb
(9) |
Mar
(31) |
Apr
(36) |
May
(17) |
Jun
(21) |
Jul
(13) |
Aug
(18) |
Sep
(2) |
Oct
(10) |
Nov
(18) |
Dec
(28) |
2005 |
Jan
(26) |
Feb
(15) |
Mar
(26) |
Apr
(11) |
May
(60) |
Jun
(3) |
Jul
(12) |
Aug
(4) |
Sep
(12) |
Oct
(19) |
Nov
(36) |
Dec
(10) |
2006 |
Jan
(6) |
Feb
(13) |
Mar
(6) |
Apr
(2) |
May
(9) |
Jun
(3) |
Jul
(6) |
Aug
(13) |
Sep
(1) |
Oct
(24) |
Nov
(33) |
Dec
(47) |
2007 |
Jan
(21) |
Feb
(41) |
Mar
(17) |
Apr
(9) |
May
(4) |
Jun
(20) |
Jul
(24) |
Aug
(71) |
Sep
(35) |
Oct
(10) |
Nov
(39) |
Dec
(39) |
2008 |
Jan
(24) |
Feb
(42) |
Mar
(61) |
Apr
(12) |
May
(11) |
Jun
(4) |
Jul
(9) |
Aug
(6) |
Sep
(6) |
Oct
(4) |
Nov
(3) |
Dec
(14) |
2009 |
Jan
(25) |
Feb
(18) |
Mar
(19) |
Apr
(24) |
May
(14) |
Jun
(7) |
Jul
(14) |
Aug
(25) |
Sep
(40) |
Oct
(20) |
Nov
(22) |
Dec
(4) |
2010 |
Jan
(55) |
Feb
(11) |
Mar
(9) |
Apr
(10) |
May
(10) |
Jun
(9) |
Jul
(7) |
Aug
(4) |
Sep
(15) |
Oct
(7) |
Nov
(2) |
Dec
(3) |
2011 |
Jan
(2) |
Feb
(1) |
Mar
(4) |
Apr
(6) |
May
(20) |
Jun
(30) |
Jul
(15) |
Aug
(4) |
Sep
(23) |
Oct
(24) |
Nov
(3) |
Dec
(8) |
2012 |
Jan
(23) |
Feb
(7) |
Mar
(19) |
Apr
(48) |
May
(8) |
Jun
(27) |
Jul
(10) |
Aug
(1) |
Sep
(11) |
Oct
(1) |
Nov
|
Dec
(3) |
2013 |
Jan
(1) |
Feb
|
Mar
(17) |
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2014 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
(12) |
Sep
(2) |
Oct
|
Nov
|
Dec
(1) |
2015 |
Jan
|
Feb
|
Mar
(14) |
Apr
(5) |
May
(1) |
Jun
|
Jul
|
Aug
(2) |
Sep
(5) |
Oct
(1) |
Nov
(2) |
Dec
(1) |
2016 |
Jan
(7) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2017 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2018 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Eric Y. K. <eri...@gm...> - 2009-09-07 08:53:57
|
On Sun, Sep 06, 2009 at 21:03:27 +0200, Sebastian Klüft wrote: > > Hmm, that's interesting. Are you using the stock wxWidgets or one that > > you built yourself? > > Yes I have (sort of). I have installed wxWidgets through MacPorts, so > it's built on this machine but everything is done automagically. Another thought: are you sure it's your MacPorts-installed wxWidgets that's being picked up by the wxcore configure script and not the stock one? Thanks, -- Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow> PGP Key ID: 08AC04F9 |
From: Eric Y. K. <eri...@gm...> - 2009-09-06 19:14:34
|
On Sun, Sep 06, 2009 at 21:03:27 +0200, Sebastian Klüft wrote: > How do I get this "recabalised" wxcore? git clone git://github.com/bsl/wxdirect git clone git://github.com/bsl/wxcore It's not yet officially supported by the wxHaskell team, but perhaps in the future it will be. -- Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow> PGP Key ID: 08AC04F9 |
From: Sebastian K. <sk...@gm...> - 2009-09-06 19:03:59
|
2009/9/5 Eric Y. Kow <eri...@gm...>: > Hmm, that's interesting. Are you using the stock wxWidgets or one that > you built yourself? Yes I have (sort of). I have installed wxWidgets through MacPorts, so it's built on this machine but everything is done automagically. Guess i could try the binary distribution instead and see if that helps. > Also, I'm using the new recabalised wxcore (which has the advantage that > you don't need to install it in the global package space), if it makes a > difference. How do I get this "recabalised" wxcore? /Sebastian |
From: Fernando B. <gre...@gm...> - 2009-09-05 15:17:09
|
Hi Eric That file has the bug too, indeed Pablo Picasso<http://www.brainyquote.com/quotes/authors/p/pablo_picasso.html> - "Computers are useless. They can only give you answers." On Sat, Sep 5, 2009 at 6:12 AM, Eric Y. Kow <eri...@gm...> wrote: > On Fri, Sep 04, 2009 at 10:32:04 -0300, Fernando Benavides wrote: > > Googleing a bit, I've found that this is a known bug in wxEiffel: > > > http://www.mombu.com/programming/eiffel/t-problems-getting-a-wx-find-replace-data-1408529.html > > Then, I've checked the source code for wxHaskell ( > > http://darcs.haskell.org/wxhaskell/wxc/src/eljfindrepldlg.cpp) and found > > this: > > Thanks for this! > > Is http://code.haskell.org/wxhaskell/wxc/src/eljfindrepldlg.cpp > also wrong? > > The repo has been moved to code.haskell.org. This sort of thing makes > me wish for wxC unification. > > -- > Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow> > PGP Key ID: 08AC04F9 > |
From: Eric Y. K. <eri...@gm...> - 2009-09-05 09:12:39
|
On Fri, Sep 04, 2009 at 10:32:04 -0300, Fernando Benavides wrote: > Googleing a bit, I've found that this is a known bug in wxEiffel: > http://www.mombu.com/programming/eiffel/t-problems-getting-a-wx-find-replace-data-1408529.html > Then, I've checked the source code for wxHaskell ( > http://darcs.haskell.org/wxhaskell/wxc/src/eljfindrepldlg.cpp) and found > this: Thanks for this! Is http://code.haskell.org/wxhaskell/wxc/src/eljfindrepldlg.cpp also wrong? The repo has been moved to code.haskell.org. This sort of thing makes me wish for wxC unification. -- Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow> PGP Key ID: 08AC04F9 |
From: Eric Y. K. <eri...@gm...> - 2009-09-05 09:11:01
|
On Fri, Sep 04, 2009 at 23:06:18 +0200, Sebastian Klüft wrote: > I can add that I'm also running Mac OS X Leopard and I installed > WXHaskell through Cabal. Hmm, that's interesting. Are you using the stock wxWidgets or one that you built yourself? Also, I'm using the new recabalised wxcore (which has the advantage that you don't need to install it in the global package space), if it makes a difference. > GHC version: 6.10.4. Likewise. Latest Haskell Platform. Eric PS. What would make me very happy is if magically, the wxWidgets that ships with Snow Leopard just works with wxHaskell. I'm slightly less grumpy about this now that I've discovered that Ubuntu Jaunty's wxWidgets works just fine. I wonder what's changed where. -- Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow> PGP Key ID: 08AC04F9 |
From: Sebastian K. <sk...@gm...> - 2009-09-04 21:06:48
|
Thanks for the reply. I can add that I'm also running Mac OS X Leopard and I installed WXHaskell through Cabal. GHC version: 6.10.4. -- Sebastian Klüft sk...@gm... 2009/9/4 Eric Y. Kow <eri...@gm...>: > Hi Sebastian, > > On Fri, Sep 04, 2009 at 12:34:32 +0200, Sebastian Klüft wrote: >> "assert "m_dynamicEvents" failed in SearchDynamicEventTable(): caller >> should check that we have dynamic events" >> >> Everything seems to work just fine if i ignore it. So I'm wondering >> what the meaning of it is and how to get rid of it? > > I don't really know how to answer your question, but I can at least > report that this program does not spit out any error messages: > > import Graphics.UI.WX > > main = start gui > gui = do > f <- frame [text := "Hello World"] > t <- timer f [interval := 20] > return () > > Works for me on MacOS X Leopard without any warnings. > I'm using a wxWidgets I built myself. > > Maybe folks on other platforms could try the same? > > -- > Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow> > PGP Key ID: 08AC04F9 > |
From: Fernando B. <gre...@gm...> - 2009-09-04 14:01:53
|
Hi all, I'm working in my first project with wxHaskell. My project includes an editor, so I wanted to add find&replace functionality to it but then I stepped into what I think is a little bug. I think you'll see the problem clearly with an example (and it will be easier for me than explaining it in english :P): Let's say you've got the following code > *s* <- *findReplaceDataCreateDefault* > *findReplaceDataSetFindString* *s* "find" > *findReplaceDataSetReplaceString* *s* "replace" > *r* <- *findReplaceDataGetReplaceString* *s* > You expect that, when executed, the value of r will be "replace", but it's not. It's "find" instead. Googleing a bit, I've found that this is a known bug in wxEiffel: http://www.mombu.com/programming/eiffel/t-problems-getting-a-wx-find-replace-data-1408529.html Then, I've checked the source code for wxHaskell ( http://darcs.haskell.org/wxhaskell/wxc/src/eljfindrepldlg.cpp) and found this: EWXWEXPORT(wxString*,*wxFindReplaceData_GetReplaceString*)(void* _obj) > { > wxString *result = new wxString(); > *result = ((wxFindReplaceData*)_obj)->*GetFindString*(); > return result; > } > I think that explains it. Then I decided to write this mail to let you know about it, so maybe it can be fixed in the next wxHaskell release :) Cheers!! Joan Crawford<http://www.brainyquote.com/quotes/authors/j/joan_crawford.html> - "I, Joan Crawford, I believe in the dollar. Everything I earn, I spend." |
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: Eric Y. K. <eri...@gm...> - 2009-09-04 13:18:31
|
Hi Sebastian, On Fri, Sep 04, 2009 at 12:34:32 +0200, Sebastian Klüft wrote: > "assert "m_dynamicEvents" failed in SearchDynamicEventTable(): caller > should check that we have dynamic events" > > Everything seems to work just fine if i ignore it. So I'm wondering > what the meaning of it is and how to get rid of it? I don't really know how to answer your question, but I can at least report that this program does not spit out any error messages: import Graphics.UI.WX main = start gui gui = do f <- frame [text := "Hello World"] t <- timer f [interval := 20] return () Works for me on MacOS X Leopard without any warnings. I'm using a wxWidgets I built myself. Maybe folks on other platforms could try the same? -- Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow> PGP Key ID: 08AC04F9 |
From: Sebastian K. <sk...@gm...> - 2009-09-04 10:35:03
|
Hello, I've just installed wxhaskell via cabal. But every time i create a timer i get this warning message that looks as follows: "assert "m_dynamicEvents" failed in SearchDynamicEventTable(): caller should check that we have dynamic events" Everything seems to work just fine if i ignore it. So I'm wondering what the meaning of it is and how to get rid of it? The simplest program I've been able to make that produces this message is gui = do f <- frame [text := "Hello World"] t <- timer f [interval := 20] return () If i comment out the timer part i don't get the warning message. Likewise if I modify the program and add an "on paint" event to the frame the warning message never pops up. Like so: gui = do f <- frame [text := "Hello World", on paint := (\_ _ -> return ())] t <- timer f [interval := 20] return () Regards Sebastian Klüft sk...@gm... |
From: Brian L. <br...@lo...> - 2009-09-04 04:32:09
|
I'll check out the situation in Windows tonight. |
From: Eric Y. K. <eri...@gm...> - 2009-09-03 21:34:59
|
On Wed, Sep 02, 2009 at 18:20:57 -0400, Anthony Cowley wrote: > Is there a way to style a frame so that a wxHaskell application on Mac > OS X runs full screen? I've tried setting the style to 31, which hides > the usual window chrome, but haven't been able to get something whose > client area actually covers the screen. So, I wouldn't really know how to answer this question, but it sounds like a good first step would be to work out how to do it in wxWidgets... and then see if wxHaskell needs to be in any way extended to support it. -- Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow> PGP Key ID: 08AC04F9 |
From: anty <ma...@an...> - 2009-09-03 10:10:18
|
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: 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: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: 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: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 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: Anthony C. <ac...@se...> - 2009-09-02 22:21:10
|
Hello, Is there a way to style a frame so that a wxHaskell application on Mac OS X runs full screen? I've tried setting the style to 31, which hides the usual window chrome, but haven't been able to get something whose client area actually covers the screen. Thanks, Anthony |
From: Eric Y. K. <eri...@gm...> - 2009-09-02 20:45:43
|
> > On Wed, Sep 02, 2009 at 00:14:08 -0700, Lyle Kopnicky wrote: > > > Is it not possible to install wxHaskell without Cygwin after all? > > > > How about using the Windows binaries? Hmm... see - http://biolpc22.york.ac.uk/pub/2.8.9/install-msw-2.8.9.txt - http://www.haskell.org/haskellwiki/WxHaskell/Windows > It looks like that still tries to read "wx-config", which I don't know how > to generate. That's part of wxWidgets. Once you've got wxWidgets installed, you should be able to see a wx-config in its bin dir somewhere. -- Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow> PGP Key ID: 08AC04F9 |
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-02 15:10:16
|
Hi Eric, On Wed, Sep 2, 2009 at 4:36 AM, Eric Y. Kow <eri...@gm...> wrote: > Hi Lyle, > > On Wed, Sep 02, 2009 at 00:14:08 -0700, Lyle Kopnicky wrote: > > Is it not possible to install wxHaskell without Cygwin after all? > > How about using the Windows binaries? > The only binaries I see at http://www.wxwidgets.org/downloads/ are for Debian and Ubuntu. Everything else is source. Meanwhile Brian has done some work attempting to improve the > cabalisation of the wxcore package - http://github.com/bsl/wxcore > It looks like that still tries to read "wx-config", which I don't know how to generate. Thanks, Lyle |
From: Eric Y. K. <eri...@gm...> - 2009-09-02 11:36:48
|
Hi Lyle, On Wed, Sep 02, 2009 at 00:14:08 -0700, Lyle Kopnicky wrote: > Is it not possible to install wxHaskell without Cygwin after all? How about using the Windows binaries? Meanwhile Brian has done some work attempting to improve the cabalisation of the wxcore package - http://github.com/bsl/wxcore Maybe that will work better? -- Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow> PGP Key ID: 08AC04F9 |
From: Lyle K. <li...@qs...> - 2009-09-02 07:14:22
|
Hi folks, I'm trying to build a program using GHC that links statically to wxHaskell, so it can be easily distributed as a single file. Therefore I don't want any dependencies on Cygwin. I'm using Windows Vista 32-bit. I was able to download wxWidgets 2.8 and build it using Visual C++ 2008 Express Edition. But I don't know what to do next. I get this error from cabal: PS C:\wxWidgets-2.8.10> cabal install wx Resolving dependencies... warning: Unable to find wxWidgets configuration (wx-config). checking system: error: Unable to find the 'wx-config' program: wx-config Maybe you forgot to run 'make install' on wxWidgets? Otherwise, add the install directory of wx-config to your path. Or maybe you are trying to compile with Microsoft Visual C++? If so, you can specify that on the command line: For example: ./configure --with-msc cabal.exe: Error: some packages failed to install: wx-0.11.1.2 depends on wxcore-0.11.1.2 which failed to install. wxcore-0.11.1.2 failed during the configure step. The exception was: exit: ExitFailure 2 I don't see a program called wx-config, but I do see wx-config.in. I tried "nmake install" (Microsoft make) but nothing happened. It seems to me that running the configure script requires bash. Is it not possible to install wxHaskell without Cygwin after all? Thanks, Lyle |