wxhaskell-devel — wxhaskell developers

Re: [wxhaskell-devel] Conflicting exports in wxcore

[<mac...@gm...>]

Thanks, that sorted this one out.

In summary, to build darcs tip on Windows against wxWidgets 2.8 I needed:

1. a patch that removes wx-config --version call and hard-codes 2.8
libraries (attached)
2. Dave's patch from the previous e-mail in this thread

1. is obviously not ideal given that the goal now is to support
multiple wxWidgets versions with the same codebase. I'll have a look
at Eric's Haskell version of wx-config to see if it can help here.

Maciek

On Fri, Jul 29, 2011 at 9:43 PM, Dave Tapley <duk...@gm...> wrote:
> The attached patch resolves this issue for me.
>
> Let me know how you get on.
>
> Dave,
>
>
> On 28 July 2011 23:08, Dave Tapley <duk...@gm...> wrote:
>>
>> Yep, I see this¹ as well, I'll take a look now.
>>
>> Dave,
>>
>>
>> ¹ http://sourceforge.net/mailarchive/message.php?msg_id=27810904
>
>

[wxhaskell-devel] Patches for wxWidgets 2.9.2 GTK2 Linux

[Dave T. <duk...@gm...>]

Hi all,

So I can now build the latest from the wxHaskell darcs repo, but only after
applying the attached patches.
Quite a lot of them are very "hack it to make it work" patches, but I
thought I'd offer them to the list for review before cleaning them up.

Comments are welcome.

Dave,

Re: [wxhaskell-devel] Patches to build wxHaskell with wxWidgets 2.9.2 GTK on Linux

[Dave T. <duk...@gm...>]

On 29 July 2011 08:54, Heinrich Apfelmus <apf...@qu...> wrote:

> Dave Tapley wrote:
> > Hmm, further to this:
> >
> > $ darcs pull
> > Pulling from "http://code.haskell.org/wxhaskell"...
> > Official wxHaskell darcs repository
> > **********************
> > No remote changes to pull in!
> > $ cd wx
> > $ cabal configure
> > Resolving dependencies...
> > Configuring wx-0.13.1...
> > Warning: This package indirectly depends on multiple versions of the same
> > package. This is highly likely to cause a compile failure.
> > package wxcore-0.13.1 requires containers-0.3.0.0
> > package wxdirect-0.13.1 requires containers-0.4.0.0
> > package wxcore-0.13.1 requires parsec-2.1.0.1
> > package wxdirect-0.13.1 requires parsec-3.1.1
>
> You may need to bump dependency version. Are you using GHC 7.0? The
> easiest way to proceed is probably to copy the version constraints from
> the *latest* packages on hackage:
>
>   http://hackage.haskell.org/package/wx
>   http://hackage.haskell.org/package/wxcore
>   http://hackage.haskell.org/package/wxdirect
>
> and then reconfigure, rebuild and reinstall these packages.
>


Thank you for your response.
I actually resolved the problem in a different way, I found my "don't worry,
I have fixed it" email to the list sat in my drafts folder; sorry about that
:|

After some discussion on #haskell it transpired that it was a problem local
to my machine probably caused by this 'issue':
http://www.vex.net/~trebla/haskell/sicp.xhtml#pigeon

Some how I had ended up with ghc-pkg having both containers-0.3.0.0 and
containers-0.4.0.0 registered, with wxcore and wxdirect compiled again each
one respectively. By removing everything which depended on
containers-0.4.0.0 and then containers-0.4.0.0 itself I was able to rebuild
and reinstall wxdirect (only after running 'cabal clean') pinned to
containers-0.3.0.0, this allowed wx to configure without issue.

Dave,



>
>
> Best regards,
> Heinrich Apfelmus
>
> --
> http://apfelmus.nfshost.com
>
>
>
> ------------------------------------------------------------------------------
> Got Input?   Slashdot Needs You.
> Take our quick survey online.  Come on, we don't ask for help often.
> Plus, you'll get a chance to win $100 to spend on ThinkGeek.
> http://p.sf.net/sfu/slashdot-survey
> _______________________________________________
> wxhaskell-devel mailing list
> wxh...@li...
> https://lists.sourceforge.net/lists/listinfo/wxhaskell-devel
>

Re: [wxhaskell-devel] Patches to build wxHaskell with wxWidgets 2.9.2 GTK on Linux

[Heinrich A. <apf...@qu...>]

Dave Tapley wrote:
> Hmm, further to this:
> 
> $ darcs pull
> Pulling from "http://code.haskell.org/wxhaskell"...
> Official wxHaskell darcs repository
> **********************
> No remote changes to pull in!
> $ cd wx
> $ cabal configure
> Resolving dependencies...
> Configuring wx-0.13.1...
> Warning: This package indirectly depends on multiple versions of the same
> package. This is highly likely to cause a compile failure.
> package wxcore-0.13.1 requires containers-0.3.0.0
> package wxdirect-0.13.1 requires containers-0.4.0.0
> package wxcore-0.13.1 requires parsec-2.1.0.1
> package wxdirect-0.13.1 requires parsec-3.1.1

You may need to bump dependency version. Are you using GHC 7.0? The 
easiest way to proceed is probably to copy the version constraints from 
the *latest* packages on hackage:

   http://hackage.haskell.org/package/wx
   http://hackage.haskell.org/package/wxcore
   http://hackage.haskell.org/package/wxdirect

and then reconfigure, rebuild and reinstall these packages.


Best regards,
Heinrich Apfelmus

--
http://apfelmus.nfshost.com

[wxhaskell-devel] Conflicting exports in wxcore

[Dave T. <duk...@gm...>]

Yep, I see this¹ as well, I'll take a look now.

Dave,


¹ http://sourceforge.net/mailarchive/message.php?msg_id=27810904

Re: [wxhaskell-devel] Patches to build wxHaskell with wxWidgets 2.9.2 GTK on Linux

[Dave T. <duk...@gm...>]

On 28 July 2011 02:45, Dave Tapley <duk...@gm...> wrote:

> Please find attached a darcs patch file with the changes I had to make to
> build wxcore.
> Feel free to have a look and comment, they are all very much "make it
> compile" changes and I suspect I may have introduced badness (returning a
> null pointer).
>
> Unfortunately having made these changes and following these steps¹ I am now
> getting this error, which is a little confusing:
>
> wxhaskell-dev/wx$ sudo cabal install --global
> Resolving dependencies...
> cabal: dependencies conflict: wxcore-0.13.1 requires containers ==0.4.0.0
> however
> containers-0.4.0.0 was excluded because wxcore-0.13.1 requires containers
> ==0.3.0.0
>
> Its other dependencies have installed correctly:
> wxhaskell-dev/wx$ ghc-pkg list wxdirect
> /var/lib/ghc-6.12.1/package.conf.d
>    wxdirect-0.13.1
>
> wxhaskell-dev/wx$ ghc-pkg list wxcore
> /var/lib/ghc-6.12.1/package.conf.d
>    wxcore-0.13.1
>
>
> Any idea what this could mean?
>
> Dave,
>
> ¹ http://haskell.org/haskellwiki/WxHaskell/Building#Source_Release
>


Hmm, further to this:

$ darcs pull
Pulling from "http://code.haskell.org/wxhaskell"...
Official wxHaskell darcs repository
**********************
No remote changes to pull in!
$ cd wx
$ cabal configure
Resolving dependencies...
Configuring wx-0.13.1...
Warning: This package indirectly depends on multiple versions of the same
package. This is highly likely to cause a compile failure.
package wxcore-0.13.1 requires containers-0.3.0.0
package wxdirect-0.13.1 requires containers-0.4.0.0
package wxcore-0.13.1 requires parsec-2.1.0.1
package wxdirect-0.13.1 requires parsec-3.1.1

Re: [wxhaskell-devel] Specifying wxWidgets version to build wxHaskell with

[Eric Y. K. <eri...@gm...>]

On Tue, Jul 26, 2011 at 09:15:03 +0100, Jeremy O'Donoghue wrote:
> Perhaps we should do this work in a branch (I've never tried
> this in Darcs - how easy is it Eric?)

The mechanics of maintaining a Darcs branch are simple enough;
you just push to a separate directory, say

  http://code.haskell.org/wxhaskell/wxWidgets-2.9
 
One tricky thing may be what happens when there are conflicts,
because when you do not propagate conflict resolutions to
all involved branches, darcs suffers :-(

We generally do not advise people to maintain long term branches
unless they get merged in somewhat regularly.

-- 
Eric Kow <http://erickow.com>

Re: [wxhaskell-devel] Building wxcore on Ubuntu 10.04

[Dave T. <duk...@gm...>]

On 26 July 2011 00:41, Dave Tapley <duk...@gm...> wrote:

> On 25 July 2011 15:49, Jeremy O'Donoghue <jer...@gm...>wrote:
>
>> Hi all,
>>
>> On 25 July 2011 07:45, Eric Y. Kow <eri...@gm...> wrote:
>>
>>> On Mon, Jul 25, 2011 at 01:10:15 +0100, Dave Tapley wrote:
>>> > A very good suggestion.
>>> > I cabal unpacked wxcore-0.12.1.7 and it appears to have a fix in it¹.
>>> >
>>> > Do we know why this fix is in the release, but not in darcs?
>>>
>>> I suspect the answer lies somewhere in here:
>>>
>>>  darcs changes --repo http://code.haskell.org/wxhaskell --from-tag .
>>>  --match 'hunk 45999'
>>>
>>
>> The answer is that it comes from my clean-up for wxWidgets 2.9, and is
>> probably a case of being over-zealous. The problem wasn't caught because
>> (most likely) no-one built tip for Gtk. It's not an environment I have
>> readily available to me.
>>
>> I'm not sure that there is a straightforward way to get similar behaviour
>> on Gtk, so I think the only clean solution is to revert the old 'NULL'
>> implementation. What do you think?
>>
>> EWXWEXPORT(wxCursor*,Cursor_CreateLoad)(wxString* name,long type,int
>> width,int height)
>> {
>> #if (wxVERSION_NUMBER >= 2900)
>>     wxBitmapType bm_type = (wxBitmapType) type;
>> #else
>>     long bm_type = type;
>> #endif
>>
>> #ifdef __WXGTK__
>>  // See http://thread.gmane.org/gmane.comp.lib.wxwidgets.general/45999
>>     return NULL;
>> #else
>>     return new wxCursor(*name, bm_type, width, height);
>> #endif
>> }
>>
>> Regards
>> Jeremy
>>
>
> Having made these modifications I now get passed that error, but stumble on
> this: http://hpaste.org/49525
> Does anyone have any intuition why these files could be missing?
>


Hmm, I've switched to the 2.9.2 dev release of wxWidgets and I'm getting a
similar failures with:
Both with the latest wxHaskell in hackage: http://hpaste.org/49563
And with the latest from darcs: http://hpaste.org/49564

Does anyone have any suggestions as to a fix, or a more reliable build set
up?

Thanks,
Dave

Re: [wxhaskell-devel] Specifying wxWidgets version to build wxHaskell with

[Dave T. <duk...@gm...>]

On 26 July 2011 09:15, Jeremy O'Donoghue <jer...@gm...> wrote:

> On 26 July 2011 06:59, Eric Y. Kow <eri...@gm...> wrote:
>
>> On Tue, Jul 26, 2011 at 00:28:01 +0100, Dave Tapley wrote:
>> > I'm getting the impression that most people are using wxWidgets 2.9 with
>> > wxHaskell, is that a fair assumption?
>>
>> I was surprised by your impression, but now I see why you may feel that
>> way.
>>
>
> I think there's something of a mix. There are probably more wxWidgets 2.8
> users out there, but most people don't install unless something has broken -
> say a new HP version comes out. I started to look at support for 2.9 when
> people started asking for 2.9 features. In particular, I believe that 2.9
> can be compiled as a 64 bit library on newer Macs.
>
>
>> It turns out wxWidgets 2.9 was released early this month, on 2011-07-05.
>> This makes it a bit more urgent for wxhaskell to support both (good
>> thing Jeremy was working so furiously on that)
>>
>
> Hmmm. Nice to hear you say it, but truth be told, I rarely have the time to
> work 'furiously' on wxHaskell :-( Most work happens on intercontinental
> flights (good news: I have another one coming up in a couple of weeks).
>
> We have never had a good story for support of multiple versions, in part
> because wxdirect doesn't support conditional compilation, which means that
> we can't put #ifdefs around version/platform dependent parts of wxC headers.
> In the past we've sort of fudged the issue by officially supporting only one
> version, but I don't think that's a tenable position any longer.
>
> Eric's Haskell version of wx-config will help the 'library' aspect -
> especially if we start to use wxPack on Windows, so we can rely on having
> the libraries built in a specific way. We will need to make it work for 2.9
> and 2.8 though - I think these will need to coexist for a while yet. I
> looked at fixing the existing wx-config source for 2.9 (ISTR it's in C++),
> but looking at the code I lost the will to live. It's rather, err, verbose.
> Haskell would be much better.
>
> I did sort-of warn the list that 2.9 work would likely destabilize the tip
> for a while. Perhaps we should do this work in a branch (I've never tried
> this in Darcs - how easy is it Eric?)
>
> Jeremy
>

Let me know if there's any way I can help.
I'm going to be relying on wxHaskell in the immediate future so I'm keen to
familiarise myself with it because I suspect there are some 2.9 features I
need which aren't implemented in wxHaskell presently.

Re: [wxhaskell-devel] Specifying wxWidgets version to build wxHaskell with

[Dave T. <duk...@gm...>]

On 26 July 2011 06:59, Eric Y. Kow <eri...@gm...> wrote:

> On Tue, Jul 26, 2011 at 00:28:01 +0100, Dave Tapley wrote:
> > I'm getting the impression that most people are using wxWidgets 2.9 with
> > wxHaskell, is that a fair assumption?
>
> I was surprised by your impression, but now I see why you may feel that
> way.
>
> It turns out wxWidgets 2.9 was released early this month, on 2011-07-05.
> This makes it a bit more urgent for wxhaskell to support both (good
> thing Jeremy was working so furiously on that)
>

This impression came primarily from the fact that I couldn't build wxhaskell
again wxWidgets 2.8 (for the reasons I've sent other messages to the list).
Unfortunately it seems it also won't build against the 2.9.2 dev release,
but I'll post a separate message about that.


>
> > I've just grabbed the latest dev release (2.9.2) of wxWidgets because I'm
> > still getting errors trying to compile against the 2.8.10 version I got
> from
> > the Ubuntu repositories (I'm going to post about those errors separately)
> > and I'd just like to get something working.
>
> If you just want something that works, use wxWidgets 2.8 and the
> stable version of wxHaskell.
>

Well, there are some features in wxWidgets which aren't supported by
wxHaskell, so I was rather hoping to get it building so I can contribute to
the project :)


>
> --
> Eric Kow <http://erickow.com>
>

Re: [wxhaskell-devel] Specifying wxWidgets version to build wxHaskell with

[Jeremy O'D. <jer...@gm...>]

On 26 July 2011 06:59, Eric Y. Kow <eri...@gm...> wrote:

> On Tue, Jul 26, 2011 at 00:28:01 +0100, Dave Tapley wrote:
> > I'm getting the impression that most people are using wxWidgets 2.9 with
> > wxHaskell, is that a fair assumption?
>
> I was surprised by your impression, but now I see why you may feel that
> way.
>

I think there's something of a mix. There are probably more wxWidgets 2.8
users out there, but most people don't install unless something has broken -
say a new HP version comes out. I started to look at support for 2.9 when
people started asking for 2.9 features. In particular, I believe that 2.9
can be compiled as a 64 bit library on newer Macs.


> It turns out wxWidgets 2.9 was released early this month, on 2011-07-05.
> This makes it a bit more urgent for wxhaskell to support both (good
> thing Jeremy was working so furiously on that)
>

Hmmm. Nice to hear you say it, but truth be told, I rarely have the time to
work 'furiously' on wxHaskell :-( Most work happens on intercontinental
flights (good news: I have another one coming up in a couple of weeks).

We have never had a good story for support of multiple versions, in part
because wxdirect doesn't support conditional compilation, which means that
we can't put #ifdefs around version/platform dependent parts of wxC headers.
In the past we've sort of fudged the issue by officially supporting only one
version, but I don't think that's a tenable position any longer.

Eric's Haskell version of wx-config will help the 'library' aspect -
especially if we start to use wxPack on Windows, so we can rely on having
the libraries built in a specific way. We will need to make it work for 2.9
and 2.8 though - I think these will need to coexist for a while yet. I
looked at fixing the existing wx-config source for 2.9 (ISTR it's in C++),
but looking at the code I lost the will to live. It's rather, err, verbose.
Haskell would be much better.

I did sort-of warn the list that 2.9 work would likely destabilize the tip
for a while. Perhaps we should do this work in a branch (I've never tried
this in Darcs - how easy is it Eric?)

Jeremy

Re: [wxhaskell-devel] Specifying wxWidgets version to build wxHaskell with

[Eric Y. K. <eri...@gm...>]

On Tue, Jul 26, 2011 at 00:28:01 +0100, Dave Tapley wrote:
> I'm getting the impression that most people are using wxWidgets 2.9 with
> wxHaskell, is that a fair assumption?

I was surprised by your impression, but now I see why you may feel that
way.

It turns out wxWidgets 2.9 was released early this month, on 2011-07-05.
This makes it a bit more urgent for wxhaskell to support both (good
thing Jeremy was working so furiously on that)

> I've just grabbed the latest dev release (2.9.2) of wxWidgets because I'm
> still getting errors trying to compile against the 2.8.10 version I got from
> the Ubuntu repositories (I'm going to post about those errors separately)
> and I'd just like to get something working.

If you just want something that works, use wxWidgets 2.8 and the
stable version of wxHaskell.

-- 
Eric Kow <http://erickow.com>

Re: [wxhaskell-devel] Building wxcore on Ubuntu 10.04

[Dave T. <duk...@gm...>]

On 25 July 2011 15:49, Jeremy O'Donoghue <jer...@gm...> wrote:

> Hi all,
>
> On 25 July 2011 07:45, Eric Y. Kow <eri...@gm...> wrote:
>
>> On Mon, Jul 25, 2011 at 01:10:15 +0100, Dave Tapley wrote:
>> > A very good suggestion.
>> > I cabal unpacked wxcore-0.12.1.7 and it appears to have a fix in it¹.
>> >
>> > Do we know why this fix is in the release, but not in darcs?
>>
>> I suspect the answer lies somewhere in here:
>>
>>  darcs changes --repo http://code.haskell.org/wxhaskell --from-tag .
>>  --match 'hunk 45999'
>>
>
> The answer is that it comes from my clean-up for wxWidgets 2.9, and is
> probably a case of being over-zealous. The problem wasn't caught because
> (most likely) no-one built tip for Gtk. It's not an environment I have
> readily available to me.
>
> I'm not sure that there is a straightforward way to get similar behaviour
> on Gtk, so I think the only clean solution is to revert the old 'NULL'
> implementation. What do you think?
>
> EWXWEXPORT(wxCursor*,Cursor_CreateLoad)(wxString* name,long type,int
> width,int height)
> {
> #if (wxVERSION_NUMBER >= 2900)
>     wxBitmapType bm_type = (wxBitmapType) type;
> #else
>     long bm_type = type;
> #endif
>
> #ifdef __WXGTK__
>  // See http://thread.gmane.org/gmane.comp.lib.wxwidgets.general/45999
>     return NULL;
> #else
>     return new wxCursor(*name, bm_type, width, height);
> #endif
> }
>
> Regards
> Jeremy
>

Having made these modifications I now get passed that error, but stumble on
this: http://hpaste.org/49525
Does anyone have any intuition why these files could be missing?

[wxhaskell-devel] Specifying wxWidgets version to build wxHaskell with

[Dave T. <duk...@gm...>]

I'm getting the impression that most people are using wxWidgets 2.9 with
wxHaskell, is that a fair assumption?

I've just grabbed the latest dev release (2.9.2) of wxWidgets because I'm
still getting errors trying to compile against the 2.8.10 version I got from
the Ubuntu repositories (I'm going to post about those errors separately)
and I'd just like to get something working.

I have configure'd and make'd 2.9.2, I didn't want to make install because I
don't want it to conflict with the 2.8.10 version.

I see that the wxHaskell's Setup.hs uses wx-config, but I don't see any way
to specify a prefix to wx-config, so I was just wondering how you guys get
wxHaskell to build using a specific version of wxHaskell? The only approach
I can see is to make sure the wx-config in your path in a symlink and that
it points to the wxWidgets library you want to use.

Thanks, Dave

Re: [wxhaskell-devel] Building wxcore on Ubuntu 10.04

[Dave T. <duk...@gm...>]

On 25 July 2011 15:49, Jeremy O'Donoghue <jer...@gm...> wrote:

> Hi all,
>
> On 25 July 2011 07:45, Eric Y. Kow <eri...@gm...> wrote:
>
>> On Mon, Jul 25, 2011 at 01:10:15 +0100, Dave Tapley wrote:
>> > A very good suggestion.
>> > I cabal unpacked wxcore-0.12.1.7 and it appears to have a fix in it¹.
>> >
>> > Do we know why this fix is in the release, but not in darcs?
>>
>> I suspect the answer lies somewhere in here:
>>
>>  darcs changes --repo http://code.haskell.org/wxhaskell --from-tag .
>>  --match 'hunk 45999'
>>
>
> The answer is that it comes from my clean-up for wxWidgets 2.9, and is
> probably a case of being over-zealous. The problem wasn't caught because
> (most likely) no-one built tip for Gtk. It's not an environment I have
> readily available to me.
>
> I'm not sure that there is a straightforward way to get similar behaviour
> on Gtk, so I think the only clean solution is to revert the old 'NULL'
> implementation. What do you think?
>
> EWXWEXPORT(wxCursor*,Cursor_CreateLoad)(wxString* name,long type,int
> width,int height)
> {
> #if (wxVERSION_NUMBER >= 2900)
>     wxBitmapType bm_type = (wxBitmapType) type;
> #else
>     long bm_type = type;
> #endif
>
> #ifdef __WXGTK__
>  // See http://thread.gmane.org/gmane.comp.lib.wxwidgets.general/45999
>     return NULL;
> #else
>     return new wxCursor(*name, bm_type, width, height);
> #endif
> }
>
> Regards
> Jeremy
>

Well, the 2.9.2 dev release¹ appears to include that constructor (in
include/wx/gtk/cursor.h) if wxUSE_IMAGE is set.
So perhaps we should check that?


¹ http://www.wxwidgets.org/downloads/#latest_dev

Re: [wxhaskell-devel] Building wxcore on Ubuntu 10.04

[Dave T. <duk...@gm...>]

On 25 July 2011 07:45, Eric Y. Kow <eri...@gm...> wrote:

> On Mon, Jul 25, 2011 at 01:10:15 +0100, Dave Tapley wrote:
> > A very good suggestion.
> > I cabal unpacked wxcore-0.12.1.7 and it appears to have a fix in it¹.
> >
> > Do we know why this fix is in the release, but not in darcs?
>
> I suspect the answer lies somewhere in here:
>
>  darcs changes --repo http://code.haskell.org/wxhaskell --from-tag .
>  --match 'hunk 45999'
>
> (the 45999 is from the URL mentioned in the source code you pasted)
>
> It could be a good thing if you would catalogue all the wxWidgets
> 2.8 regressions you have encountered so far
>
> --
> Eric Kow <http://erickow.com>
>

The only other step I had to take after pulling the latest was:
darcs obliterate -p "Additional libraries required by wxWidgets 2.9"

Failure to do this causes:
Configuring wxcore-0.13.1...
setup: Missing dependencies on foreign libraries:
* Missing C libraries: wx_baseu-2.8, wx_baseu_net-2.8, wx_baseu_xml-2.8,
wx_gtk2u_core-2.8, wx_gtk2u_adv-2.8, wx_gtk2u_html-2.8, wx_gtk2u_qa-2.8,
wx_gtk2u_xrc-2.8, wx_gtk2u_aui-2.8, wx_gtk2u_richtext-2.8
This problem can usually be solved by installing the system packages that
provide these libraries (you may need the "-dev" versions). If the libraries
are already installed but in a non-standard location then you can use the
flags --extra-include-dirs= and --extra-lib-dirs= to specify where they are.

Re: [wxhaskell-devel] Building wxcore on Ubuntu 10.04

[Jeremy O'D. <jer...@gm...>]

Hi all,

On 25 July 2011 07:45, Eric Y. Kow <eri...@gm...> wrote:

> On Mon, Jul 25, 2011 at 01:10:15 +0100, Dave Tapley wrote:
> > A very good suggestion.
> > I cabal unpacked wxcore-0.12.1.7 and it appears to have a fix in it¹.
> >
> > Do we know why this fix is in the release, but not in darcs?
>
> I suspect the answer lies somewhere in here:
>
>  darcs changes --repo http://code.haskell.org/wxhaskell --from-tag .
>  --match 'hunk 45999'
>

The answer is that it comes from my clean-up for wxWidgets 2.9, and is
probably a case of being over-zealous. The problem wasn't caught because
(most likely) no-one built tip for Gtk. It's not an environment I have
readily available to me.

I'm not sure that there is a straightforward way to get similar behaviour on
Gtk, so I think the only clean solution is to revert the old 'NULL'
implementation. What do you think?

EWXWEXPORT(wxCursor*,Cursor_CreateLoad)(wxString* name,long type,int
width,int height)
{
#if (wxVERSION_NUMBER >= 2900)
    wxBitmapType bm_type = (wxBitmapType) type;
#else
    long bm_type = type;
#endif
#ifdef __WXGTK__
 // See http://thread.gmane.org/gmane.comp.lib.wxwidgets.general/45999
    return NULL;
#else
    return new wxCursor(*name, bm_type, width, height);
#endif
}

Regards
Jeremy

Re: [wxhaskell-devel] Building wxcore on Ubuntu 10.04

[Eric Y. K. <eri...@gm...>]

On Mon, Jul 25, 2011 at 01:10:15 +0100, Dave Tapley wrote:
> A very good suggestion.
> I cabal unpacked wxcore-0.12.1.7 and it appears to have a fix in it¹.
> 
> Do we know why this fix is in the release, but not in darcs?

I suspect the answer lies somewhere in here:

  darcs changes --repo http://code.haskell.org/wxhaskell --from-tag .  --match 'hunk 45999'

(the 45999 is from the URL mentioned in the source code you pasted)

It could be a good thing if you would catalogue all the wxWidgets
2.8 regressions you have encountered so far

-- 
Eric Kow <http://erickow.com>

Re: [wxhaskell-devel] Building wxcore on Ubuntu 10.04

[Dave T. <duk...@gm...>]

On 24 July 2011 22:57, Eric Y. Kow <eri...@gm...> wrote:

> On Sat, Jul 23, 2011 at 21:26:12 +0100, Dave Tapley wrote:
> > Well I have a response¹ from someone in the wx-dev group saying that the
> > missing GTK constructor "is
> > available in 2.9.2 but chances of this being backported to 2.8 are slim".
> >
> > I don't know how people would feel about modifying wxcore to use a
> > constructor which is implemented for 2.8 with GTK?
>
> I think it's worth checking that the stable wxcore doesn't already do
> this.
>
> --
> Eric Kow <http://erickow.com>
>

A very good suggestion.
I cabal unpacked wxcore-0.12.1.7 and it appears to have a fix in it¹.

Do we know why this fix is in the release, but not in darcs?


¹
#ifdef __WXGTK__
// See http://thread.gmane.org/gmane.comp.lib.wxwidgets.general/45999
    return NULL;
#else

Re: [wxhaskell-devel] Building wxcore on Ubuntu 10.04

[Eric Y. K. <eri...@gm...>]

On Sat, Jul 23, 2011 at 21:26:12 +0100, Dave Tapley wrote:
> Well I have a response¹ from someone in the wx-dev group saying that the
> missing GTK constructor "is
> available in 2.9.2 but chances of this being backported to 2.8 are slim".
> 
> I don't know how people would feel about modifying wxcore to use a
> constructor which is implemented for 2.8 with GTK?

I think it's worth checking that the stable wxcore doesn't already do
this.

-- 
Eric Kow <http://erickow.com>

Re: [wxhaskell-devel] Building wxcore on Ubuntu 10.04

[Dave T. <duk...@gm...>]

Well I have a response¹ from someone in the wx-dev group saying that the
missing GTK constructor "is
available in 2.9.2 but chances of this being backported to 2.8 are slim".

I don't know how people would feel about modifying wxcore to use a
constructor which is implemented for 2.8 with GTK?

Dave,


¹
---------- Forwarded message ----------
From: Vadim Zeitlin <va...@wx...>
Date: 23 July 2011 12:52
Subject: Re: [wx-dev] [2.8.12] Missing constructor definition in gtk
cursor.h
To: wx...@go...


On Sat, 23 Jul 2011 02:32:12 +0100 Dave Tapley <duk...@gm...> wrote:

DT> It seems that in (at least) the latest 2.8.12 release of wxWidgets¹ the
DT> cursor.h file in include/wx/gtk/ does not contain a four argument
DT> constructor², however the cursor.h in include/wx/msw does.
DT>
DT> Does anyone know why this is so?

 It simply wasn't implemented initially. It was added since then and is
available in 2.9.2 but chances of this being backported to 2.8 are slim.

 Regards,
VZ



On 23 July 2011 02:26, Dave Tapley <dav...@gm...> wrote:

> I have done some further investigation on this and discovered the source of
> the problem, and it is very strange.
>
> It seems that even in the latest 2.8.12 release of wxWidgets¹ the cursor.h
> file in include/wx/gtk/ does not contain the four argument constructor
> (which is causing the build failure below), however the cursor.h in
> include/wx/msw does.
>
> I looked at the history for eljcursor.cpp in darcs and it hasn't been
> changed in anyway in a long time, so this can't be a new problem.
>
> I am going to post to the wx-dev² group and see if anyone knows why this
> constructor declaration is missing.
>
> But the question remains:
> How have we been able to build wxcore for GTK when its .cabal claims³ it
> works for GTK with wxWidgets 2.8?
>
> Thanks,
> Dave
>
>
> ¹ http://sourceforge.net/projects/wxwindows/files/2.8.12/
> ² http://groups.google.com/group/wx-dev
> ³ http://code.haskell.org/wxhaskell/wxcore/wxcore.cabal
>
>
>
> On 22 July 2011 20:06, Dave Tapley <dav...@gm...> wrote:
>
>> Hmm, unfortunately whilst cabal configure now completes successfully, I am
>> having a problem when doing cabal build, see output below. Could it be
>> related to this:
>> http://comments.gmane.org/gmane.comp.lang.haskell.wxhaskell.general/298
>> ?
>>
>> src/cpp/eljcursor.cpp:23:0:
>>      error: no matching function for call to
>> ‘wxCursor::wxCursor(wxString&, long int&, int&, int&)’
>>
>> /usr/include/wx-2.8/wx/gtk/cursor.h:31:0:
>>      note: candidates are: wxCursor::wxCursor(const char*, int, int, int,
>> int, const char*, const wxColour*, const wxColour*)
>>
>> /usr/include/wx-2.8/wx/gtk/cursor.h:29:0:
>>      note:                 wxCursor::wxCursor(const wxImage&)
>>
>> /usr/include/wx-2.8/wx/gtk/cursor.h:27:0:
>>      note:                 wxCursor::wxCursor(int)
>>
>> /usr/include/wx-2.8/wx/gtk/cursor.h:26:0:
>>      note:                 wxCursor::wxCursor()
>>
>> /usr/include/wx-2.8/wx/gtk/cursor.h:23:0:
>>      note:                 wxCursor::wxCursor(const wxCursor&)
>>
>>
>>
>>
>>
>>
>> On 21 July 2011 23:00, Dave Tapley <dav...@gm...> wrote:
>>
>>> That was exactly the problem!
>>>
>>> Thank you very much Eric :)
>>>
>>> Dave,
>>>
>>>
>>>
>>>
>>> On 21 July 2011 22:44, Eric Y. Kow <eri...@gm...> wrote:
>>>
>>>> Hi Dave,
>>>>
>>>> On Thu, Jul 21, 2011 at 21:54:11 +0100, Dave Tapley wrote:
>>>> > I am having trouble compiling wxcore on Ubuntu 10.04.
>>>> > The source I am using I pulled with a "darcs get" from hackage, I then
>>>> > descended into the wxcore directory and did a "cabal configure".
>>>>
>>>> I suspect that recent minor changes to our Setup.hs file have
>>>> broken compatibility with wxWidgets 2.8.
>>>>
>>>> Could you try
>>>>
>>>>  darcs obliterate -p "Additional libraries required by wxWidgets 2.9"
>>>>
>>>> and see if it has any result?
>>>>
>>>> Alternatively, if you just want a working wxHaskell and aren't
>>>> particularly interested in debugging this sort of thing, I'd
>>>> suggest just doing cabal install wx and fetching the one on
>>>> hackage for now.
>>>>
>>>> Thanks!
>>>>
>>>> --
>>>> Eric Kow <http://erickow.com>
>>>>
>>>
>>>
>>
>

Re: [wxhaskell-devel] Building wxcore on Ubuntu 10.04

[Dave T. <dav...@gm...>]

I have done some further investigation on this and discovered the source of
the problem, and it is very strange.

It seems that even in the latest 2.8.12 release of wxWidgets¹ the cursor.h
file in include/wx/gtk/ does not contain the four argument constructor
(which is causing the build failure below), however the cursor.h in
include/wx/msw does.

I looked at the history for eljcursor.cpp in darcs and it hasn't been
changed in anyway in a long time, so this can't be a new problem.

I am going to post to the wx-dev² group and see if anyone knows why this
constructor declaration is missing.

But the question remains:
How have we been able to build wxcore for GTK when its .cabal claims³ it
works for GTK with wxWidgets 2.8?

Thanks,
Dave


¹ http://sourceforge.net/projects/wxwindows/files/2.8.12/
² http://groups.google.com/group/wx-dev
³ http://code.haskell.org/wxhaskell/wxcore/wxcore.cabal


On 22 July 2011 20:06, Dave Tapley <dav...@gm...> wrote:

> Hmm, unfortunately whilst cabal configure now completes successfully, I am
> having a problem when doing cabal build, see output below. Could it be
> related to this:
> http://comments.gmane.org/gmane.comp.lang.haskell.wxhaskell.general/298  ?
>
> src/cpp/eljcursor.cpp:23:0:
>      error: no matching function for call to ‘wxCursor::wxCursor(wxString&,
> long int&, int&, int&)’
>
> /usr/include/wx-2.8/wx/gtk/cursor.h:31:0:
>      note: candidates are: wxCursor::wxCursor(const char*, int, int, int,
> int, const char*, const wxColour*, const wxColour*)
>
> /usr/include/wx-2.8/wx/gtk/cursor.h:29:0:
>      note:                 wxCursor::wxCursor(const wxImage&)
>
> /usr/include/wx-2.8/wx/gtk/cursor.h:27:0:
>      note:                 wxCursor::wxCursor(int)
>
> /usr/include/wx-2.8/wx/gtk/cursor.h:26:0:
>      note:                 wxCursor::wxCursor()
>
> /usr/include/wx-2.8/wx/gtk/cursor.h:23:0:
>      note:                 wxCursor::wxCursor(const wxCursor&)
>
>
>
>
>
>
> On 21 July 2011 23:00, Dave Tapley <dav...@gm...> wrote:
>
>> That was exactly the problem!
>>
>> Thank you very much Eric :)
>>
>> Dave,
>>
>>
>>
>>
>> On 21 July 2011 22:44, Eric Y. Kow <eri...@gm...> wrote:
>>
>>> Hi Dave,
>>>
>>> On Thu, Jul 21, 2011 at 21:54:11 +0100, Dave Tapley wrote:
>>> > I am having trouble compiling wxcore on Ubuntu 10.04.
>>> > The source I am using I pulled with a "darcs get" from hackage, I then
>>> > descended into the wxcore directory and did a "cabal configure".
>>>
>>> I suspect that recent minor changes to our Setup.hs file have
>>> broken compatibility with wxWidgets 2.8.
>>>
>>> Could you try
>>>
>>>  darcs obliterate -p "Additional libraries required by wxWidgets 2.9"
>>>
>>> and see if it has any result?
>>>
>>> Alternatively, if you just want a working wxHaskell and aren't
>>> particularly interested in debugging this sort of thing, I'd
>>> suggest just doing cabal install wx and fetching the one on
>>> hackage for now.
>>>
>>> Thanks!
>>>
>>> --
>>> Eric Kow <http://erickow.com>
>>>
>>
>>
>

Re: [wxhaskell-devel] Building wxcore on Ubuntu 10.04

[Dave T. <dav...@gm...>]

Hmm, unfortunately whilst cabal configure now completes successfully, I am
having a problem when doing cabal build, see output below. Could it be
related to this:
http://comments.gmane.org/gmane.comp.lang.haskell.wxhaskell.general/298  ?

src/cpp/eljcursor.cpp:23:0:
     error: no matching function for call to ‘wxCursor::wxCursor(wxString&,
long int&, int&, int&)’

/usr/include/wx-2.8/wx/gtk/cursor.h:31:0:
     note: candidates are: wxCursor::wxCursor(const char*, int, int, int,
int, const char*, const wxColour*, const wxColour*)

/usr/include/wx-2.8/wx/gtk/cursor.h:29:0:
     note:                 wxCursor::wxCursor(const wxImage&)

/usr/include/wx-2.8/wx/gtk/cursor.h:27:0:
     note:                 wxCursor::wxCursor(int)

/usr/include/wx-2.8/wx/gtk/cursor.h:26:0:
     note:                 wxCursor::wxCursor()

/usr/include/wx-2.8/wx/gtk/cursor.h:23:0:
     note:                 wxCursor::wxCursor(const wxCursor&)





On 21 July 2011 23:00, Dave Tapley <dav...@gm...> wrote:

> That was exactly the problem!
>
> Thank you very much Eric :)
>
> Dave,
>
>
>
>
> On 21 July 2011 22:44, Eric Y. Kow <eri...@gm...> wrote:
>
>> Hi Dave,
>>
>> On Thu, Jul 21, 2011 at 21:54:11 +0100, Dave Tapley wrote:
>> > I am having trouble compiling wxcore on Ubuntu 10.04.
>> > The source I am using I pulled with a "darcs get" from hackage, I then
>> > descended into the wxcore directory and did a "cabal configure".
>>
>> I suspect that recent minor changes to our Setup.hs file have
>> broken compatibility with wxWidgets 2.8.
>>
>> Could you try
>>
>>  darcs obliterate -p "Additional libraries required by wxWidgets 2.9"
>>
>> and see if it has any result?
>>
>> Alternatively, if you just want a working wxHaskell and aren't
>> particularly interested in debugging this sort of thing, I'd
>> suggest just doing cabal install wx and fetching the one on
>> hackage for now.
>>
>> Thanks!
>>
>> --
>> Eric Kow <http://erickow.com>
>>
>
>

Re: [wxhaskell-devel] Building wxcore on Ubuntu 10.04

[Dave T. <dav...@gm...>]

That was exactly the problem!

Thank you very much Eric :)

Dave,



On 21 July 2011 22:44, Eric Y. Kow <eri...@gm...> wrote:

> Hi Dave,
>
> On Thu, Jul 21, 2011 at 21:54:11 +0100, Dave Tapley wrote:
> > I am having trouble compiling wxcore on Ubuntu 10.04.
> > The source I am using I pulled with a "darcs get" from hackage, I then
> > descended into the wxcore directory and did a "cabal configure".
>
> I suspect that recent minor changes to our Setup.hs file have
> broken compatibility with wxWidgets 2.8.
>
> Could you try
>
>  darcs obliterate -p "Additional libraries required by wxWidgets 2.9"
>
> and see if it has any result?
>
> Alternatively, if you just want a working wxHaskell and aren't
> particularly interested in debugging this sort of thing, I'd
> suggest just doing cabal install wx and fetching the one on
> hackage for now.
>
> Thanks!
>
> --
> Eric Kow <http://erickow.com>
>

Re: [wxhaskell-devel] Building wxcore on Ubuntu 10.04

[Eric Y. K. <eri...@gm...>]

Hi Dave,

On Thu, Jul 21, 2011 at 21:54:11 +0100, Dave Tapley wrote:
> I am having trouble compiling wxcore on Ubuntu 10.04.
> The source I am using I pulled with a "darcs get" from hackage, I then
> descended into the wxcore directory and did a "cabal configure".

I suspect that recent minor changes to our Setup.hs file have
broken compatibility with wxWidgets 2.8.

Could you try

 darcs obliterate -p "Additional libraries required by wxWidgets 2.9"

and see if it has any result?

Alternatively, if you just want a working wxHaskell and aren't
particularly interested in debugging this sort of thing, I'd
suggest just doing cabal install wx and fetching the one on
hackage for now.

Thanks!

-- 
Eric Kow <http://erickow.com>