path: root/legacy
diff options
authorCarsten Haitzler <>2012-08-16 00:53:31 +0000
committerCarsten Haitzler <>2012-08-16 00:53:31 +0000
commitd91c5bc76f4bb8031753f625179a551a9d423e9b (patch)
tree8bafa864c544e28b8d6333ad80e0db76c9d27006 /legacy
parentc27e15df0b7c0eb5c74c2d4fa90a01afff2ec1ad (diff)
update README
SVN revision: 75299
Diffstat (limited to 'legacy')
1 files changed, 30 insertions, 64 deletions
diff --git a/legacy/evas/README b/legacy/evas/README
index d582c9d7e5..ddfcda0084 100644
--- a/legacy/evas/README
+++ b/legacy/evas/README
@@ -552,6 +552,35 @@ this loader load tga format files. these files are very old-fashioned
552but found often in the 3d graphics world. 552but found often in the 3d graphics world.
553 553
554 554
557this loader will execute a given binary to decode an image and read
558the resulting image data via a shared memory segment, a mmaped file or
559stdout. it uses the command-line to pass the filename and any load
560parameters, and reads stdout from the loader binary to get metadata like
561width, height, alpha channel flag and location of pixel data. this
562loader has no dependencies as the binaries run are to be found in
563PREIFX/lib/evas/utils and are named evas_image_loader.EXTENSION where
564.EXTENSION is replaced by the filename extension to be decoded. if
565this binary does not exist then evas_image_loader (with no extension) is
566tried as a last fallback allowing it to handle "all cases".
568since this loader doesn't use any libraires, it relies on runtime
569dependencies and executables existing in the utils directory. note that
570images loaded via this mechanism will have slower load times due to the
571overhead of execution of another binary, but any instability in the
572loaders themselves will not affect the application using evas.
574this also means that licenses such as GPL for the binaries in this
575utils directory do not affect evas and the applications or libraries
576using evas.
578there is a separately released evas_generic_loaders package which
579builds stand-alone binaries that can do this style of decoding for for
580evas. this package currently handles XCF, PDF, PS, RAW, SVG (via
581librsvg) and video formats (via gstreamer).
555------------------------------------------------------------------------------ 584------------------------------------------------------------------------------
557--enable-font-loader-eet[=static] 586--enable-font-loader-eet[=static]
@@ -759,76 +788,13 @@ with --enable-pthreads and --enable-async-events. you really want all
759of these available. 788of these available.
760 789
761 790
762--enable-async-render **CAUTION - MAY NOT WORK RIGHT** 791--enable-pipe-render **NOT ON BY DEFAULT DUE TO DUBIOUS IMPROVEMENTS**
764this enables a software multi-frame threaded renderer. this will
765allocate (for example) 2 frames to 2 cores, with one core of the cpu
766rendering the previous frame while the next frame starts rendering on
767another core in the meantime allowing for higher framerates with
768software rendering, using more cpu resources that are available on
769modern multi-core cpu's.
771This is buggy! it will likely cause crashes and rendering corruption.
772Do not enable it unless you plan to actually work on it. This requires you
773also set the environment variable EVAS_RENDER_MODE to "non-blocking" to
774enable it at runtime, as the compile-time enable simply sets up the feature
775to be ready to work. The runtime switch actually turns it on. If you don't
776plan to use this feature, don't enable it in the build as there is a general
777performance hit of maintaining this feature at all, so beware that
778enabling it for single core systems will likely take a performance hit.
781--enable-pipe-render **DISABLED DUE TO BUGS**
782 792
783this enables a multiple-thread renderer that divides the rendering 793this enables a multiple-thread renderer that divides the rendering
784into N regions (1 per core) to speed up rendering in software when you 794into N regions (1 per core) to speed up rendering in software when you
785have multiple cpu cores. 795have multiple cpu cores.
786 796
787 797
788--enable-word-cache **DISABLED DUE TO BUGS**
790Cache rendered words and draw them as a single object, instead of
791individual characters. This is a big gain for things like neon which
792draw large runs effectively.
794However it is useless on GL and similar back-ends as the cost in
795sending a word sized texture kills the performance gain (and GL is
796pretty good at drawing lots of small things anyway). If it detects a GL
797backend is in use, it disables itself.
799By default words (strings) of more then 50 characters are not cached.
800The system caches 40 words by default, but this can be changed by
801setting EVAS_WORD_CACHE_MAX_WORDS to another number. Setting it to 0
802will disable word-cache at run time.
804Text based benchmarks are 50-100% quicker.
806If you have any issues with word caching, please report them to either
807the e-devel mailing list or Brett Nash <>
809For GL see metric caching...
812--enable-metric-cache **DISABLED DUE TO BUGS**
814Metric caching saves character metrics between characters in words.
815This enables it to render words much quicker as it avoids things like
816space calculations and kerning calculation.
818The cache size is also controlled by EVAS_WORD_CACHE_MAX_WORDS.
820It is useful for GL in particular, although software engines do get
821some gain.
823Generally it is recommended you enable one or both of word or metric caching,
824depending on your engine use. If you are only using software, enable word
825caching (and neon on arm if you can), for GL, turn on metric caching.
826A simple solution is enable both, and let the engine sort it out at run time.
828If you have any issues with metric caching, please report them to either
829the e-devel mailing list or Brett Nash <>
832--enable-fontconfig 798--enable-fontconfig
833 799
834this enables fontconfig support for loading font files by using 800this enables fontconfig support for loading font files by using