Personal tools

WxHaskell/Windows

From HaskellWiki

< WxHaskell(Difference between revisions)
Jump to: navigation, search
m
(DLLs: Added a remark about using cygcheck)
(23 intermediate revisions by 5 users not shown)
Line 1: Line 1:
=== Building wxWidgets and wxc with Microsoft Visual C++ ===
+
== wxWidgets 2.9 and wxHaskell 0.90.x ==
   
The advantage of using Visual C++ is that the resulting libraries are smaller and faster than the gnu compiled ones. Furthermore, the debug version provides for automatic detection of memory leaks in the wxWidgets libraries and you get a warning when forgetting to deallocate wxWidgets objects. The drawback is that the configure scripts are not used and you will need to set some options manually.
+
{|border=1 style="border-collapse: collapse;"
  +
! Windows
  +
! Haskell Platform
  +
! wxWidgets
  +
|-
  +
|| 7 || 2011.2.0.1 || 2.9.3
  +
|-
  +
|}
   
If you want to use Visual C++ Express Edition, you must use Visual C++ 2008 Express Editions or higher. Because previous version requires [http://msdn2.microsoft.com/express/aa700755.aspx installing Microsoft Platform SDK] before building wxWidgets or wxHaskell.
 
   
We use the wxWidgets provided workspace directly:
+
Prerequisites:
  +
* [http://sourceforge.net/projects/mingw/files/Automated%20MinGW%20Installer MinGW] 5.1.6 and [http://downloads.sourceforge.net/mingw/MSYS-1.0.11.exe MSYS] 1.0.11 (these are the latest versions at the time of writing). You must select the C++ compiler option when installing MinGW.
   
* '''wxWidgets 2.4''': Open the <tt>$wxwin/src/wxWidgets.dsw</tt> workspace. Select menu &quot;<tt>Build/Set active configuration</tt>&quot; and select &quot;<tt>wxWidgets - win32 release unicode</tt>&quot; to build the (static) library. After compilation, you can also select &quot;<tt>wxWidgets - win32 debug unicode</tt>&quot; to build the debug version.
+
Environment variables:
* '''wxWidgets 2.6''': Open the <tt>$wxwin/build/msw/wx.dsw</tt> workspace. Select menu &quot;<tt>Build/Batch build</tt>&quot; and select all configurations by using the mouse and the <tt>shift</tt> key, when you click a marker, all configurations are deselected. Next you manually select the &quot;Unicode Release&quot; and &quot;Unicode Debug&quot; versions of all projects and press &quot;Build&quot;. Afterwards, press &quot;Save All&quot; to save all your mouse clicking work :-)
 
If you want to use [http://wxhaskell.sourceforge.net/doc/Graphics.UI.WXCore.Db.html database access] and [http://wxhaskell.sourceforge.net/doc/Graphics.UI.WXCore.OpenGL.html openGL canvas], you must edit <tt>$wxwin/include/msw/setup.h</tt>'s <tt>#define wxUSE_*</tt>(* is target feature name) from 0 to 1.
 
   
After building wxWidgets, you need to run <tt>configure</tt> for the wxHaskell library.
+
* CABAL_DIR: C:\Users\XXX\AppData\Roaming\cabal (Windows XP: C:\Documents and Settings\XXX\Application Data\cabal, or for all Windows versions: %APPDATA%\cabal)
  +
* GHC_VERSION: 7.0.3 (for our convenience)
  +
* WXC_VERSION: 0.90.0.2
  +
* WXWIN: C:\wxWidgets-2.9.3
  +
* WXCFG: gcc_dll\mswu
  +
* PATH: (add these) %WXWIN%\lib\gcc_dll;%WXWIN%;%CABAL_DIR%\wxc-%WXC_VERSION%\%GHC_VERSION%
   
<pre>&gt; cd $wxhaskell
+
Steps:
&gt; ./configure --with-msc</pre>
 
If you want to use the debug version of the library, use the <tt>--wxc-libname</tt> option too.
 
   
<pre>&gt; ./configure --with-msc --wxc-libname=wxcd</pre>
+
<ol>
After configuration, first run <tt>make</tt> command to generate stc_gen.* files.
+
<li> Download [http://wxwidgets.org/downloads wxWidgets 2.9.3 source]
  +
<li> Extract to C:\wxWidgets-2.9.3
  +
<li> [http://wiki.wxwidgets.org/Compiling_wxWidgets_with_MinGW Build wxWidgets-2.9.3]
  +
<br>I (who?) compiled it as follows: edit <tt>wxwidgets-src-dir\build\msw\config.gcc</tt> so that the following values are set:
  +
<pre>
  +
SHARED ?= 1
  +
BUILD ?= release
  +
</pre>
  +
Then (in cmd.exe, ''not'' bash):
  +
<pre>
  +
cd wxwidgets-src-dir\build\msw
  +
mingw32-make -f makefile.gcc
  +
</pre>
  +
<li> Download [https://sourceforge.net/projects/wxhaskell/files/wx-config-win/ wx-config.exe] (a new version for wxWidgets > 2.9) and copy it somewhere into your path, for instance via
  +
<pre>
  +
cp wx-config.exe %CABAL_DIR%\bin
  +
</pre>
  +
<li> Install the wxHaskell libraries
  +
<pre>
  +
cabal install wxdirect
  +
cabal install wxc
  +
cabal install wxcore
  +
cabal install wx
  +
</pre>
  +
</ol>
   
<pre>&gt; make</pre>
+
=== DLLs ===
Make will stop by following error.
 
   
<pre>&gt; make: *** No rule to make target `out/wxc/wxc-msw2.6.4-0.10.1.dll', needed by `wxc'. Stop.</pre>
+
In order to run a wxHaskell application, the following wxWidgets DLLs must be in the search path:
Then go <tt>$wxhaskell/wxc</tt> directory. Here, you need to adapt the <tt>wxc-&lt;em&gt;version&lt;/em&gt;.dsp</tt> project to reference the correct wxWidgets directory. Open the <tt>.dsp</tt> file in an editor and replace all occurrences of &quot;<tt>..\..\wxWindows-2.4.2</tt>&quot; (or &quot;<tt>..\..\wxWindows-2.6.4</tt>&quot;) or by the installed wxWidgets directory, i.e. <tt>$wxwin</tt>.
 
   
After adapting the project file, you can open the workspace <tt>wxc/wxc-&lt;em&gt;version&lt;/em&gt;.dsw</tt> and build the release and debug versions of the C wrapper library (if you use wxWidgets 2.6.4, you must choose &quot;Unicode Release&quot; or &quot;Unicode Debug&quot; instead of choosing just &quot;Release&quot; or &quot;Debug&quot;).
+
(If you built wxWidgets in directory wxWidgets-2.9.3,
  +
the following files can be found in wxWidgets-2.9.3\lib\gcc_dll\ (change revision as needed))
  +
* wxbase293u_gcc_custom.dll
  +
* wxbase293u_net_gcc_custom.dll
  +
* wxbase293u_xml_gcc_custom.dll
  +
* wxmsw293u_adv_gcc_custom.dll
  +
* wxmsw293u_aui_gcc_custom.dll
  +
* wxmsw293u_core_gcc_custom.dll
  +
* wxmsw293u_gl_gcc_custom.dll
  +
* wxmsw293u_html_gcc_custom.dll
  +
* wxmsw293u_propgrid_gcc_custom.dll
  +
* wxmsw293u_ribbon_gcc_custom.dll
  +
* wxmsw293u_richtext_gcc_custom.dll
  +
* wxmsw293u_stc_gcc_custom.dll
  +
* wxmsw293u_xrc_gcc_custom.dll
   
And finally! – you can run <tt>make</tt> in the <tt>$wxhaskell</tt> directory to build the Haskell libraries.
+
The following file can be found in directory wxc\dist\build\, after building package wxc in directory wxc:
  +
* wxc.dll
   
<pre>&gt; cd $wxhaskell
+
Furthermore, the following DLLs need to be in the search path (these can be found in directory "Haskell Platform\2012.2.0.0\mingw\bin\", or in ghc-7.4.2\mingw\bin\ if you installed the compiler only (change revision as needed)):
&gt; make
+
* libgcc_s_dw2-1.dll
&gt; make install
+
* libstdc++-6.dll
&gt; make wx
+
* mingwm10.dll
&gt; make wx-install</pre>
 
   
== User experiences ==
+
Some wxHaskell applications also require the following DLLs:
==== GHC 6.8.3, wxWidgets 2.6.4, wxHaskell 0.10.3 (binary) ====
+
* uuid.dll
  +
* perl510.dll
  +
* libaprutil-1.dll
   
# Download the wxhaskell binary from [http://sourceforge.net/project/showfiles.php?group_id=73133&package_id=73173&release_id=586065 sourceforge]
+
These DLLs can be obtained by installing [http://sourceforge.net/projects/xampp/ XAMPP]; the DLLs are in the directories:
# Unpack wxhaskell-*.zip. And double-click wxhaskell-*\bin\wxhaskell-register.bat.
+
* xampp\perl\site\lib\auto\APR\UUID
# wxhaskell-register.bat install wxHaskell to your system.
+
* xampp\perl\bin
  +
* xampp\apache\bin
   
==== Assumptions (a.k.a. what I have tested) ====
+
If there are still DLLs missing, you can find out which, using [http://cygwin.com/cygwin-ug-net/using-utils.html cygcheck] from the [http://www.cygwin.com/ Cygwin project]. Note, that you will get problems if you have both MinGW and Cygwin in your search path; it is best to specify the full path to cygcheck.exe.
   
* GHC 6.4.2 (Jason Dagit reports success with GHC 6.5 as well).
+
== wxWidgets 2.8 and wxHaskell 0.13.x ==
   
* Cygwin installation. See [http://wxhaskell.sourceforge.net/building-cygwin.html | wxHaskell cygwin page] for detail, but broadly, you need Cygwin bash and install binaries.
+
Follow [http://www.scribd.com/doc/38034374/20100923-WxHaskell-Setup SkyTreeBird's guide]. It which walks you through the basic steps
   
* wxWidgets built/installed in a path with no spaces in it. Actually you can use a path with spaces but there are a few rules. For example, I had ghc installed to this location:<br/><tt>C:\Program Files\Visual Haskell</tt><br/>So this required me to use the following configure command:<br/><tt>./configure --libdir=C:/Progra~1/Visual~1</tt><br/>
+
* wx-config
The two important things here are: 1) You must use the forward slash
+
* wxPack
and 2) you cannot use spaces.
+
* setting up environment variables
  +
* <code>cabal install wx</code>
   
Next I found that I needed to add <tt>C:\Program Files\Visual Haskell</tt> to
+
Note that the best way to refer to WxWidgets in your PATH is probably to use the WXWIN variable that you set, eg. <code>%WXWIN%/lib/gcc_dll</code>
my path so that the wxHaskell dlls could be located by windows.
 
   
* Environment variables:
+
The guide has been tested with the following configurations. Others may work too:
** PATH should include MinGW and Cygwin binary directories. MinGW must come before Cygwin in PATH.
 
** WXHASKELL environment var points to wxHaskell install directory.
 
** WXWIN environment directory points to wxWidgets install directory.
 
   
For more detailed information, see [http://biolpc22.york.ac.uk/pub/2.6.4/install-msw-2.6.4.txt Installing wxWidgets 2.6.4 on Microsoft Windows 9x/ME, Windows NT, Windows 2000, Windows XP, and Windows CE].
+
{|border=1 style="border-collapse: collapse;"
  +
! Windows
  +
! Haskell Platform
  +
! wxWidgets
  +
|-
  +
|| XP || 2010.2.0.0 || 2.8.10
  +
|-
  +
|| 7 || 2011.2.0.1 || 2.8.12
  +
|}
  +
  +
  +
=== DLLs ===
  +
  +
In order to run a wxHaskell application, the following DLLs must be in the search path:
  +
  +
* mingwm10.dll; this can be found in directory "Haskell Platform\2012.2.0.0\mingw\bin\", or in ghc-7.4.2\mingw\bin\ if you installed just the compiler (change revision as needed)
  +
  +
* wxmsw28u_gcc_custom.dll
  +
  +
  +
  +
=== Troubleshooting installation with cabal ===
  +
  +
These remarks refer to wx-0.13.2 and Haskell Platform 2011.4.0.0 on Windows 7.
  +
  +
Cabal package wx depends on wxcore which depends on wxdirect. By default cabal installs on a per user base, thus wxdirect.exe will be installed to <code>c:\Users\<YOUR NAME>\AppData\Roaming\cabal\bin\</code>. This folder must be in your <code>PATH</code> for <code>cabal install wxcore</code> to succeed.
  +
  +
Package wxcore-0.13.2 does not work well with wx-config revision 21 2006-10-19 (downloaded from [http://sites.google.com/site/wxconfig/ here] on Feb 2<sup>nd</sup> 2012). If <code>cabal install wxcore</code> fails with an output containing "Usage: wx-config [options]" try this:
  +
  +
* <code>cabal unpack wxcore</code>
  +
* <code>cd wxcore-0.13.2</code>
  +
* edit <code>Setup.hs</code> and comment out/remove the line containing <code>"wx-config" ["--version"]</code>
  +
* <code>runhaskell.exe Setup.hs configure --user</code>
  +
* <code>runhaskell.exe Setup.hs build</code>
  +
* <code>runhaskell.exe Setup.hs install</code>
  +
  +
Finally call <code>cabal install wx</code>.
   
 
== See also ==
 
== See also ==

Revision as of 18:02, 1 January 2013

Contents

1 wxWidgets 2.9 and wxHaskell 0.90.x

Windows Haskell Platform wxWidgets
7 2011.2.0.1 2.9.3


Prerequisites:

  • MinGW 5.1.6 and MSYS 1.0.11 (these are the latest versions at the time of writing). You must select the C++ compiler option when installing MinGW.

Environment variables:

  • CABAL_DIR: C:\Users\XXX\AppData\Roaming\cabal (Windows XP: C:\Documents and Settings\XXX\Application Data\cabal, or for all Windows versions: %APPDATA%\cabal)
  • GHC_VERSION: 7.0.3 (for our convenience)
  • WXC_VERSION: 0.90.0.2
  • WXWIN: C:\wxWidgets-2.9.3
  • WXCFG: gcc_dll\mswu
  • PATH: (add these) %WXWIN%\lib\gcc_dll;%WXWIN%;%CABAL_DIR%\wxc-%WXC_VERSION%\%GHC_VERSION%

Steps:

  1. Download wxWidgets 2.9.3 source
  2. Extract to C:\wxWidgets-2.9.3
  3. Build wxWidgets-2.9.3
    I (who?) compiled it as follows: edit wxwidgets-src-dir\build\msw\config.gcc so that the following values are set:
     SHARED ?= 1
     BUILD ?= release
    

    Then (in cmd.exe, not bash):

     cd wxwidgets-src-dir\build\msw
     mingw32-make -f makefile.gcc
    
  4. Download wx-config.exe (a new version for wxWidgets > 2.9) and copy it somewhere into your path, for instance via
    cp wx-config.exe %CABAL_DIR%\bin
    
  5. Install the wxHaskell libraries
    cabal install wxdirect
    cabal install wxc
    cabal install wxcore
    cabal install wx
    

1.1 DLLs

In order to run a wxHaskell application, the following wxWidgets DLLs must be in the search path:

(If you built wxWidgets in directory wxWidgets-2.9.3, the following files can be found in wxWidgets-2.9.3\lib\gcc_dll\ (change revision as needed))

  • wxbase293u_gcc_custom.dll
  • wxbase293u_net_gcc_custom.dll
  • wxbase293u_xml_gcc_custom.dll
  • wxmsw293u_adv_gcc_custom.dll
  • wxmsw293u_aui_gcc_custom.dll
  • wxmsw293u_core_gcc_custom.dll
  • wxmsw293u_gl_gcc_custom.dll
  • wxmsw293u_html_gcc_custom.dll
  • wxmsw293u_propgrid_gcc_custom.dll
  • wxmsw293u_ribbon_gcc_custom.dll
  • wxmsw293u_richtext_gcc_custom.dll
  • wxmsw293u_stc_gcc_custom.dll
  • wxmsw293u_xrc_gcc_custom.dll

The following file can be found in directory wxc\dist\build\, after building package wxc in directory wxc:

  • wxc.dll

Furthermore, the following DLLs need to be in the search path (these can be found in directory "Haskell Platform\2012.2.0.0\mingw\bin\", or in ghc-7.4.2\mingw\bin\ if you installed the compiler only (change revision as needed)):

  • libgcc_s_dw2-1.dll
  • libstdc++-6.dll
  • mingwm10.dll

Some wxHaskell applications also require the following DLLs:

  • uuid.dll
  • perl510.dll
  • libaprutil-1.dll

These DLLs can be obtained by installing XAMPP; the DLLs are in the directories:

  • xampp\perl\site\lib\auto\APR\UUID
  • xampp\perl\bin
  • xampp\apache\bin

If there are still DLLs missing, you can find out which, using cygcheck from the Cygwin project. Note, that you will get problems if you have both MinGW and Cygwin in your search path; it is best to specify the full path to cygcheck.exe.

2 wxWidgets 2.8 and wxHaskell 0.13.x

Follow SkyTreeBird's guide. It which walks you through the basic steps

  • wx-config
  • wxPack
  • setting up environment variables
  • cabal install wx

Note that the best way to refer to WxWidgets in your PATH is probably to use the WXWIN variable that you set, eg. %WXWIN%/lib/gcc_dll

The guide has been tested with the following configurations. Others may work too:

Windows Haskell Platform wxWidgets
XP 2010.2.0.0 2.8.10
7 2011.2.0.1 2.8.12


2.1 DLLs

In order to run a wxHaskell application, the following DLLs must be in the search path:

  • mingwm10.dll; this can be found in directory "Haskell Platform\2012.2.0.0\mingw\bin\", or in ghc-7.4.2\mingw\bin\ if you installed just the compiler (change revision as needed)
  • wxmsw28u_gcc_custom.dll


2.2 Troubleshooting installation with cabal

These remarks refer to wx-0.13.2 and Haskell Platform 2011.4.0.0 on Windows 7.

Cabal package wx depends on wxcore which depends on wxdirect. By default cabal installs on a per user base, thus wxdirect.exe will be installed to c:\Users\<YOUR NAME>\AppData\Roaming\cabal\bin\. This folder must be in your PATH for cabal install wxcore to succeed.

Package wxcore-0.13.2 does not work well with wx-config revision 21 2006-10-19 (downloaded from here on Feb 2nd 2012). If cabal install wxcore fails with an output containing "Usage: wx-config [options]" try this:

  • cabal unpack wxcore
  • cd wxcore-0.13.2
  • edit Setup.hs and comment out/remove the line containing "wx-config" ["--version"]
  • runhaskell.exe Setup.hs configure --user
  • runhaskell.exe Setup.hs build
  • runhaskell.exe Setup.hs install

Finally call cabal install wx.

3 See also