On Sat, Aug 08, 2009 at 18:36:10 -0500, Brian Lewis wrote:
> > In the darcs version of wxHaskell, I've also attempted to split
> > wxcore off so that it is cleanly Cabalised (just the Simple build
> > method), but I haven't worked out how to make it point the wxc
> > package that we would have to build separately.
> 
> Could you explain a little more? I don't understand the part after "I
> haven't worked out how ...".

I'm dimly aware that we build this wxc library that wxcore is
dynamically linked against (I think), that we seem to give this library
a different name depending on what wxWidgets we build against (for
example, on my Mac, I have libwxc-mac2.8.7-0.11.1.3.dylib, whereas on
Linux, I have libwxc-gtk2.8.8-0.11.0.so), and that we tend to install
this library in the same place that wxWidget's wx-config program
lives (eg /usr/local/wxhaskell/lib on my Mac because I've symlinked
wx-config into the /usr/local/wxhaskell/bin directory for convenience,
but /usr/lib on my Ubuntu box (yuck!) because I forgot to do the same).

I also know that somehow on my Mac the wxcore package has this
information:
  library-dirs: /usr/local/wxhaskell/lib
  hs-libraries: wxcore wxcore0 wxcore1 wxcore2
  extra-libraries: wxc-mac2.8.7-0.11.1.2

And I vaguely recall that this is due to some ghc-pkg specific file
that we generate from our Makefile.

I don't remember what these wxcore wxcore0 wxcore1 wxcore2 libraries
are, unfortunately.

> > Try it and see what I mean.  I'm sure it's not a hard problem to
> > solve; we just need somebody that's got 2 hours to stare at the
> > problem, poke it in the right place.  Can you help?
> 
> I'd be happy to try. I'll take a look and write back.

Are you starting to see what I'm getting at?  I'm sorry if I'm
being unclear; it's because I just don't have a good grasp on
what all the pieces are and how they all fit together.  I'll
bet we can do things to make this simpler though.

One hope was to be able to dissociate wxc from wxcore, but I don't even
know if this is actually a good idea or potentially foolish.  If we do
this, then we're going to have to find some way for pick up this wxc
library for linking whenever we build a wxHaskell program.  Surely this
sort of thing has been solved before by other Haskell libraries that
wrap around some C library!

-- 
Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow>
PGP Key ID: 08AC04F9

Attachment: pgpkNwmcLfaaa.pgp
Description: PGP signature

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
wxhaskell-users mailing list
wxhaskell-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wxhaskell-users

Reply via email to