On 9 January 2012 18:09, Dave Tapley wrote:
> On 9 January 2012 17:04, Jeremy O'Donoghue wrote:
>
>> On 6 January 2012 16:02, Dave Tapley wrote:
>>
>>> 2012/1/6 shelarcy
>>>
>>
>> Needless to say, I have immediately hit the wx-config roadblock, since I
>> have compiled a release build of wxWidg
On 9 January 2012 17:04, Jeremy O'Donoghue wrote:
> Hi Dave, all
> On 6 January 2012 16:02, Dave Tapley wrote:
>
>> 2012/1/6 shelarcy
>>
>>> 2. It seems that wxcore depends on Eric's wx-config implicitly at least
>>> Windows environment. "cabal install" fail with wx-config-win binary,
>>>
>>
>>
2012/1/8 shelarcy
> Hi,
>
> I think that we can remove old-time dependency from wxcore now. Because
> wxcore uses old-time's System.Time modules in only Graphics.UI.WXCore.Db
> module, and that module is removed this version.
>
> I attached a patch for removing old-time dependency in Dave's wxhas
Hi Dave, all
On 6 January 2012 16:02, Dave Tapley wrote:
> 2012/1/6 shelarcy
>
>> 2. It seems that wxcore depends on Eric's wx-config implicitly at least
>> Windows environment. "cabal install" fail with wx-config-win binary,
>>
>
> Can you remember how this failed, or send some output from the
Hi Jeremy,
I found where causes installation problem. My wx-config-win can't recognise
--version option.
$ wx-config --version
wx-config Error: Unrecognised option: '--version'
Usage: wx-config [options]
Options:
(snip)
-v Outputs the revision of wx-config.
Note t
