Re: [wxhaskell-devel] Windows
Hi Brian, On Thu, 12 Nov 2009 11:54 -0600, Brian Lewis br...@lorf.org wrote: WxcClassInfo is in the exported modules list, but its source is generated by wxdirect into dist/build/autogen. I added dist/build/autogen to hs-source-dirs and I think it's working. Please add that line or pull my repo and try again. This fails as well. The error message this time is: ERROR: wxcore-0.12.1.1.tar.gz: 400 Error in upload 400 Error in upload 'hs-source-dirs: dist/build/autogen' points inside the 'dist' directory. This is not reliable because the location of this directory is configurable by the user (or package manager). In addition the layout of the 'dist' directory is subject to change in future versions of Cabal. I think I'll try putting the autogens in src. This should make things work while we try to find a better way of approaching this. Jeremy -- Jeremy O'Donoghue jeremy.odonog...@gmail.com -- 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-devel mailing list wxhaskell-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wxhaskell-devel
Re: [wxhaskell-devel] Windows
For me, wxcore 0.12.1.1 on hackage fails to build for lack of stc_gen.cpp. It seems to be in darcs, though. -- 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-devel mailing list wxhaskell-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wxhaskell-devel
Re: [wxhaskell-devel] Windows
Hi Brian, 2009/11/13 Brian Lewis br...@lorf.org: For me, wxcore 0.12.1.1 on hackage fails to build for lack of stc_gen.cpp. It seems to be in darcs, though. Working on the problem now. Will let you all know when I have something which works - believe I am fairly close now, although it's late here :-( Jeremy -- 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-devel mailing list wxhaskell-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wxhaskell-devel
Re: [wxhaskell-devel] Windows
The problem, of course, being that stc.cpp includes stc_gen.cpp. For now I'm going to put it into extra-source-files. Didn't spot that before upload, and the cabal verifier obviously couldn't. We should try to find a better way to do this, but for now this should be OK. Jeremy 2009/11/13 Jeremy O'Donoghue jeremy.odonog...@gmail.com: Hi Brian, 2009/11/13 Brian Lewis br...@lorf.org: For me, wxcore 0.12.1.1 on hackage fails to build for lack of stc_gen.cpp. It seems to be in darcs, though. Working on the problem now. Will let you all know when I have something which works - believe I am fairly close now, although it's late here :-( Jeremy -- 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-devel mailing list wxhaskell-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wxhaskell-devel
Re: [wxhaskell-devel] Windows
Hi all, [Eric - note question aimed your way, buried near the bottom] 2009/11/10 Brian Lewis br...@lorf.org: On Tuesday, 10.11.09 at 12:42, Jeremy O'Donoghue wrote: One good option may be to commit the code 'as-is' to enable simple cabal install of wxHaskell, and work on putting back the features we have (temporarily) lost. If basic functionality is still there, I really favor doing it this way, because projects that are hard to install are in the danger zone. I agree with Brian and Eric on this and no-one else has commented, so I have committed the updates to the darcs repo. I've pulled a clean build and it functions just as expected, but... I'd like to get official wxdirect, wxcore, wx repos in order, maybe bumping version numbers as appropriate, and post something to -cafe about wxhaskell being truly installable via cabal. I hope this will spur interest. I would really like to see this library in good shape. I think the most important thing right now is to lower the barrier to using and developing on the project. While the darcs repo is now in order (with a version bump to 0.12.1.1 to signify that we are fully cabalized), I'm failing to create a cabal sdist package for wxcore. The error is: $ WXWIN=/c/utils/wxWidgets-2.8.10 WXCFG=gcc_dll/mswu runhaskell Setup.hs sdist Building source dist for wxcore-0.12.1.1... Setup.hs: Error: Could not find module: Graphics.UI.WXCore.WxcClassInfo with any suffix: [gc,chs,hsc,x,y,ly,cpphs,hs,lhs] I remember that we had some trouble with this last time. I thought the 'extra-tmp-files' stanza indicated that we don't need these files in the sdist. Eric, you fixed this for me last time. What did you do? Happy to upload once I have fixed this - wxdirect is already uploaded, and I'll do wx in a few moments. Once I've verified the whole chain using 'cabal install wx' on a clean computer, I'll make the announcements and update the wiki. It will be a pleasure to simplify the install instructions :-) Regards Jeremy -- 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-devel mailing list wxhaskell-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wxhaskell-devel
Re: [wxhaskell-devel] Windows
On Thu, Nov 12, 2009 at 14:11:17 +, Jeremy O'Donoghue wrote: $ WXWIN=/c/utils/wxWidgets-2.8.10 WXCFG=gcc_dll/mswu runhaskell Setup.hs sdist Building source dist for wxcore-0.12.1.1... Setup.hs: Error: Could not find module: Graphics.UI.WXCore.WxcClassInfo with any suffix: [gc,chs,hsc,x,y,ly,cpphs,hs,lhs] I remember that we had some trouble with this last time. I thought the 'extra-tmp-files' stanza indicated that we don't need these files in the sdist. Eric, you fixed this for me last time. What did you do? I think I replied too soon. The problem looks like an interaction between the fact that we expose our autogenerated modules and the fact that we generate them in a non-src directory (which is nice to do). One thing which makes the cabal sdist go is to change Setup.hs so that we no longer use autogen, but the source directory (slash haskell). I wonder if there is a better way though, for example, having a module that imports these autogen'ed modules and re-exports them. This would avoid dumping stuff into src -- Eric Kow http://www.nltg.brighton.ac.uk/home/Eric.Kow PGP Key ID: 08AC04F9 pgpaY1ohpXLcO.pgp Description: PGP signature -- 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-devel mailing list wxhaskell-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wxhaskell-devel
Re: [wxhaskell-devel] Windows
Hi Eric, 2009/11/12 Eric Y. Kow eric@gmail.com: I think I replied too soon. The problem looks like an interaction between the fact that we expose our autogenerated modules and the fact that we generate them in a non-src directory (which is nice to do). Yup - discovered that when I tried it :-( It's neat, but to be honest the old flex/bison user in me doesn't find it very offensive to generate code in src, provided that the clean target is implemented nicely. It has the advantage, for anyone working on the source code, of keeping everything nicely together. One thing which makes the cabal sdist go is to change Setup.hs so that we no longer use autogen, but the source directory (slash haskell). I wonder if there is a better way though, for example, having a module that imports these autogen'ed modules and re-exports them. This would avoid dumping stuff into src Does it solve the problem? I couldn't find any documentation on the extra-tmp-files: stanza, so I'm not really sure what it does. I suspect that the root cause of the problem is that we are trying to export modules which do not exist in a clean directory structure. Is it worth asking the cabal guys what they would suggest in this case? Jeremy -- 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-devel mailing list wxhaskell-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wxhaskell-devel
Re: [wxhaskell-devel] Windows
On Thursday, 12.11.09 at 14:11, Jeremy O'Donoghue wrote: Setup.hs: Error: Could not find module: Graphics.UI.WXCore.WxcClassInfo with any suffix: [gc,chs,hsc,x,y,ly,cpphs,hs,lhs] WxcClassInfo is in the exported modules list, but its source is generated by wxdirect into dist/build/autogen. I added dist/build/autogen to hs-source-dirs and I think it's working. Please add that line or pull my repo and try again. -- 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-devel mailing list wxhaskell-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wxhaskell-devel
Re: [wxhaskell-devel] Windows
On Tuesday, 10.11.09 at 12:42, Jeremy O'Donoghue wrote: One good option may be to commit the code 'as-is' to enable simple cabal install of wxHaskell, and work on putting back the features we have (temporarily) lost. If basic functionality is still there, I really favor doing it this way, because projects that are hard to install are in the danger zone. I'd like to get official wxdirect, wxcore, wx repos in order, maybe bumping version numbers as appropriate, and post something to -cafe about wxhaskell being truly installable via cabal. I hope this will spur interest. I would really like to see this library in good shape. I think the most important thing right now is to lower the barrier to using and developing on the project. -- 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-devel mailing list wxhaskell-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wxhaskell-devel
