Hello Jeremy. I was replying to the list but only your address got in at first.
So, I was updating wxHaskell targeting the stable wxWidgets 2.8.12 branch. After knowing wx-config had to be updated, I opted to build wxHaskell targeting 2.9 instead. I managed to get some progress. Compiled wx-config-win and set environment variables in windows. They were already set for wxWidgets 2.8.12. Pointed 'WXWIN' to wxWidgets-svn directory and 'WXCFG' to gcc_dll/mswu. Right now I am stuck with compiling wxc with cabal install. Cabal configure warned about missing debug libraries. After building them I have this one left that I don't know how to build. E:\Dev\Repo\wxhaskell-dev-darcs\wxhaskell-dev-v14patch\wxc>cabal configure Resolving dependencies... Configuring wxc-0.1... Configuring wxc to build against wx 2.9 setup.exe: Missing dependency on a foreign library: * Missing C library: wxmsw29ud_all This problem can usually be solved by installing the system package that provides this library (you may need the "-dev" version). If the library is already installed but in a non-standard location then you can use the flags --extra-include-dirs= and --extra-lib-dirs= to specify where it is. On 1 February 2012 17:08, Jeremy O'Donoghue <jeremy.odonog...@gmail.com> wrote: > Hi Paulo > > [Replying to all] > First, apologies that it has taken so long for you to fail to get going. I > am going to try to cover both wxWidgets 2.8.12 and 2.9.x approaches in the > same mail. Please feel free to choose whichever you prefer. I assume that > you are working on Windows, based on the output you have pasted. > On 1 February 2012 16:03, Paulo Pocinho <poci...@gmail.com> wrote: >> >> Trying to follow up with the latest stable version of wxHaskell 0.13.2 >> (based on wxWidgets 2.8.12). I run straight into trouble using the >> wx-config tool, preventing me to update the package - it does not >> work. > > > On Windows there is no wx-config supplied with wxWidgets. There is a > workaround, which is to use wx-config-win (found at > http://code.google.com/p/wx-config-win/). This is a C++ implementation of > wx-config for Windows targets. The version on Google Code is OK for use with > wxHaskell 0.13.2, but does not work for the latest code. > > You need to make sure that the WXWIN environment variable is pointing to > your wxWidgets install and that WXCFG points to the directory containing > your build.cfg. In my case (i.e. what I have tested) this is gcc_dll\mswu. > > If you have the above configuration with wx-config.exe from the Google code > site, cabal install wx should work. > >> >> Then I found out about the latest development. Pulled the sources from >> http://darcsden.com/kowey/wxhaskell - packed and installed that >> wx-config with cabal and still no luck. > > > This one won't work - it has only been tested for wxWidgets 2.9.x - and we > probably won't use it moving forward, as it needs quite a bit of work to > make it function completely correctly. > >> >> As last resort, I checked out from Dave Tapley. Patched it with >> Jeremy's diff and tried to build that version against wxWidgets 2.9 >> (compiled from svn sources). Now, I am lost in a circular dependency: > > > >> >> E:\Dev\Repo\wxhaskell-dev-darcs\wxhaskell-dev-v14patch\wxcore>cabal >> configure >> Resolving dependencies... >> Configuring wxcore-0.14... >> setup.exe: At least the following dependencies are missing: >> wxc -any >> >> E:\Dev\Repo\wxhaskell-dev-darcs\wxhaskell-dev-v14patch\wxcore>cd ..\wxc >> >> E:\Dev\Repo\wxhaskell-dev-darcs\wxhaskell-dev-v14patch\wxc>cabal configure >> Resolving dependencies... >> Configuring wxc-0.1... >> setup.exe: This version of wxcore requires wx 2.9 to be available > > > This is the root of your problem. > > A couple of possibilities: > > You may have WXWIN and WXCFG environment variables pointing to your > wxWidgets 2.8.x install (or not pointing anywhere at all) > You need the updated version of wx-config-win I put together to get all of > the correct configuration data for a wxWidgets 2.9 configuration.If you > don't have it, it was attached to the following message: > http://article.gmane.org/gmane.comp.lang.haskell.wxhaskell.devel/807 . You > will need to compile(*) the CPP file. If you don't have a C++ compiler, I > can also send you an executable - assuming that none of the mail tools block > it, that is. > > > > (*) Nothing very difficult. I think gcc -o wx-config.exe wx-config-win.cpp > should do it. > >> >> >> E:\Dev\Repo\wxhaskell-dev-darcs\wxhaskell-dev-v14patch\wxc>cd ..\wx >> >> E:\Dev\Repo\wxhaskell-dev-darcs\wxhaskell-dev-v14patch\wx>cabal configure >> Resolving dependencies... >> Configuring wx-0.14... >> cabal: At least the following dependencies are missing: >> wxcore >=0.14 >> >> It's been a great adventure though. Thanks for everyone working on this! >> >> >> On 31 January 2012 16:32, Jeremy O'Donoghue <jeremy.odonog...@gmail.com> >> wrote: >> > Hi all, >> > >> > Attached are patches which enable me to build and Dave's repo on >> > Windows. I >> > have built and run most of the samples and test cases (including OpenGL, >> > STC >> > and PropertyGrid) >> > I also included Nicholas Tung's patch from a couple of days back to >> > support >> > GHC 7.2.2 by adding some FlexibleInstances pragmas. >> > >> > The remaining issue on Windows is that GHCi is not working as it should. >> > I >> > will look at this next. >> > On 25 January 2012 15:33, Dave Tapley <duked...@gmail.com> wrote: >> >> >> >> On 22 January 2012 00:37, Jeremy O'Donoghue >> >> <jeremy.odonog...@gmail.com> >> >> wrote: >> >>> >> >>> I now have wxC building on Windows. Details below and patches >> >>> attached. >> >> >> >> >> >> Excellent! >> >> I'll take a look. >> >> >> >>> >> >>> I am now failing to build wxcore. This is faling to find the wxc >> >>> header >> >>> files on Windows (it is looking for them in ./include/wxc). I notice >> >>> that >> >>> Dave has already marked the wxcInstallDir function as dubious, so I'll >> >>> start >> >>> looking there when it isn't past midnight (a bad time to start >> >>> anything, >> >>> IME). >> >> >> >> >> >> Mmm, I'm sorry about that. >> >> I actually went for this solution because I'm using cabal-dev to work >> >> on >> >> wxHaskell (so I can keep the hackage wxHaskell in my system cabal pkg >> >> conf): >> >> I needed a way to find the wxC headers (which obviously should be part >> >> of >> >> the wxC package) during the wxcore configure (because wxdirect (called >> >> by >> >> wxcore) needs them to generate some Haskell source (the FFI bindings)). >> > >> > >> > The solution turned out to be simpler than I expected: the working code >> > for >> > Linux was using System.Directory.Posix, when System.Directory will get >> > you >> > the same thing, but internally select between System.Directory.Posix and >> > System.Directory.Windows. No prizes for guessing which you need on >> > Windows >> > :-) >> > >> >> >> >> >> >> Whilst I did mark wxcInstallDir as dubious, I do quite like the idea of >> >> having cabal work out which version of wxC it is using to satisfy >> >> wxcore's >> >> dependency, and then linking against exactly that version's header >> >> files. >> >> The only alternatives I can think of are: >> >> >> >> 1. Enforce that wxC is installed as a system or user shared library and >> >> find/version it up as we would any other external library (this would >> >> be >> >> required if we stopped using cabal). >> >> >> >> 2. Provide some other (auto-guesswork-or-specify-on-command-line) >> >> mechanism to tell wxcore: "can you configure yourself with the wxC >> >> headers >> >> here, and link against this shared library". >> > >> > >> > Actually, after some reflection, I don't think wxcInstallDir is dubious >> > at >> > all. It is, I think, using a documented Cabal API, and it works on all >> > Cabal >> > platforms. >> > >> > One area where we do have an issue is that wxc.dll gets installed >> > somewhere >> > no sane human being would evenr look to find it. I think the solution >> > will >> > be to do a skeleton wxHaskell project Cabal file which pulls all of the >> > dlls >> > from their install directory and copies them to dist/build, or something >> > similar. >> > >> > Regards >> > Jeremy >> > >> > >> > ------------------------------------------------------------------------------ >> > Keep Your Developer Skills Current with LearnDevNow! >> > The most comprehensive online learning library for Microsoft developers >> > is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, >> > Metro Style Apps, more. Free future releases when you subscribe now! >> > http://p.sf.net/sfu/learndevnow-d2d >> > _______________________________________________ >> > wxhaskell-devel mailing list >> > wxhaskell-devel@lists.sourceforge.net >> > https://lists.sourceforge.net/lists/listinfo/wxhaskell-devel >> > >> >> >> ------------------------------------------------------------------------------ >> Keep Your Developer Skills Current with LearnDevNow! >> The most comprehensive online learning library for Microsoft developers >> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, >> Metro Style Apps, more. Free future releases when you subscribe now! >> http://p.sf.net/sfu/learndevnow-d2d >> _______________________________________________ >> wxhaskell-devel mailing list >> wxhaskell-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wxhaskell-devel > > ------------------------------------------------------------------------------ Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d _______________________________________________ wxhaskell-devel mailing list wxhaskell-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wxhaskell-devel
