On 7 March 2012 14:38, Eric Kow wrote:
> Note that this work is very far behind Dave and Jeremy's efforts. I'm
> hoping it'll eventually be obsolete in some future when we've merged
> everything we need to merge.
>
I'm in the process of trying to pull this all together.
One piece of good news
On 9 Mar 2012, at 09:42, Frodo Kenny wrote:
> This could be the problem that the "install-name" of a shared library
> on the mac needs to be set to the correct absolute path to be able to
> link.
> I encountered the same problem with the shared library version of
> wxHaskell from Dave's branch (al
This could be the problem that the "install-name" of a shared library
on the mac needs to be set to the correct absolute path to be able to
link.
I encountered the same problem with the shared library version of
wxHaskell from Dave's branch (allowing ghci to work with wx!). That
version is working
On Mar 7, 2012, at 15:38 , Eric Kow wrote:
> Sorry, just one more follow-up.
>
> 4. I've published my branch at http://darcsden.com/kowey/wxhaskell-osx64 (in
> the process I've renamed the two WIP patches and simplified the build to only
> look for wxWidgets 2.9)
We have spent a couple of hou
Hi,
On 7 Mar 2012, at 15:39, S D Swierstra wrote:
> setup: Missing dependencies on foreign libraries:
> * Missing C libraries: wx_baseu-2.9, wx_baseu_net-2.9, wx_baseu_xml-2.9,
> wx_osx_cocoau_core-2.9, wx_osx_cocoau_adv-2.9, wx_osx_cocoau_qa-2.9,
> wx_osx_cocoau_html-2.9, wx_osx_cocoau_webview-2.
Sorry, just one more follow-up.
4. I've published my branch at http://darcsden.com/kowey/wxhaskell-osx64 (in
the process I've renamed the two WIP patches and simplified the build to only
look for wxWidgets 2.9)
Note that this work is very far behind Dave and Jeremy's efforts. I'm hoping
it'll
Hi all,
Just a couple of minor follow-ups on the issue of getting wxHaskell to work on
MacOS X Lion
1. I noticed this piece of text from the wxWidgets wiki [wxWidgets]:
If you want 64-bit wxWidgets on OS X you'll need 2.9+ and configure
-with-osx_cocoa - see below; but remember that 2.9 is not
On Mon, 27 Feb 2012, Eric Kow wrote:
On 27 Feb 2012, at 15:38, Eric Kow wrote:
darcs get --lazy http://code.haskell.org/wxhaskell
the-patch-you-downloaded.dpatch
cd wxhaskell
darcs apply -i ~/foo/the-patch-you-downloaded.dpatch
Oops, that's darcs get --lazy --context
The idea is that da
Hi,
On Mon, Feb 27, 2012 at 4:42 PM, Eric Kow wrote:
>
>> darcs get --lazy http://code.haskell.org/wxhaskell
>> the-patch-you-downloaded.dpatch
>> cd wxhaskell
>> darcs apply -i ~/foo/the-patch-you-downloaded.dpatch
>
Thank you very much, with this process it appears to work, although
there are
On 27 Feb 2012, at 15:38, Eric Kow wrote:
> darcs get --lazy http://code.haskell.org/wxhaskell
> the-patch-you-downloaded.dpatch
> cd wxhaskell
> darcs apply -i ~/foo/the-patch-you-downloaded.dpatch
>
Oops, that's darcs get --lazy --context
The idea is that darcs will then grab and then un
Sarah,
The good news is that it *can* be done. I know because I'm on Lion, and I'm
using wxHaskell.
On 25 Feb 2012, at 14:58, Sarah Brofeldt wrote:
> I've been trying frantically to get a working setup of wxHaskell and
> wxWidgets on my Mac recently, but to no avail. I was wondering if
> anyone
Hello everyone,
I've been trying frantically to get a working setup of wxHaskell and
wxWidgets on my Mac recently, but to no avail. I was wondering if
anyone knows how exactly to go about it. I've tried just about every
combination of old and new versions of wxWidgets from homebrew as well
as olde
12 matches
Mail list logo
