[wxhaskell-users] darcs patch: Add a Cabal file for wxcore. (and 2 more)
Any comments or complaints, Jeremy?
Otherwise I'm pushing this tomorrow.
If it actually works, we ought to put wxhaskell on hackage.
Thu Feb 14 17:50:50 GMT 2008 Eric Kow [EMAIL PROTECTED]
* Add a Cabal file for wxcore.
This uses the Make build-type, so we still need our configure file
and the makefile.
Thu Feb 14 17:53:29 GMT 2008 Eric Kow [EMAIL PROTECTED]
* Add cabal file for high level directory.
Thu Feb 14 17:55:21 GMT 2008 Eric Kow [EMAIL PROTECTED]
* Update online build instructions for Cabal.
New patches:
[Add a Cabal file for wxcore.
Eric Kow [EMAIL PROTECTED]**20080214175050
This uses the Make build-type, so we still need our configure file
and the makefile.
] {
addfile ./Setup.lhs
hunk ./Setup.lhs 1
+#!/usr/bin/env runhaskell
+
+ import Distribution.Make
+ main = defaultMain
hunk ./configure 328
echo Ignoring --cache option; this option must be the first (and only) option.
echo ;;
+ --with-hc=*)
+ hc=$arg;;
-hc=*|--hc=*)
hc=$arg;;
-hcpkg=*|--hcpkg=*)
hunk ./makefile 274
#--
# Install (unfortunately with extra clauses for the mac)
#--
+copy:
+ $(MAKE) install prefix=$(destdir)/$(prefix) \
+bindir=$(destdir)/$(bindir) \
+libdir=$(destdir)/$(libdir) \
+datadir=$(destdir)/$(datadir) \
+libexecdir=$(destdir)/$(libexecdir)
+
+register: wxcore-register
+
install: wxcore-install-files wxcore-register
@echo --
@echo Done with wxcore...
addfile ./wxhaskell-core.cabal
hunk ./wxhaskell-core.cabal 1
+Name: wxcore
+Version:0.10.1
+License:wxWindows
+License-file: license.txt
+Author: Daan Leijen
+Flag splitBase
+Description: Choose the new smaller, split-up base package.
+
+Library
+if flag(splitBase)
+build-depends: base = 3
+else
+build-depends: base 3
+Build-Type: Make
+Description:wxHaskell core
+Maintainer: wxhaskell-users@lists.sourceforge.net
+Exposed-Modules:
+ Graphics.UI.WXCore
+ Graphics.UI.WXCore.WxcObject
+ Graphics.UI.WXCore.Draw
+ Graphics.UI.WXCore.WxcClassTypes
+ Graphics.UI.WXCore.DragAndDrop
+ Graphics.UI.WXCore.WxcDefs
+ Graphics.UI.WXCore.Process
+ Graphics.UI.WXCore.Print
+ Graphics.UI.WXCore.WxcClassesMZ
+ Graphics.UI.WXCore.Events
+ Graphics.UI.WXCore.Frame
+ Graphics.UI.WXCore.IntMap
+ Graphics.UI.WXCore.Layout
+ Graphics.UI.WXCore.Controls
+ Graphics.UI.WXCore.Types
+ Graphics.UI.WXCore.WxcClassesAL
+ Graphics.UI.WXCore.Dialogs
+ Graphics.UI.WXCore.Db
+ Graphics.UI.WXCore.WxcTypes
+ Graphics.UI.WXCore.Image
+ Graphics.UI.WXCore.WxcClasses
+ Graphics.UI.WXCore.OpenGL
+ Graphics.UI.WXCore.WxcClassInfo
+ Graphics.UI.WXCore.Defines
+
}
[Add cabal file for high level directory.
Eric Kow [EMAIL PROTECTED]**20080214175329] {
addfile ./wx/license.txt
hunk ./wx/license.txt 1
-
+--
+PREAMBLE
+
+The wxHaskell libraries are distributed under the wxWindows library
+license. The documentation is subject to the wxWidgets documentation
+license.
+
+See http://www.wxwidgets.org/newlicen.htm; for the legal description
+of the license, which is also included in this document.
+
+The wxWindows library licence is essentially the L-GPL (Library General
+Public Licence), with an exception stating that derived works in binary
+form may be distributed on the user's own terms. This means that it is
+possible to create commercial software with this library without paying
+royalties or disclosing source code. This is a solution that satisfies
+those who wish to produce GPL'ed software using wxHaskell, and also
+those producing proprietary software.
+
+This library is distributed in the hope that it will be useful, but
+WITHOUT ANY WARRANTY; without even the implied warranty of
+MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the wxWidgets
+library license for more details.
+
+
+--
+ WXWINDOWS LIBRARY LICENCE
+ TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+ This library is free software; you can redistribute it and/or modify it
+ under the terms of the GNU Library General Public Licence as published by
+ the Free Software Foundation; either version 2 of the Licence, or (at
+ your option) any later version.
+
+ This library is distributed in the hope that it will be useful, but
+ WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Library
+ General Public Licence for more details.
+
+ You should have received a copy of the GNU Library General Public
[wxhaskell-users] wxhaskell, cabal, and linux
I have several libraries on hackage that depend on wxhaskell. Because wxhaskell is not itself on hackage, my libraries won't compile and won't haddock there. I'd really like to have cross-library haddocks all working. Is Cabal for wxhaskell in the works? Are there roadblocks? If Ross could build wxhaskell (both libs and docs) on the Linux machine that hosts hackage, then he could hack around lack of Cabal building. But he's having trouble. What version of wxhaskell is recommended for Linux? Does it build successfully? Is there anyone who would help Ross through the process? Thanks, - Conal -- Forwarded message -- From: Conal Elliott [EMAIL PROTECTED] Date: Thu, Feb 14, 2008 at 10:12 AM Subject: Re: off-world libs docs To: Ross Paterson [EMAIL PROTECTED] Thanks. I'll ask around. - Conal On Thu, Feb 14, 2008 at 10:07 AM, Ross Paterson [EMAIL PROTECTED] wrote: On Wed, Feb 13, 2008 at 10:25:30AM -0800, Conal Elliott wrote: Some of my packages use wxhaskell, which is not on hackage. That means those libs fail to compile *and* to produce haddock docs on hackage. I love the idea of people browsing through lib docs, following links from one lib to another to another. And I don't know how to get there. Any ideas? Perhaps one improvement would be to run haddock even when compiling fails -- assuming there's a place on hackage to deposit the .haddock files or a way to find them off of hackage. Or, maybe rely on folks to make sure all of their dependencies get moved onto hackage. I don't know why wxhaskell is not there. I don't see gtk2hs there either. It seems from the sourceforge page that someone is moving on wxhaskell with the aim of turning it into a Cabal package, which could then join the party, but I don't know what the timescale is. In the meantime, I could hack around it (as I did with base), but I need to be able to build wxhaskell and its documentation with ghc 6.8.2 and haddock2 on Linux, which I've not managed in my initial attempts. Which version of wxhaskell is preferred, and do know of anyone who has done this? Ross - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ wxhaskell-users mailing list wxhaskell-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wxhaskell-users
Re: [wxhaskell-users] wxhaskell, cabal, and linux
Hi Conal, On 14/02/2008, Conal Elliott [EMAIL PROTECTED] wrote: I have several libraries on hackage that depend on wxhaskell. Because wxhaskell is not itself on hackage, my libraries won't compile and won't haddock there. I'd really like to have cross-library haddocks all working. Is Cabal for wxhaskell in the works? Are there roadblocks? I just sent a cabalisation patch about 15 minutes ago. It's not yet applied, but you can give it a try. The wxcore bit just wraps around the makefile and configure script. -- Eric Kow http://www.nltg.brighton.ac.uk/home/Eric.Kow PGP Key ID: 08AC04F9 - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ wxhaskell-users mailing list wxhaskell-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wxhaskell-users
