[Fribidi-discuss] Help with porting fribidi to Mac OS X
Dov Grobgeld
dov at imagic.weizmann.ac.il
Tue Apr 15 08:31:29 EST 2003
On Tue, Apr 15, 2003 at 05:33:39PM +0300, Nir Soffer wrote:
>
> I did a make install to a temp directory. I need your help with the
> files:
>
> ./bin:
> fribidi* - this is the command line tool. Can It work standalone?
> can I deliver *only this file* with a GUI that uses it to end users?
Of course you can execute an external command. But normally you write
your GUI in c-and link to the library. In another word, if you write
a GUI you don't need the executable.
>
> fribidi-config* - What that? --help does not really help :-)
Used for compilation. Do `fribidi-config --cflags` in a makefile to
get the c-compiler flags and `fribidi-config --libs` to get the library
flags.
>
> ./include:
> ./include/fribidi:
> lot of header files... - include files for projects using the library?
> ./lib:
> libfribidi.0.0.0.dylib* - dynamic library? how can I use it in my
> project?
> libfribidi.a - static library? how can I use it in my project?
> libfribidi.la* - libtool config file - why do we need libtool anyway?
>
> ./lib/pkgconfig:
> fribidi.pc - Whats that?
This is the next generation fribidi config.
Your questions are really general and related to any kind of library
on compiled under MacOS. I'm sure you can find information in a general
site that talks about porting to MacOS.
>
>
> What I want to do with fribidi:
> I want to create a tool for Mac OS X end users (read double clickable)
> to convert between visual Hebrew ISO-8859-8 and Windows-1255 or Unicode
> UTF-8 both ways, and maybe other fribidi tricks if needed later.
If it is for web use I discourage supporting visual Hebrew at all.
It is a disaster that should be banned as soon as possible. Tell your
users to update to a BiDi supporting browser asap.
Regards,
Dov
>
> I have two options:
> 1. Tzafrir Cohen figured that I should use the library in my project. I
> will need help on how to include the library in my code. Code examples
> would be great.
>
> 2. I was planning to use the command line tool. It is easy and well
> documented to use Cocoa (read OpenStep) to run a command line tool,
> write and read data from it using pipes etc. I can also create a quick
> solution by using AppleScript to run the command line tool.
>
> What do you think is the right direction?
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Fribidi-discuss mailing list
> Fribidi-discuss at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/fribidi-discuss
More information about the FriBidi
mailing list