wxhaskell-users — General mailing list for wxhaskell users

Re: [wxhaskell-users] strings truncated to one character in wxhaskell-0.10.1 under ghc-6.6

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

On Wed, Dec 06, 2006 at 13:22:21 -0800, Conal Elliott wrote:
> Fixed!  Now I have wxHaskell-0.10.1 and wxWidgets-2.6.3 working together
> with unicode, and no more truncated strings.

Fantastic! Sorry about not getting back to you.

> One more small annoyance.  I get many compiler complaints about -fPIC, e.=
g.,
>=20
> g++ -c wxc/src/ewxw_main.cpp -o out/wxc/ewxw_main.o -MD
> -IC:/cygwin/usr/local/include -IC:/cygwin/usr/local/lib/wx/include/msw-
> unicode-release-static-2.6 -IC:/cygwin/usr/local/include/wx-2.6 -D__WIN95=
__
> -D__WXMSW__ -fPIC -Iwxc/include
> cc1plus.exe: warning: -fPIC ignored for target (all code is position
> independent)

Hmm, this comes from Ari's patch to add -fPIC to the Makefile.  Perhaps
we need this to be set by the configure script.  Anyone volunteer to
submit a patch?

> Is there a process for submitting & tracking wxHaskell bug reports?

Please use the tracker on sourceforge.

Thanks,

--=20
Eric Kow                     http://www.loria.fr/~kow
PGP Key ID: 08AC04F9         Merci de corriger mon fran=E7ais.

[wxhaskell-users] installing/registering haddock docs for wxhaskell?

[Conal E. <co...@co...>]

I see how to make wxhaskell (haddock) docs and how to build and install &
register the wxhaskell packages.  Is there a way to install & register the
haddock docs so that haddock can find them for libraries that use
wxhaskell?  (As a temporary hack, I edited the paths right into my ghc
package.conf file.)

  - Conal

Re: [wxhaskell-users] strings truncated to one character in wxhaskell-0.10.1 under ghc-6.6

[Conal E. <co...@co...>]

Fixed!  Now I have wxHaskell-0.10.1 and wxWidgets-2.6.3 working together
with unicode, and no more truncated strings.

The compilation problem below seems to have been that my wxHaskell compile
was picking up my old wxWidgets-2.4 include files rather than the new
2.6.3ones.  Looking in /usr/local/include, I saw wx/ and
wx-2.6.  Although the wxHaskell compilations explicitly ref'd include/wx-2.=
6,
the error messages below ref'd include/wx, I fixed the problem by renaming
include/wx to include/wx-2.4 and recompiling wxHaskell.

There was one more build problem.  After wxcore was built, I got "multiple
target patterns" errors from "make install".  To work around this problem, =
I
moved two sets *.d files out of the way, as follows:

bash-3.1$ make install
out/wxc/ewxw_main.d:1: *** multiple target patterns.  Stop.
bash-3.1$ pushd out/wxc
/c/Haskell/wxhaskell/out/wxc /c/Haskell/wxhaskell /usr/local/include
/c/wxWidgets-2.6.3/mybuild
bash-3.1$ mkdir ds
bash-3.1$ mv *.d ds
bash-3.1$ pushd
/c/Haskell/wxhaskell /c/Haskell/wxhaskell/out/wxc /usr/local/include
/c/wxWidgets-2.6.3/mybuild
bash-3.1$ make install
out/wxc/ewxw/eljaccelerator.d:1: *** multiple target patterns.  Stop.
bash-3.1$ pushd
/c/Haskell/wxhaskell/out/wxc /c/Haskell/wxhaskell /usr/local/include
/c/wxWidgets-2.6.3/mybuild
bash-3.1$ cd ewxw
bash-3.1$ mkdir ds
bash-3.1$ mv *.d ds
bash-3.1$ pushd
/c/Haskell/wxhaskell /c/Haskell/wxhaskell/out/wxc/ewxw /usr/local/include
/c/wxWidgets-2.6.3/mybuild
bash-3.1$ make install
install directory: C:/cygwin/usr/local/lib/
...

All went well from there.

One more small annoyance.  I get many compiler complaints about -fPIC, e.g.=
,

g++ -c wxc/src/ewxw_main.cpp -o out/wxc/ewxw_main.o -MD
-IC:/cygwin/usr/local/include -IC:/cygwin/usr/local/lib/wx/include/msw-
unicode-release-static-2.6 -IC:/cygwin/usr/local/include/wx-2.6 -D__WIN95__
-D__WXMSW__ -fPIC -Iwxc/include
cc1plus.exe: warning: -fPIC ignored for target (all code is position
independent)

Is there a process for submitting & tracking wxHaskell bug reports?

Cheers,  - Conal


On 12/4/06, Conal Elliott <co...@co...> wrote:
>
> oops -- premature send.
>
> any advice?  what configure options do you use for wxWidgets-2.6.3?
>
> Thanks,   - Conal
>
>
>
> On 12/4/06, Conal Elliott <co...@co...> wrote:
> >
> > Thanks for the tips, Eric.  I've built & installed wxWidgets 2.6.3(conf=
iguring with --with-msw
> > --disable-shared --with-opengl --enable-unicode).  When I compile
> > wxHaskell (configuring with --prefix=3D/usr/local --with-opengl), I get=
 a host
> > of errors, such as
> >
> > C:/cygwin/usr/local/include/wx/chkconf.h:100:9: #error "wxUSE_PROLOGIO
> > must be defined."
> > C:/cygwin/usr/local/include/wx/chkconf.h:488:9: #error "wxUSE_NEW_GRID
> > must be defined."
> > C:/cygwin/usr/local/include/wx/chkconf.h:1184:9: #error
> > "wxUSE_DYNAMIC_CLASSES must be defined as 1"
> >
> > and
> >
> > C:/cygwin/usr/local/include/wx/object.h:438: `wxClassInfo' was not
> > declared in this scope
> > C:/cygwin/usr/local/include/wx/object.h:438: `info' was not declared in
> > this  scope
> > C:/cygwin/usr/local/include/wx/object.h:438: invalid data member
> > initialization
> >
> >
> >
> >
> > On 12/2/06, Eric Y. Kow <eri...@gm...> wrote:
> > >
> > > On Thu, Nov 30, 2006 at 14:26:43 -0800, Conal Elliott wrote:
> > > > I don't know whether Unicode was enabled in my wxWidgets build.  I
> > > have
> > > > wxWidgets 2.4.2 and configured compilation without any mention of
> > > unicode.
> > > > Would I want unicode enabled or disabled?
> > >
> > > You want it enabled
> > >
> > > > I just tried a clean build & install with --enable-unicode and one
> > > with
> > > > --disable-unicode, and I got the same truncation behavior in both
> > > cases.
> > >
> > > You might also want to make sure that wxhaskell is using the wxWidget=
s
> > > you think it's using.  You can set this explicitly with ./configure
> > > --wx-config=3D/the/path/to/your/wxWidgets
> > >
> > > > What is the ideal version of wxWidgets and what are the ideal build
> > > > configuration parameters for wxWidgets & wxHaskell with ghc-6.6?
> > >
> > > > And does anyone have wxHaskell working correctly (not just
> > > compiling) with
> > > > ghc-6.6?
> > >
> > > It has worked for me in the past with 2.4.2 and ghc-6.4.1, and it
> > > seems
> > > to be working for me with ghc-6.6 and wxWidgets 2.6.3
> > >
> > > --
> > > Eric Kow                     http://www.loria.fr/~kow<http://www.lori=
a.fr/%7Ekow>
> > > PGP Key ID: 08AC04F9         Merci de corriger mon fran=E7ais.
> > >
> > >
> > >
> >
>

[wxhaskell-users] embedding icons into executable under CYGWIN

[Artem Gr <ar...@bi...>]

Here is my experience of embedding .ico files into executable:

Write and compile the resource file with several named icons as described in
http://www.wxwidgets.org/wiki/index.php/Cross-Compiling_Windows_Resources
(windres.exe is provided with the CYGWIN).

A part of my resource file:

ico1_normal ICON "src/PENCL01J.ICO"
ico2_noPing ICON "src/PAINT05B.ICO"

Compiling it into an object file:

$ windres src/resources.rc src/resources.o

Linking it into the Haskell program:

$ ghc --make src/*.hs src/resources.o

Using the linked icon from Haskell:

  ico <- iconCreateLoad "ico1_normal" wxBITMAP_TYPE_ICO_RESOURCE (sz 32 32)
  f <- frame [text := "Frame title goes here.", visible := False]
  frameSetIcon f ico

Re: [wxhaskell-users] strings truncated to one character in wxhaskell-0.10.1 under ghc-6.6

[Conal E. <co...@co...>]

oops -- premature send.

any advice?  what configure options do you use for wxWidgets-2.6.3?

Thanks,   - Conal



On 12/4/06, Conal Elliott <co...@co...> wrote:
>
> Thanks for the tips, Eric.  I've built & installed wxWidgets 2.6.3(config=
uring with --with-msw
> --disable-shared --with-opengl --enable-unicode).  When I compile
> wxHaskell (configuring with --prefix=3D/usr/local --with-opengl), I get a=
 host
> of errors, such as
>
> C:/cygwin/usr/local/include/wx/chkconf.h:100:9: #error "wxUSE_PROLOGIO
> must be defined."
> C:/cygwin/usr/local/include/wx/chkconf.h:488:9: #error "wxUSE_NEW_GRID
> must be defined."
> C:/cygwin/usr/local/include/wx/chkconf.h:1184:9: #error
> "wxUSE_DYNAMIC_CLASSES must be defined as 1"
>
> and
>
> C:/cygwin/usr/local/include/wx/object.h:438: `wxClassInfo' was not
> declared in this scope
> C:/cygwin/usr/local/include/wx/object.h:438: `info' was not declared in
> this  scope
> C:/cygwin/usr/local/include/wx/object.h:438: invalid data member
> initialization
>
>
>
>
> On 12/2/06, Eric Y. Kow <eri...@gm...> wrote:
> >
> > On Thu, Nov 30, 2006 at 14:26:43 -0800, Conal Elliott wrote:
> > > I don't know whether Unicode was enabled in my wxWidgets build.  I
> > have
> > > wxWidgets 2.4.2 and configured compilation without any mention of
> > unicode.
> > > Would I want unicode enabled or disabled?
> >
> > You want it enabled
> >
> > > I just tried a clean build & install with --enable-unicode and one
> > with
> > > --disable-unicode, and I got the same truncation behavior in both
> > cases.
> >
> > You might also want to make sure that wxhaskell is using the wxWidgets
> > you think it's using.  You can set this explicitly with ./configure
> > --wx-config=3D/the/path/to/your/wxWidgets
> >
> > > What is the ideal version of wxWidgets and what are the ideal build
> > > configuration parameters for wxWidgets & wxHaskell with ghc-6.6?
> >
> > > And does anyone have wxHaskell working correctly (not just compiling)
> > with
> > > ghc-6.6?
> >
> > It has worked for me in the past with 2.4.2 and ghc-6.4.1, and it seems
> > to be working for me with ghc-6.6 and wxWidgets 2.6.3
> >
> > --
> > Eric Kow                     http://www.loria.fr/~kow<http://www.loria.=
fr/%7Ekow>
> > PGP Key ID: 08AC04F9         Merci de corriger mon fran=E7ais.
> >
> >
> >
>

Re: [wxhaskell-users] strings truncated to one character in wxhaskell-0.10.1 under ghc-6.6

[Conal E. <co...@co...>]

Thanks for the tips, Eric.  I've built & installed wxWidgets
2.6.3(configuring with --with-msw
--disable-shared --with-opengl --enable-unicode).  When I compile wxHaskell
(configuring with --prefix=3D/usr/local --with-opengl), I get a host of
errors, such as

C:/cygwin/usr/local/include/wx/chkconf.h:100:9: #error "wxUSE_PROLOGIO must
be defined."
C:/cygwin/usr/local/include/wx/chkconf.h:488:9: #error "wxUSE_NEW_GRID must
be defined."
C:/cygwin/usr/local/include/wx/chkconf.h:1184:9: #error
"wxUSE_DYNAMIC_CLASSES must be defined as 1"

and

C:/cygwin/usr/local/include/wx/object.h:438: `wxClassInfo' was not declared
in this scope
C:/cygwin/usr/local/include/wx/object.h:438: `info' was not declared in
this  scope
C:/cygwin/usr/local/include/wx/object.h:438: invalid data member
initialization




On 12/2/06, Eric Y. Kow <eri...@gm...> wrote:
>
> On Thu, Nov 30, 2006 at 14:26:43 -0800, Conal Elliott wrote:
> > I don't know whether Unicode was enabled in my wxWidgets build.  I have
> > wxWidgets 2.4.2 and configured compilation without any mention of
> unicode.
> > Would I want unicode enabled or disabled?
>
> You want it enabled
>
> > I just tried a clean build & install with --enable-unicode and one with
> > --disable-unicode, and I got the same truncation behavior in both cases=
.
>
>
> You might also want to make sure that wxhaskell is using the wxWidgets
> you think it's using.  You can set this explicitly with ./configure
> --wx-config=3D/the/path/to/your/wxWidgets
>
> > What is the ideal version of wxWidgets and what are the ideal build
> > configuration parameters for wxWidgets & wxHaskell with ghc-6.6?
>
> > And does anyone have wxHaskell working correctly (not just compiling)
> with
> > ghc-6.6?
>
> It has worked for me in the past with 2.4.2 and ghc-6.4.1, and it seems
> to be working for me with ghc-6.6 and wxWidgets 2.6.3
>
> --
> Eric Kow                     http://www.loria.fr/~kow<http://www.loria.fr=
/%7Ekow>
> PGP Key ID: 08AC04F9         Merci de corriger mon fran=E7ais.
>
>
>

Re: [wxhaskell-users] wxHaskell Status

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

Hi Wouter,

Some long overdue updates on what I am doing (and why) in-line. By the
way, if anyone thinks that whay I am doing is the wrong way to go,
please chime in (preferably with a constructive alternative).

On 03/12/06, Wouter Swierstra <ws...@cs...> wrote:
>
> I was curious what the status of wxhaskell is now. I realize that
> there's been a lot of progress and you guys have set up a new darcs
> repository. Is there a new release that has been tested on different
> platforms and is known to work well with certain versions of ghc and
> wxWidgets?

We're not yet ready for a release. The sources out of darcs can be
successfully built on Linux/OSX/Windows (I can personally vouch for
OSX and Windows) but there are enough wrinkles that stop it from
working 'out of the box' that it can't really be called 'ready'.

> Will there be binaries available any time soon?

Not until we are confident about making something which 'always works'.

> A lot of
> people seem to be having trouble with disable/enable unicode - now
> would be a good time to update the homepage, bring the build
> instructions up to date, and get a new version out there.

The main issue seems to be that although the wxHaskell sources
themselves are very solid indeed (and Eric has been doing a superb job
in ensuring the quality of what goes into darcs), it's too easy to get
the build wrong and end up with something which appears to compile and
link, but then does not work.

OS X seems to be particularly susceptible to this, and after the
problems Stefan Holdermans reported a week or two back, I have
diverted into looking into why the OS X build is so fragile. I don't
yet have a reason,but I'm definitely seeing unexpected linker
behaviour with some build scenarios which I am trying to get to the
bottom of. We were able to get Stafan going by creating a statically
linked build variant, but I would like to understand why the
dynamically linked version is so sensitive to the options used to
build wxWidgets.

Before I was diverted onto the OS X build, I was looking at
Cabalization (assuming that such a word exists...)

One of the key issues raised by GHC 6.6 was that it breaks the
wxHaskell build system due to the way in which the wxc, wxCore and wx
libraries are built and installed. There is a work-around in darcs
(from shelarcy - basically do the build in several stages), but this
is not really satisfactory for the longer term.

My original idea was to do the whole build with Cabal, but this really
isn't an option for the wxc wrapper as Cabal is poorly equipped for
building complex C codebases (not really a criticism - it is the
*Haskell* Cabal!).

I've therefore moved to separate the build of wxc from the remainder
of wxHaskell. This is probably sensible as wxc is not really tied in
any way to Haskell, and should probably stand alone in the longer term
(c.f. wxc.sourceforge.net, which exists, but is not currently very
active).

This means splitting the wxHaskell makefile so that it contains only
the parts needed to build wxc, which I have done for OS X and Unix (OK
- it was the easy part, but I still want to be sure about OS X
stability), and am in the process of doing for Windows (I'm getting
rid of the VC++ project files which required the user to edit a
machine-generated file which says 'do not edit' at the top and
replacing with an NMAKE makefile). This should make Windows builds
much easier to do as the bits which might need to be edited are all in
one place (can't auto-detect on Windows as on Unix, unfortunately). It
will (I think) also have the benefit that it should be possible to
build wxC with only the free versions of the Microsoft tools.

One note I should make regarding the wxC parts: the wxc maintainers on
Sourceforge have not chosen to use Make.  They have, instead, chosen
to use Geant which is, I think, an Eiffel-based 'Ant-alike'. I can't
agree with this, and prefer to have a few dependencies as possible for
the build system. The wxC library needs no more than a C++ compiler
and make to build it; anyone likely to be interested in wxC will
already have these. Using any other build system just multiplies
dependencies and ensures that anyone interested is more likely to give
up. Cabal is OK for Haskell-specific parts as it's part of the
distribution. Anyway,I already know and loathe make ;-)

Last part, which I haven't finished, is Cabalization of the Haskell
parts, which should make the Haskell build much more maintainable. The
hard bit is wxDirect (or rather, running it over wxC library to
generate the WX.Core sources) in Cabal. This requires me to write a
bit more code than I expected, and so it's taking some time.

Anyway, I've probably gone completely off-topic in answering you, but
that's what I am getting up to.

Regards
Jeremy

[wxhaskell-users] wxHaskell Status

[Wouter S. <ws...@cs...>]

Hiya,

I was curious what the status of wxhaskell is now. I realize that  
there's been a lot of progress and you guys have set up a new darcs  
repository. Is there a new release that has been tested on different  
platforms and is known to work well with certain versions of ghc and  
wxWidgets? Will there be binaries available any time soon? A lot of  
people seem to be having trouble with disable/enable unicode - now  
would be a good time to update the homepage, bring the build  
instructions up to date, and get a new version out there. I, for one,  
am a bit hesitant to invest too much effort in getting wxHaskell  
running as long as it is still very much in a state of flux.

Thanks again!

   Wouter 

Re: [wxhaskell-users] strings truncated to one character in wxhaskell-0.10.1 under ghc-6.6

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

On Thu, Nov 30, 2006 at 14:26:43 -0800, Conal Elliott wrote:
> I don't know whether Unicode was enabled in my wxWidgets build.  I have
> wxWidgets 2.4.2 and configured compilation without any mention of unicode.
> Would I want unicode enabled or disabled?

You want it enabled

> I just tried a clean build & install with --enable-unicode and one with
> --disable-unicode, and I got the same truncation behavior in both cases.

You might also want to make sure that wxhaskell is using the wxWidgets
you think it's using.  You can set this explicitly with ./configure
--wx-config=3D/the/path/to/your/wxWidgets

> What is the ideal version of wxWidgets and what are the ideal build
> configuration parameters for wxWidgets & wxHaskell with ghc-6.6?

> And does anyone have wxHaskell working correctly (not just compiling) with
> ghc-6.6?

It has worked for me in the past with 2.4.2 and ghc-6.4.1, and it seems
to be working for me with ghc-6.6 and wxWidgets 2.6.3

--=20
Eric Kow                     http://www.loria.fr/~kow
PGP Key ID: 08AC04F9         Merci de corriger mon fran=E7ais.

[wxhaskell-users] Does anyone use wxHaskell with ghc-6.6?

[Conal E. <co...@co...>]

I'd love to hear from anyone who has wxHaskell & ghc-6.6 working together.
I'm stuck on a Unicode issue (apparently), as mentioned in my previous
message.  - Conal

Re: [wxhaskell-users] Undefined reference to wxGLCanvas::*

[Bas v. D. <bas...@ho...>]

On Thursday 30 November 2006 19:35, ami...@st... wrote:
> I "solved" this on my linux install by passing the --with-opengl flag to
> the configure script.

Yes, I tried that but it didn't help.

Bas.

Re: [wxhaskell-users] strings truncated to one character in wxhaskell-0.10.1 under ghc-6.6

[Conal E. <co...@co...>]

I don't know whether Unicode was enabled in my wxWidgets build.  I have
wxWidgets 2.4.2 and configured compilation without any mention of unicode.
Would I want unicode enabled or disabled?

I just tried a clean build & install with --enable-unicode and one with
--disable-unicode, and I got the same truncation behavior in both cases.

What is the ideal version of wxWidgets and what are the ideal build
configuration parameters for wxWidgets & wxHaskell with ghc-6.6?

And does anyone have wxHaskell working correctly (not just compiling) with
ghc-6.6?

  - Conal

On 11/30/06, Eric Kow <eri...@gm...> wrote:
>
> Is you wxWidgets Unicode-enabled?  That might fit in with what Daan is
> saying: we are sending whar_t, 4 bytes at a time, so you'll be getting
> something that looks like char NULL NULL NULL.
>
> On 11/30/06, Conal Elliott <co...@co...> wrote:
> > "I guess your strings get sent as unicode but by the fields function
> > interpreted as ascii in which case the second byte is zero and thus you
> see
> > only 1 character. The string should be converted to utf-8 probably and
> > perhaps they forgot this function."
> --
> Eric Kow                     http://www.loria.fr/~kow
> PGP Key ID: 08AC04F9         Merci de corriger mon fran=E7ais.
>

Re: [wxhaskell-users] Undefined reference to wxGLCanvas::*

[<ami...@st...>]

I "solved" this on my linux install by passing the --with-opengl flag to
the configure script.

> On 11/30/06, Bas van Dijk <bas...@ho...> wrote:
>> bas@bassbox ~/development/haskell/wxhaskell/samples/wx $ make
>> ghc -package wx -o BouncingBalls BouncingBalls.hs
>> /usr/lib/libwxc-gtk2.6.2-0.10.1.so: undefined reference to
>> `wxGLCanvas::SwapBuffers()'
>
> On the Debian-based Linuxes, I get around this by installing the
> package freeglut3-dev
>
> Does that help? (On the other hand, I don't fully understand why it
> should be neccesary)
>
> --
> Eric Kow                     http://www.loria.fr/~kow
> PGP Key ID: 08AC04F9         Merci de corriger mon fran=C3=A7ais.
> -----------------------------------------------------------------------=
--
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share
> your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D=
DEVDEV
> _______________________________________________
> wxhaskell-users mailing list
> wxh...@li...
> https://lists.sourceforge.net/lists/listinfo/wxhaskell-users
>

Re: [wxhaskell-users] Undefined reference to wxGLCanvas::*

[Bas v. D. <bas...@ho...>]

> On the Debian-based Linuxes, I get around this by installing the
> package freeglut3-dev
>
> Does that help? (On the other hand, I don't fully understand why it
> should be neccesary)

I installed the latest freeglut-2.4.0 [1] and build wxHaskell again. But the 
examples still fail with the same error.

Bas

[1] http://freeglut.sourceforge.net

Re: [wxhaskell-users] Undefined reference to wxGLCanvas::*

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

T24gMTEvMzAvMDYsIEJhcyB2YW4gRGlqayA8YmFzdmFuZGlqa0Bob21lLm5sPiB3cm90ZToKPiBi
YXNAYmFzc2JveCB+L2RldmVsb3BtZW50L2hhc2tlbGwvd3hoYXNrZWxsL3NhbXBsZXMvd3ggJCBt
YWtlCj4gZ2hjIC1wYWNrYWdlIHd4IC1vIEJvdW5jaW5nQmFsbHMgQm91bmNpbmdCYWxscy5ocwo+
IC91c3IvbGliL2xpYnd4Yy1ndGsyLjYuMi0wLjEwLjEuc286IHVuZGVmaW5lZCByZWZlcmVuY2Ug
dG8KPiBgd3hHTENhbnZhczo6U3dhcEJ1ZmZlcnMoKScKCk9uIHRoZSBEZWJpYW4tYmFzZWQgTGlu
dXhlcywgSSBnZXQgYXJvdW5kIHRoaXMgYnkgaW5zdGFsbGluZyB0aGUKcGFja2FnZSBmcmVlZ2x1
dDMtZGV2CgpEb2VzIHRoYXQgaGVscD8gKE9uIHRoZSBvdGhlciBoYW5kLCBJIGRvbid0IGZ1bGx5
IHVuZGVyc3RhbmQgd2h5IGl0CnNob3VsZCBiZSBuZWNjZXNhcnkpCgotLSAKRXJpYyBLb3cgICAg
ICAgICAgICAgICAgICAgICBodHRwOi8vd3d3LmxvcmlhLmZyL35rb3cKUEdQIEtleSBJRDogMDhB
QzA0RjkgICAgICAgICBNZXJjaSBkZSBjb3JyaWdlciBtb24gZnJhbsOnYWlzLgo=

[wxhaskell-users] Undefined reference to wxGLCanvas::*

[Bas v. D. <bas...@ho...>]

Hello,

When making the wx samples I got the following error:

bas@bassbox ~/development/haskell/wxhaskell/samples/wx $ make
ghc -package wx -o BouncingBalls BouncingBalls.hs
/usr/lib/libwxc-gtk2.6.2-0.10.1.so: undefined reference to 
`wxGLCanvas::SwapBuffers()'
/usr/lib/libwxc-gtk2.6.2-0.10.1.so: undefined reference to 
`wxGLCanvas::SetColour(wchar_t const*)'
/usr/lib/libwxc-gtk2.6.2-0.10.1.so: undefined reference to 
`wxGLCanvas::wxGLCanvas(wxWindow*, wxGLCanvas const*, int, wxPoint const&, 
wxSize const&, long, wxString const&, int*, wxPalette const&)'
/usr/lib/libwxc-gtk2.6.2-0.10.1.so: undefined reference to 
`wxGLCanvas::SetCurrent()'
/usr/lib/libwxc-gtk2.6.2-0.10.1.so: undefined reference to 
`wxGLCanvas::wxGLCanvas(wxWindow*, int, wxPoint const&, wxSize const&, long, 
wxString const&, int*, wxPalette const&)'
collect2: ld returned 1 exit status
make: *** [BouncingBalls] Error 1

I configured wxHaskell --with-opengl and my wxWindows implementation (on 
Gentoo Linux) has OpenGL support:

emerge x11-libs/wxGTK -vp

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild   R   ] x11-libs/wxGTK-2.6.2-r1  USE="X doc joystick opengl sdl 
unicode -debug -gnome -odbc" 0 kB

What is wrong here?

Bas van Dijk.

Re: [wxhaskell-users] strings truncated to one character in wxhaskell-0.10.1 under ghc-6.6

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

SXMgeW91IHd4V2lkZ2V0cyBVbmljb2RlLWVuYWJsZWQ/ICBUaGF0IG1pZ2h0IGZpdCBpbiB3aXRo
IHdoYXQgRGFhbiBpcwpzYXlpbmc6IHdlIGFyZSBzZW5kaW5nIHdoYXJfdCwgNCBieXRlcyBhdCBh
IHRpbWUsIHNvIHlvdSdsbCBiZSBnZXR0aW5nCnNvbWV0aGluZyB0aGF0IGxvb2tzIGxpa2UgY2hh
ciBOVUxMIE5VTEwgTlVMTC4KCk9uIDExLzMwLzA2LCBDb25hbCBFbGxpb3R0IDxjb25hbEBjb25h
bC5uZXQ+IHdyb3RlOgo+ICJJIGd1ZXNzIHlvdXIgc3RyaW5ncyBnZXQgc2VudCBhcyB1bmljb2Rl
IGJ1dCBieSB0aGUgZmllbGRzIGZ1bmN0aW9uCj4gaW50ZXJwcmV0ZWQgYXMgYXNjaWkgaW4gd2hp
Y2ggY2FzZSB0aGUgc2Vjb25kIGJ5dGUgaXMgemVybyBhbmQgdGh1cyB5b3Ugc2VlCj4gb25seSAx
IGNoYXJhY3Rlci4gVGhlIHN0cmluZyBzaG91bGQgYmUgY29udmVydGVkIHRvIHV0Zi04IHByb2Jh
Ymx5IGFuZAo+IHBlcmhhcHMgdGhleSBmb3Jnb3QgdGhpcyBmdW5jdGlvbi4iCi0tIApFcmljIEtv
dyAgICAgICAgICAgICAgICAgICAgIGh0dHA6Ly93d3cubG9yaWEuZnIvfmtvdwpQR1AgS2V5IElE
OiAwOEFDMDRGOSAgICAgICAgIE1lcmNpIGRlIGNvcnJpZ2VyIG1vbiBmcmFuw6dhaXMuCg==

Re: [wxhaskell-users] strings truncated to one character in wxhaskell-0.10.1 under ghc-6.6

[Conal E. <co...@co...>]

Daan's take:

"I guess your strings get sent as unicode but by the fields function
interpreted as ascii in which case the second byte is zero and thus you see
only 1 character. The string should be converted to utf-8 probably and
perhaps they forgot this function."

Is anyone using wxhaskell and ghc-6.6?  If so, are you getting the same
problem?  Fix?  Work-around?

  - Conal

On 11/29/06, Conal Elliott <co...@co...> wrote:
>
> I grabbed & built the latest wxhaskell from http://darcs.haskell.org and
> recompiled an app, all under ghc-6.6 .   My labels and text fields are
> getting truncated to a single character.  Any ideas?  Thanks,  - Conal
>

[wxhaskell-users] strings truncated to one character in wxhaskell-0.10.1 under ghc-6.6

[Conal E. <co...@co...>]

I grabbed & built the latest wxhaskell from http://darcs.haskell.org and
recompiled an app, all under ghc-6.6.   My labels and text fields are
getting truncated to a single character.  Any ideas?  Thanks,  - Conal

[wxhaskell-users] darcs patch: Add an eyeball test for Unicode strings.

[Eric K. <eri...@lo...>]

Wed Nov 29 05:22:30 CET 2006  Eric Kow <eri...@lo...>
  * Add an eyeball test for Unicode strings.

[wxhaskell-users] patches accepted 2006-11-25

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

Accepted since the last cycle (2)
---------------------------------
Wed Nov 15 13:10:06 CET 2006  Arie Middelkoop <ar...@cs...>
  * Added the -fPIC compiler flag to CXX options in the makefile.
 =20
Sat Nov 25 13:56:28 CET 2006  Arie Middelkoop <ar...@cs...>
  * Use intptr_t to avoid assumption that integers are 32 bit.
 =20
Please resend any patches I may have missed

--=20
Eric Kow                     http://www.loria.fr/~kow
PGP Key ID: 08AC04F9         Merci de corriger mon fran=E7ais.

Re: [wxhaskell-users] darcs patch: Added the -fPIC compiler flag to CXX opt... (and 1 more)

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

Hi,

I'm going to push a slightly modified version of this patch in.
The only modification is in the description.  Arie, you'll want
to obliterate your version of the patch so that it does not
conflict with the one I push in.

The patch seems to make sense (although I must point out I haven't done
any C coding since the late 90s and can't really claim to know what I'm
talking about).  I found this bit of explanation on the web helpful:

  Any valid pointer to an object (the original C99 text speaks of "any
  valid pointer to void") can be converted to this type, and then
  converted back safely to void *. The result must compare equal to the
  original pointer. In other words, intptr_t legalizes a popular yet
  non-portable tradition of converting data pointers to integral types,
  and vice versa.

--=20
Eric Kow                     http://www.loria.fr/~kow
PGP Key ID: 08AC04F9         Merci de corriger mon fran=E7ais.

Re: [wxhaskell-users] No text displayed in widgets

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

On 21/11/06, Eric Y. Kow <eri...@gm...> wrote:
> On Tue, Nov 21, 2006 at 19:17:51 +0100, Stefan Holdermans wrote:
> > I have a problem with wxHaskell (checked out from darcs a week ago)
> > running on Mac OS X 10.4.8: my GUIs refuse to display any text at all.
> >
> > For instance, the following program,
>
> Hmm.  I can't reproduce this.  What wxWidgets are you using?  Is it
> Unicode-enabled?  I've got the one from MacPorts.

I've certainly run into something similar to this on my Mac long ago -
using the wxWidgets which is pre-installed on the Mac (a variant of
wxWidgets 2.5.x, I think) - you need to ensure that wxHaskell is
compiled with the same Unicode (or not) configuration as your
wxWidgets library. The Mac provided version does require Unicode.

Regards
Jeremy

Re: [wxhaskell-users] No text displayed in widgets

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

On Tue, Nov 21, 2006 at 19:17:51 +0100, Stefan Holdermans wrote:
> I have a problem with wxHaskell (checked out from darcs a week ago) =20
> running on Mac OS X 10.4.8: my GUIs refuse to display any text at all.
>=20
> For instance, the following program,

Hmm.  I can't reproduce this.  What wxWidgets are you using?  Is it
Unicode-enabled?  I've got the one from MacPorts.

--=20
Eric Kow                     http://www.loria.fr/~kow
PGP Key ID: 08AC04F9         Merci de corriger mon fran=E7ais.

[wxhaskell-users] No text displayed in widgets

[Stefan H. <st...@cs...>]

I have a problem with wxHaskell (checked out from darcs a week ago)  
running on Mac OS X 10.4.8: my GUIs refuse to display any text at all.

For instance, the following program,

 > import Graphics.UI.WX
 >
 > main :: IO ()
 > main =  start gui
 >
 > gui :: IO ()
 > gui =  do
 >   frame [text := "Hello"]
 >   return ()

yields an empty frame with *no title* shown in the title bar.

Likewise, GUIs that feature buttons, labels, etc., display empty  
widgets, i.e., without the texts.

Is this a known issue? What can be done about it?

Cheers,

   Stefan