Le 8 juin 09 à 18:47, BH a écrit :
I guess I'm not being clear. The only reason I use cocoAspell is
because right now that's what I think most users are doing, so that I
can be helpful when problems crop up. (Most users won't have developer
tools installed, and so macports is not an easy option for them.)
I think most people wold prefer LyX to work with the mac spellchecker
%-|
So if we can bundle static libaspell into LyX.app (along with some
dictionaries or a way to get dictionaries automatically -- which I
could probably do with the installer), can we ensure that LyX will use
it?
Yes, the static libaspell would be part of the LyX binary (so you
probably need
a ppc and a intel version).
-*-*-*-
(Later)
Now that I read more about the subject, I can't believe how
complicated apple
made it. Actually, they did all hey could to make static linking
difficult.
The question now is to understand what is the right way to make it work.
Normally it should be to copy libaspell.dylib into the framework and
link against it.
The question then is to know how we can tell the binary to look there
for its libs.
Let's say I have no idea right now about improving the situation...
JMarc
