/docs/build.txt

 1ftk/README has described the general steps of building, here are some special
 2configure options for FTK:
 3
 4--enable-cairo
 5
 6build with cairo support.
 7
 8--enable-bidi
 9
10build with bidi support(NOT tested yet)
11
12--enable-opengles
13build with opengles support.
14
15--enable-tslib  
16
17build with tslib support, tslib is a library to handle touchscreen event, 
18if you has a resistive touchscreen, you should enable this option.
19
20--with-fontengine 
21
22there are two options: default and freetype, generally freetype is better
23choise, but if you don't want to depend on freetype, or freetype is
24unavailable, use default instead.
25
26--with-backend
27
28backend means how to display bitmap on the screen and how to get the input
29device events. there are three options now:
30
31linux-x11:WxH With this option, FTK will run on X11 for emulation. W and H is
32the width and height of the emulator. For exmaple, with the following value,
33it will create a emulation window with 320 pixels width and 480 pixels height.
34
35--with-backend=linux-x11:320x480
36
37linux-fb With this option, FTK will run on linux framebuffer, this is
38default value.
39
40linux-st7781 With this option, FTK will run on linux with lcm st7781
41
42linux-vlcd   With this option, FTK will run on virtual framebuffer. I wrote a
43emulator for FTK base on memfb and uinput, with a vnc server and vncviever,
44FTK can run on VNC.
45
46linux-dfb With this option, FTK will run on DirectFB, FTK does not use
47DirectFB Windows system, just use it to abstract display and input device, so
48you can utilize DirectFB hardware acceleration.
49
50See tools/cross-build/README for cross building.
51