HI Shelarcy, On 21/08/07, shelarcy <[EMAIL PROTECTED]> wrote: > > The problem is that we can't use nmake, because building on Windows > deeply depends on Visual C++ project files.
I've actually already almost solved this. I've factored out the wxc build from the top level makefile(*) and made it compatible with Visual Studio 2005 command line tools as well as GCC. This will enable a single makefile to be used for building wxC on all hosts OS. The Visual Studio project files are awkward to maintain because they require editing depending on the file locations chosen on build machine, and require irritating small changes whenever the underlying wxWidgets version changes. It has required a lot of work to get this working for all cases (I haven't rolled out the patch as I don't consider it fully tested as yet), but I do think that it represents a more easily maintainable way forward. What I'm trying to get to is a top level build system where all the user needs to do (once wxWidgets installed) is: runghc Setup.hs configure runghc Setup.hs build runghc Setup.hs install i.e. it will look just like a Cabal build even though large parts of the build are actually Makefiles. This should make things much simpler for newcomers as it's the same set of build commands as used on most Haskell projects these days. I'm more than 90% finished with this, and when it comes along it will represent a pretty large patch (so maybe Eric will be glad not to have to do a detailed review :-) on the build system. Regards Jeremy (*) There's a secondary reason for factoring out the wxc build from the wxHaskell build: a number of other languages (most of them in the FP church, if you define it reasonably broadly) use wxC as the basis for their wxWidgets bindings. In pretty much every case, the original Eiffel wxC implementation was forked, and then no-one has really maintained the C bindings. The wxHaskell implementation of wxC is far and away the most mature and best maintained C binding to wxWidgets (I checked the others - looking to see if we could bring in any code). By making wxC buildable separately from wxHaskell, maintainers of other wxWidgets bindings can make use of wxC more readily, and hopefully we can encourage maintainers of the other language bindings to contribute improvements to the C bindings in a single place... to the benefit of wxHaskell. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ wxhaskell-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wxhaskell-users
