freetype-commit
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Git][freetype/freetype][gsoc-anurag-docs-2023] [docs] Add documentation


From: Anurag Thakur (@AdbhutDev)
Subject: [Git][freetype/freetype][gsoc-anurag-docs-2023] [docs] Add documentation on compiling FreeType on an Android Device
Date: Sat, 01 Jul 2023 09:09:21 +0000

Anurag Thakur pushed to branch gsoc-anurag-docs-2023 at FreeType / FreeType

Commits:

  • c2fd294a
    by Anurag Thakur at 2023-07-01T14:38:53+05:30
    [docs] Add documentation on compiling FreeType on an Android Device
    

2 changed files:

Changes:

  • docs/.gitignore
    ... ... @@ -12,6 +12,7 @@ reference/
    12 12
     !INSTALL_MAC.md
    
    13 13
     !INSTALL_UNIX.md
    
    14 14
     !INSTALL_VMS.md
    
    15
    +!INSTALL_ANDROID.md
    
    15 16
     !MODIFYING.md
    
    16 17
     
    
    17 18
     # MkDocs Config file
    

  • docs/INSTALL_ANDROID.md
    1
    +# Compiling FreeType on Android using Termux
    
    2
    +
    
    3
    +If you want to test FreeType on arm devices, compiling it on an Android
    
    4
    +phone is one of the easiest ways.
    
    5
    +
    
    6
    +## 1. Compiling FreeType
    
    7
    +
    
    8
    +1. Install and open termux
    
    9
    +
    
    10
    +2. Update termux packages using:
    
    11
    +
    
    12
    +   ```bash
    
    13
    +   pkg update
    
    14
    +   pkg upgrade
    
    15
    +   ```
    
    16
    +   Select `y` if any configuration changes are asked
    
    17
    +
    
    18
    +3. Install `git`:
    
    19
    +
    
    20
    +   ```bash
    
    21
    +   pkg install git
    
    22
    +   ```
    
    23
    +4. Install packages required for compilation:
    
    24
    +
    
    25
    +   ```bash
    
    26
    +   pkg install automake autoconf libtool make clang binutils
    
    27
    +   ```
    
    28
    +
    
    29
    +5. Clone FreeType's git repository:
    
    30
    +
    
    31
    +   ```bash
    
    32
    +   git clone https://gitlab.freedesktop.org/freetype/freetype.git
    
    33
    +   ```
    
    34
    +
    
    35
    +6. Enter into the source directory:
    
    36
    +
    
    37
    +   ```
    
    38
    +   cd freetype/
    
    39
    +   ```
    
    40
    +
    
    41
    +7. Now you can compile FreeType according to [INSTALL_UNIX.md]:
    
    42
    +
    
    43
    +   ```bash
    
    44
    +   ./autogen.sh
    
    45
    +   ./configure
    
    46
    +   make -j$(nproc)
    
    47
    +   ```
    
    48
    +   The compiled binaries can be accessed under `objs/.libs`
    
    49
    +
    
    50
    +## 2. Compiling FreeType Demo programs
    
    51
    +If you need to test your changes you may want to use ft-demo
    
    52
    +programs. They can be compiled and run by follwing these steps:
    
    53
    +
    
    54
    +1. First compile FreeType using the steps above.
    
    55
    +
    
    56
    +2. Clone FreeType demos adjacent to the `freetype/` directory:
    
    57
    +
    
    58
    +   ```bash
    
    59
    +   git clone https://gitlab.freedesktop.org/freetype/freetype-demos.git
    
    60
    +   ```
    
    61
    +   i.e. If you can access FreeType repo under `~/freetype`, you should
    
    62
    +   be able to access `~/freetype-demos`.
    
    63
    +
    
    64
    +3. Enter into the ft-demos directory:
    
    65
    +
    
    66
    +   ```bash
    
    67
    +   cd freetype-demos
    
    68
    +   ```
    
    69
    +
    
    70
    +4. Compile the programs:
    
    71
    +
    
    72
    +   ```bash
    
    73
    +   make
    
    74
    +   ```
    
    75
    +
    
    76
    +5. The compiled binaries can be accessed and executed under `bin/` like:
    
    77
    +
    
    78
    +   ```bash
    
    79
    +   cd bin
    
    80
    +   ./ftlint
    
    81
    +   ```
    
    82
    +
    
    83
    +<!---->
    
    84
    +
    
    85
    +[INSTALL_UNIX.md]: ./INSTALL_UNIX.md


  • reply via email to

    [Prev in Thread] Current Thread [Next in Thread]