freetype-commit
[Top][All Lists]
Advanced

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

[Git][freetype/freetype][master] * docs/INSTALL: Mention Meson and MSBui


From: Alexei Podtelezhnikov (@apodtele)
Subject: [Git][freetype/freetype][master] * docs/INSTALL: Mention Meson and MSBuild more prominently.
Date: Thu, 04 Nov 2021 02:45:19 +0000

Alexei Podtelezhnikov pushed to branch master at FreeType / FreeType

Commits:

1 changed file:

Changes:

  • docs/INSTALL
    ... ... @@ -9,7 +9,8 @@ I. Prerequisites and dependencies
    9 9
     
    
    10 10
       FreeType is a low level C library  that only depends on the standard
    
    11 11
       C library with very few platform-dependent optimizations utilized at
    
    12
    -  build time.  System libraries, such as  zlib,  Gzip,  bzip2, Brotli,
    
    12
    +  build time.  Any  C89-compliant compiler  should be able  to compile
    
    13
    +  FreeType.  System libraries,  such as  zlib,  Gzip,  bzip2,  Brotli,
    
    13 14
       and libpng,  might  be  used  to handle  compressed fonts  or decode
    
    14 15
       embedded PNG glyphs.
    
    15 16
     
    
    ... ... @@ -38,15 +39,8 @@ II. Normal installation and upgrades
    38 39
     
    
    39 40
         GNU Make VERSION 3.81 OR NEWER IS NEEDED!
    
    40 41
     
    
    41
    -    [For `cmake' see below.]
    
    42 42
     
    
    43
    -
    
    44
    -  2. On VMS with the `mms' build tool
    
    45
    -
    
    46
    -    See `INSTALL.VMS' for installation instructions on this platform.
    
    47
    -
    
    48
    -
    
    49
    -  3. Other systems using GNU Make
    
    43
    +  2. Other systems using GNU Make
    
    50 44
     
    
    51 45
         On some  non-Unix platforms, it  is possible to build  the library
    
    52 46
         using only  the GNU Make utility.   Note that *NO OTHER  MAKE TOOL
    
    ... ... @@ -57,23 +51,30 @@ II. Normal installation and upgrades
    57 51
         Instructions are provided in the file `INSTALL.GNU'.
    
    58 52
     
    
    59 53
     
    
    54
    +  3. Other build tools and platforms.
    
    55
    +
    
    56
    +    A few other tools  can be used  to build FreeType.  You  can  find
    
    57
    +    the  corresponding instruction files  in  the FreeType root folder
    
    58
    +    or the builds/ sub-folder.
    
    59
    +
    
    60
    +      CMake   :: see CMakeLists.txt for more information
    
    61
    +      Meson   :: see meson.build for more information
    
    62
    +      MSBuild :: see builds/windows/vc2010/freetype.vcxproj
    
    63
    +      MMS     :: see vms_make.com and docs/INSTALL.VMS
    
    64
    +
    
    65
    +
    
    60 66
       4. With an IDE Project File (e.g., for Visual Studio or CodeWarrior)
    
    61 67
     
    
    62 68
         We provide a  small number of `project files'  for various IDEs to
    
    63 69
         automatically build  the library as  well.  Note that  these files
    
    64
    -    are  not supported  and only  sporadically maintained  by FreeType
    
    65
    -    developers, so don't expect them to work in each release.
    
    70
    +    are not actively supported by FreeType developers,  they can break
    
    71
    +    or become obsolete.
    
    66 72
     
    
    67 73
         To find them, have a  look at the content of the `builds/<system>'
    
    68 74
         directory, where <system> stands for your OS or environment.
    
    69 75
     
    
    70 76
     
    
    71
    -  5. Using cmake
    
    72
    -
    
    73
    -    See the top-level `CMakeLists.txt' file for more information.
    
    74
    -
    
    75
    -
    
    76
    -  6. From you own IDE, or own Makefiles
    
    77
    +  5. From you own IDE, or own Makefiles
    
    77 78
     
    
    78 79
         If  you  want  to  create   your  own  project  file,  follow  the
    
    79 80
         instructions   given  in  the   `INSTALL.ANY'  document   of  this
    


  • reply via email to

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