Build locally (was: Re: [wxhaskell-users] Re: [Haskell] Announce: wxHaskell 0.6)

[Daan L. <daa...@xs...>]

On Thu, 1 Apr 2004 02:43:09 -0500, Dylan Thurston <dp...@pe...> wrote:

> On Wed, Mar 03, 2004 at 01:50:58PM +0100, Daan Leijen wrote:
>> >I was playing during the 0.30.4 but could not solve sandbox problem since
>> >wxhaskell writes into /usr/lib.
>>
>> This is easily solved by giving the "--prefix" option to configure. See
>> the "building" page on the wxHaskell website. (wxhaskell normally installs
>> whereever you install wxWidgets).
>
> No, the wxhaskell install also writes to the GHC packages file, which
> is at /usr/lib/ghc-6.2/package.conf on my system.

You should use the "--package-conf" option to configure. Use "configure --help"
to see all options.


In general, to build locally, I use something like:

> ./configure --prefix=~/local/wxhaskell --package-conf=~/packages

Use "configure --help" to see all options.
(Note that you can only use "~" with the latest cvs, use /home/name to circumvent this)

If you also build wxWidgets locally:

> ../configure --prefix=/home/daan/local/wxGTK-2.4.2 --disable-shared

(Note "--disable-shared" is only recommended for the latest CVS version of wxhaskell (version 0.7))
Now, you can use for wxhaskell:

> ./configure --wx-config=/home/daan/local/wxGTK-2.4.2/bin/wx-config             --prefix=/home/daan/local/wxhaskell-gtk2.4.2 --package-conf=/home/daan/packages

And than you can build multiple version next to each other (although you can only
register one version with ghc each time).

Note that you can use "make install", and "make uninstall" to test each version seperately.

(with the latests CVS (version 0.7) the makefile knows about "DESTDIR", so you could
sandbox that way too. There is also a "make install-files" that won't register the package.
See "make help" for all targets.)

All the best,
  Daan.

Btw. I am currently in the process of releasing version 0.7, which will include rpm's this time :-)