On Friday, 13.11.09 at 23:32, Jeremy O'Donoghue wrote:
> It works - after a bump to version 0.12.1.2.
This is great.
> Someone brave should probably try:
> cabal update
> WXWIN= WXCFG=gcc_dll/mswu cabal install wx
Worked! No problems.
> I guess we should announce to the world :-)
Good announce
Hi all,
It works - after a bump to version 0.12.1.2.
I'll update darcs shortly, but in the meantime, you should be able to
do the following (assuming you have wxWidgets installed - must be
compiled with MSys if you are on Windows)
cabal update
cabal install wxdirect
WXWIN= WXCFG=gcc_dll/mswu cab
The problem, of course, being that stc.cpp includes stc_gen.cpp. For
now I'm going to put it into extra-source-files.
Didn't spot that before upload, and the cabal verifier obviously
couldn't. We should try to find a better way to do this, but for now
this should be OK.
Jeremy
2009/11/13 Jeremy
Hi Brian,
2009/11/13 Brian Lewis :
> For me, wxcore 0.12.1.1 on hackage fails to build for lack of
> stc_gen.cpp. It seems to be in darcs, though.
>
Working on the problem now. Will let you all know when I have
something which works - believe I am fairly close now, although it's
late here :-(
Je
For me, wxcore 0.12.1.1 on hackage fails to build for lack of
stc_gen.cpp. It seems to be in darcs, though.
--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design
Hi Brian,
On Thu, 12 Nov 2009 11:54 -0600, "Brian Lewis" wrote:
> WxcClassInfo is in the exported modules list, but its source is
> generated by wxdirect into dist/build/autogen. I added
> dist/build/autogen to hs-source-dirs and I think it's working.
>
> Please add that line or pull my repo and
On Thursday, 12.11.09 at 14:11, Jeremy O'Donoghue wrote:
> Setup.hs: Error: Could not find module: Graphics.UI.WXCore.WxcClassInfo with
> any suffix: ["gc","chs","hsc","x","y","ly","cpphs","hs","lhs"]
WxcClassInfo is in the exported modules list, but its source is
generated by wxdirect into dist/b
Hi Eric,
2009/11/12 Eric Y. Kow :
>
> I think I replied too soon. The problem looks like an interaction
> between the fact that we expose our autogenerated modules and the fact
> that we generate them in a non-src directory (which is nice to do).
Yup - discovered that when I tried it :-(
It's n
On Thu, Nov 12, 2009 at 14:11:17 +, Jeremy O'Donoghue wrote:
> $ WXWIN=/c/utils/wxWidgets-2.8.10 WXCFG=gcc_dll/mswu runhaskell Setup.hs sdist
> Building source dist for wxcore-0.12.1.1...
> Setup.hs: Error: Could not find module: Graphics.UI.WXCore.WxcClassInfo with
> any suffix: ["gc","chs","h
Hi Jeremy,
On Thu, Nov 12, 2009 at 14:11:17 +, Jeremy O'Donoghue wrote:
> $ WXWIN=/c/utils/wxWidgets-2.8.10 WXCFG=gcc_dll/mswu runhaskell Setup.hs sdist
> Building source dist for wxcore-0.12.1.1...
> Setup.hs: Error: Could not find module: Graphics.UI.WXCore.WxcClassInfo with
> any suffix: ["
Hi all,
A couple more things:
Cabal upload is not happy with putting 'build-depends:' in a
conditional. I get the following error:
"400 Error in upload
The dependency 'build-depends: base' does not specify an upper bound
on the version number. Each major release of the 'base' package
changes the
Hi all,
[Eric - note question aimed your way, buried near the bottom]
2009/11/10 Brian Lewis :
> On Tuesday, 10.11.09 at 12:42, Jeremy O'Donoghue wrote:
>> One good option may be to commit the code 'as-is' to enable simple
>> cabal install of wxHaskell, and work on putting back the features we
>>
On Tuesday, 10.11.09 at 12:42, Jeremy O'Donoghue wrote:
> One good option may be to commit the code 'as-is' to enable simple
> cabal install of wxHaskell, and work on putting back the features we
> have (temporarily) lost.
If basic functionality is still there, I really favor doing it this way,
be
On Tue, Nov 10, 2009 at 12:42:28 +, Jeremy O'Donoghue wrote:
> One other thing to consider - the wxc build system has always been
> pretty fragile, mainly because of the support for Visual Studio, which
> complicates everything. Brian's approach lets us get rid of the wxc
> build system complet
Hi Brian,
I've confirmed that your procedure works for me, too.
I've merged your code into a local copy of the latest Darcs repo, but
there's a problem I want to track down before releasing to the Darcs
repo.
The issue is that I'm seeing exceptions from the Debug build variants
(Release is fine)
Jeremy, thanks very much for writing back. That helped a lot.
Here's a procedure that seems to work:
Install
MinGW 5.1.6
[x] g++ compiler
[x] MinGW Make
MSYS-1.0.11
wxMSW-2.8.10
wx-config Windows port
In MSYS
cd /c/wxWidgets-2.8.10/build/msw
mingw32-make -f makefile.gcc BUILD
16 matches
Mail list logo
