Hi,
On Tue, 18 Jun 2002, Shachar Shemesh wrote: [snip] > A. If Fribidi was present during compile, check for its existance during > run time. If not present, don't enable the run time option. > or > B. Copy (port?) Fribidi into the WINE code. It's LGPL, so the license > does allow that. C. If Fribidi was present during compile, link it statically, so that there will be no dependency on fribidi for WINE package. The consequence of B and C is that WINE will not use the latest fribidi on machine. But that may be right, since I wonder if you are going to convert UTF32<->UTF16 all way. You need a 16bit fribidi, means a somehow self-taylored version, so go with B and install a 16bit fribidi on your compile machine, and build WINE. No license problem, and I will let you know of fribidi new releases ;-). > The consequence of B is that I will need to keep an eye on Fribidi, and > keep it up to date whenever something changes there. I am very reluctant > to do so. I would much rather go for the "A" solution. The problem is > that I know how to do this in Windows, but not in Linux. Any help anyone > can offer me? > Shachar -- Behdad Esfahbod 28 Khordad 1381, 2002 Jun 18 http://behdad.org/ [Finger for Geek Code] Today is a good day for information-gathering. Read someone else's mail file. ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
