summary refs log tree commit diff
path: root/pkgs/development/libraries/freetype
Commit message (Collapse)AuthorAge
* treewide: Remove unnecessary `--disable-static` (#66759)Niklas Hambüchen2019-08-31
| | | | | | | | | | | | | | * freetype: Remove unnecessary `--disable-static`. The true-by-default `dontDisableStatic` already takes care of it. Fixes freetype not being overridable to have static libs. * treewide: Remove unnecessary `--disable-static`. The true-by-default `dontDisableStatic` already takes care of it. Fixes these packages not being overridable to have static libs.
* freetype: undo formatting, esp since doesn't move to convention.Will Dietz2019-07-09
| | | | | | | Sorry, thanks for catching this in review! Leaving it as it was to keep this change simpler and friendlier to blame and such :).
* freetype: 2.10.0 -> 2.10.1Will Dietz2019-07-09
| | | | https://sourceforge.net/projects/freetype/files/freetype2/2.10.1/
* [treewide] delete unused patchesc0bw3b2019-05-04
|
* freetype2: 2.9.1 -> 2.10.0Will Dietz2019-03-15
| | | | http://lists.nongnu.org/archive/html/freetype-announce/2019-03/msg00000.html
* freetype: re-enable freetype-config, don't break all the thingsWill Dietz2019-01-16
|
* freetype: 2.9 -> 2.9.1Stephen2019-01-09
| | | exclude freetype-config
* freetype: fix cross-buildJörg Thalheim2018-11-28
|
* freetype: fix cross-compilation (#48352)volth2018-10-14
|
* Merge branch 'master' into unused5Jörg Thalheim2018-07-21
|\
| * [bot] treewide: remove unused 'inherit' in let blocksvolth2018-07-20
| |
* | pkgs/*: remove unreferenced function argumentsvolth2018-07-21
|/
* freetype: Remove crossAttrsJohn Ericson2018-05-10
| | | | | These sorts of C compiler confusions aren't really a problem anymore. Everything is on the path with the right environment variables.
* treewide: isArm -> isAarch32John Ericson2018-04-25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Following legacy packing conventions, `isArm` was defined just for 32-bit ARM instruction set. This is confusing to non packagers though, because Aarch64 is an ARM instruction set. The official ARM overview for ARMv8[1] is surprisingly not confusing, given the overall state of affairs for ARM naming conventions, and offers us a solution. It divides the nomenclature into three levels: ``` ISA: ARMv8 {-A, -R, -M} / \ Mode: Aarch32 Aarch64 | / \ Encoding: A64 A32 T32 ``` At the top is the overall v8 instruction set archicture. Second are the two modes, defined by bitwidth but differing in other semantics too, and buttom are the encodings, (hopefully?) isomorphic if they encode the same mode. The 32 bit encodings are mostly backwards compatible with previous non-Thumb and Thumb encodings, and if so we can pun the mode names to instead mean "sets of compatable or isomorphic encodings", and then voilà we have nice names for 32-bit and 64-bit arm instruction sets which do not use the word ARM so as to not confused either laymen or experienced ARM packages. [1]: https://developer.arm.com/products/architecture/a-profile
* freetype: fix freetype-configPiotr Bogdan2018-03-23
|
* freetype: 2.7.1 -> 2.9Nikolay Amiantov2018-03-06
|
* freetype default: Don't use stdenv.crosshsloan2017-06-28
|
* freetype: fix CVE-2017-{8105,8287} by upstream patchesVladimír Čunát2017-05-14
| | | | I copied the patches, as the changelog changes would certainly conflict.
* Merge branch 'master' into stagingDan Peebles2017-03-30
|\
| * Get rid of all `with { inherit... }` and just used `let inherit...`John Ericson2017-03-30
| | | | | | | | | | | | The old forms presumably predates, or were made in ignorance of, `let inherit`. This way is better style as the scoping as more lexical, something which Nix can (or might already!) take advantage of.
* | freetype: disable PCF long family namesThomas Tuegel2017-03-28
|/ | | | | Backported several patches from upstream. The test suite patch for Fontconfig is no longer necessary.
* freetype: 2.6.5 -> 2.7.1Thomas Tuegel2017-03-12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The Infinality bytecode interpreter is removed in favor of the new v40 TrueType interpreter. In the past, the Infinality interpreter provided support for ClearType-style hinting instructions while the default interpreter (then v35) provided support only for original TrueType-style instructions. The v40 interpreter corrects this deficiency, so the Infinality interpreter is no longer necessary. To understand why the Infinality interpreter is no longer necessary, we should understand how ClearType differs from TrueType and how the v40 interpreter works. The following is a summary of information available on the FreeType website [1] mixed with my own editorializing. TrueType instructions use horizontal and vertical hints to improve glyph rendering. Before TrueType, fonts were only vertically hinted; horizontal hints improved rendering by snapping stems to pixel boundaries. Horizontal hinting is a risk because it can significantly distort glyph shapes and kerning. Extensive testing at different resolutions is needed to perfect the TrueType hints. Microsoft invested significant effort to do this with its "Core fonts for the Web" project, but few other typefaces have seen this level of attention. With the advent of subpixel rendering, the effective horizontal resolution of most displays increased significantly. ClearType eschews horizontal hinting in favor of horizontal supersampling. Most fonts are designed for the Microsoft bytecode interpreter, which implements a compatibility mode with TrueType-style (horizontal and vertical) instructions. However, applying the full horizontal hints to subpixel-rendered fonts leads to color fringes and inconsistent stem widths. The Infinality interpreter implements several techniques to mitigate these problems, going so far as to embed font- and glyph-specific hacks in the interpreter. On the other hand, the v40 interpreter ignores the horizontal hinting instructions so that glyphs render as they are intended to on the Microsoft interpreter. Without the horizontal hints, the problems of glyph and kerning distortion, color fringes, and inconsistent stem widths--the problems the Infinality interpreter was created to solve--simply don't occur in the first place. There are also security concerns which motivate removing the Infinality patches. Although there is an updated version of the Infinality interpreter for FreeType 2.7, the lack of a consistent upstream maintainer is a security concern. The interpreter is a Turing-complete virtual machine which has had security vulnerabilities in the past. While the default interpreter is used in billions of devices and is maintained by an active developer, the Infinality interpreter is neither scrutinized nor maintained. We will probably never know if there are defects in the Infinality interpreter, and if they were discovered they would likely never be fixed. I do not think that is an acceptable situtation for a core library like FreeType. Dropping the Infinality patches means that font rendering will be less customizable. I think this is an acceptable trade-off. The Infinality interpreter made many compromises to mitigate the problems with horizontal hinting; the main purpose of customization is to tailor these compromises to the user's preferences. The new interpreter does not have to make these compromises because it renders fonts as their designers intended, so this level of customization is not necessary. The Infinality-associated patches are also removed from cairo. These patches only set the default rendering options in case they aren't set though Fontconfig. On NixOS, the rendering options are always set in Fontconfig, so these patches never actually did anything for us! The Fontconfig test suite is patched to account for a quirk in the way PCF fonts are named. The fontconfig option `hintstyle` is no longer configurable in NixOS. This option selects the TrueType interpreter; the v40 interpreter is `hintslight` and the older v35 interpreter is `hintmedium` or `hintfull` (which have actually always been the same thing). The setting may still be changed through the `localConf` option or by creating a user Fontconfig file. Users with HiDPI displays should probably disable hinting and antialiasing: at best they have no visible effect. The fontconfig-ultimate settings are still available in NixOS, but they are no longer the default. They still work, but their main purpose is to set rendering quirks which are no longer necessary and may actually be detrimental (e.g. setting `hintfull` for some fonts). Also, the vast array of font substitutions provided is not an appropriate default; the default setting should be to give the user the font they asked for. [1]. https://www.freetype.org/freetype2/docs/subpixel-hinting.html
* treewide: Shuffle outputsTuomas Tynkkynen2016-08-29
| | | | Make either 'bin' or 'out' the first output.
* freetype: re-add infinality patchesNikolay Amiantov2016-08-20
| | | | archfan has updated those patches for the new version.
* freetype: 2.6.2 -> 2.6.5cmfwyp2016-08-20
| | | | | | The fontconfig-ultimate patches are unmaintained. Since they were not updated for newer FreeType versions, this removes them and disables fontconfig-ultimate by default.
* freetype: add a long descriptioncmfwyp2016-08-20
|
* freetype: remove -fno-strict-aliasingcmfwyp2016-08-20
| | | | | The strict aliasing violations this was meant to fix were already fixed in FreeType.
* freetype: fix on mingwVladimír Čunát2016-04-23
|
* Merge recent 'staging' into closure-sizeVladimír Čunát2016-02-03
|\ | | | | | | Let's get rid of those merge conflicts.
| * freetype: 2.5.4 -> 2.6.2Tobias Geerinckx-Rice2016-01-24
| |
* | Merge 'staging' into closure-sizeVladimír Čunát2015-04-18
|\| | | | | | | | | | | | | | | - there were many easy merge conflicts - cc-wrapper needed nontrivial changes Many other problems might've been created by interaction of the branches, but stdenv and a few other packages build fine now.
| * freetype: fix pcf fonts by upstream patchesVladimír Čunát2014-12-17
| | | | | | | | | | | | | | The problem was uncovered by the last security patches. Firefox seems to build and work fine. Includes reverting 374a9cc16271, as this is a proper fix.
| * freetype: feature+security updateVladimír Čunát2014-12-16
| | | | | | | | | | | | | | http://savannah.nongnu.org/bugs/?43661 New version of patches from bohoomil included. Untested on NixOS so far.
* | mutiout: make it builtinVladimír Čunát2014-08-30
| |
* | WIP: getting goodVladimír Čunát2014-08-27
| |
* | Merge 'staging' into multiple-outputsVladimír Čunát2014-08-23
|\| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Conflicts: pkgs/applications/audio/flac/default.nix pkgs/build-support/gcc-wrapper/builder.sh pkgs/development/libraries/apr-util/default.nix pkgs/development/libraries/apr/default.nix pkgs/development/libraries/atk/default.nix pkgs/development/libraries/freetype/default.nix pkgs/development/libraries/gdk-pixbuf/default.nix pkgs/development/libraries/glib/default.nix pkgs/development/libraries/glibc/2.17/builder.sh pkgs/development/libraries/glibc/2.17/locales.nix pkgs/development/libraries/libjpeg/default.nix pkgs/development/libraries/libogg/default.nix pkgs/development/libraries/libsamplerate/default.nix pkgs/development/libraries/libtiff/default.nix pkgs/development/libraries/libvorbis/default.nix pkgs/development/libraries/mesa/default.nix pkgs/development/libraries/pango/default.nix pkgs/development/web/nodejs/default.nix pkgs/os-specific/linux/pam/default.nix pkgs/os-specific/linux/systemd/default.nix pkgs/stdenv/generic/setup.sh pkgs/stdenv/linux/default.nix pkgs/top-level/all-packages.nix pkgs/top-level/release-small.nix
| * freetype: flatten include to fix several buildsVladimír Čunát2014-07-09
| | | | | | | | I just wonder why freetype-2.5 needed to move headers around.
| * freetype: major update, including some CVE securityVladimír Čunát2014-06-17
| | | | | | | | | | - There's no fontconfig update yet, as I failed to debug it yet. - Infinality patches are now taken from a different (maintained) source.
* | Merge remote-tracking branch 'official/master' into multiple-outputsMathijs Kwik2013-09-11
|\| | | | | | | | | | | | | | | | | | | | | Conflicts: pkgs/development/libraries/cairo/default.nix pkgs/development/libraries/freetype/default.nix pkgs/development/libraries/glib/default.nix pkgs/development/libraries/libpng/default.nix pkgs/development/libraries/pango/default.nix pkgs/tools/typesetting/tex/texlive/default.nix pkgs/top-level/all-packages.nix
| * freetype: Update to 2.4.12Eelco Dolstra2013-06-21
| | | | | | | | | | | | | | Also update the Infinality patches. Note that FreeType 2.5 was released a few days ago, but I don't know how stable it is.
* | Merge remote-tracking branch 'origin/master' into multiple-outputsEelco Dolstra2013-06-25
|\| | | | | | | | | | | | | | | | | | | | | | | Conflicts: pkgs/development/libraries/atk/default.nix pkgs/development/libraries/cairo/default.nix pkgs/development/libraries/freetype/default.nix pkgs/development/libraries/glib/default.nix pkgs/development/libraries/gmime/default.nix pkgs/development/libraries/pango/default.nix pkgs/servers/x11/xorg/default.nix pkgs/top-level/all-packages.nix
| * non-Linux platforms: extend to some important pkgsVladimír Čunát2013-06-18
| |
* | Merge remote-tracking branch 'origin/master' into multiple-outputsEelco Dolstra2013-06-09
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Conflicts: pkgs/development/libraries/acl/default.nix pkgs/development/libraries/atk/2.6.x.nix pkgs/development/libraries/attr/default.nix pkgs/development/libraries/cairo/default.nix pkgs/development/libraries/freetype/default.nix pkgs/development/libraries/glib/2.34.x.nix pkgs/development/libraries/gtk+/2.24.x.nix pkgs/development/libraries/libtiff/default.nix pkgs/development/libraries/openssl/default.nix pkgs/development/libraries/pango/1.30.x.nix pkgs/misc/cups/default.nix pkgs/os-specific/linux/util-linux/default.nix pkgs/servers/x11/xorg/builder.sh pkgs/servers/x11/xorg/default.nix pkgs/top-level/all-packages.nix
| * | Revert Merge x-updates into master due to mesa bloatVladimír Čunát2013-05-09
| |/ | | | | | | | | | | | | | | | | | | | | See #490 discussion. This reverts commit 1278859d3167b9f84bfab680d9c8c463adf64a60, reversing changes made to 0c020c98f9d4f49d5c9907db5f4b35aac7df959b. Conflicts: pkgs/desktops/xfce/core/xfce4-session.nix (take master) pkgs/lib/misc.nix (auto)
| * fontconfig: Use /etc/fonts by default againEelco Dolstra2013-05-07
| | | | | | | | | | | | | | | | This removes the need to set $FONTCONFIG_FILE, which is especially important when using Nixpkgs binaries on non-NixOS systems. See also 9301524c500e7e7567d5da54b3f3d7d07e53d921. This is a regression caused by a change in fontconfig's configure switches.
| * Merge branch 'master' into x-updatesVladimír Čunát2013-04-17
| |\ | | | | | | | | | | | | | | | Conflicts: pkgs/development/compilers/vala/default.nix (it's different version) pkgs/development/libraries/cairo/default.nix (trivial)
| | * freetype: attempt to fix build for the other FreeBSDVladimír Čunát2013-04-13
| | |
| * | freetype+fontconfig: add infinality and enable itVladimír Čunát2013-02-10
| | | | | | | | | | | | | | | | | | | | | | | | Also add fontconfig checks , change license to "unfree" if using patented code. Inspired by Corey O'Connor in #89 https://github.com/coreyoconnor/nixpkgs/commit/27fec0aa26d44716134a86efaf48209be7c46138
| * | freetype: minor updateVladimír Čunát2013-01-29
| |/
| * freetype: making it crossbuild fine for mips.Lluís Batlle i Rossell2012-10-20
| | | | | | | | | | | | | | I think at some point the unwrapped build system gcc got into the PATH, and that breaks some cross-builds, because the configure scripts now choose the unwrapped gcc instead of the wrapped. I'll search when it happened and how to overcome this better.
generated by cgit-pink 1.4.1 (git 2.36.1) at 2024-05-03 19:08:24 +0000