On 21-jan-2007, at 0:51, Eric Y. Kow wrote:

On Fri, Jan 19, 2007 at 18:05:53 +0100, Arthur van Leeuwen wrote:
The issue occurs when trying to link: I run into not having
definitions for
what looks like *all* of the wxwidgets C++ symbols, even though the ldd
for libwxc shows that libwx is being linked to. I've pasted an
attempt to
compile samples/wxcore/HelloWorld.hs below, as well as the ldd for
my libwxc.

I've just discovered that on Debian/Ubuntu, this problem goes away if
I configure wxhaskell --with-opengl

Right, that did the trick. What the hell is happening there though? Adding -lwx_gtk2* for all libwx_gtk2* did not fix it, where reconfiguring wxhaskell
did...

It seems like this sort of thing should be handled automatically by
wxhaskell though.  Seems like one shouldn't have to throw in funny
configure switches just to make something compile.

I fully agree. Thanks!

Doei, Arthur.

--

/\ / | [EMAIL PROTECTED] | Work like you don't need the money /__\ / | A friend is someone with whom | Love like you have never been hurt / \/__ | you can dare to be yourself | Dance like there's nobody watching



Attachment: PGP.sig
Description: This is a digitally signed message part

-------------------------------------------------------------------------
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=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
wxhaskell-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wxhaskell-users

Reply via email to