remove the option and logic, but still leave the framework in there if
some day a rare case of engine that does not rely on software generic
shows.
SVN revision: 80464
platform_pc defines requirements for every platform, each can be
addressed individually by platform_pc_evil, platform_pc_escape or
platform_pc_exotic.
SVN revision: 80454
instead of replicating common patterns all around, let's use the
common patterns as m4 macros.
EFL_DEPEND_PKG() will use pkg-config and add the dependency.
EFL_OPTIONAL_DEPEND_PKG() will use the former, but also defines
have_XYZ and does the if statement for you.
SVN revision: 80402
Instead of distributing system/platform features all around, many are
shared among modules, summarize these things into one single line
using +/- notation.
SVN revision: 80394
* a single option --with-evas-dither-mask=TYPE (big, small, line or none).
* make a wise decision to fallback to small dither mask for
conversions that do not support "no-dither" or "line". Before if
you did not specify it would fallback to big (128x128).
SVN revision: 80383
instead of the previous mess, just define the functions with common
names and call the backend that was compiled in, similar to what eio
does.
also do not be silent on errors, use eina_safety_checks to issue warnings.
SVN revision: 80360
Another try to make inotify checks more common.
This time uses AC_CHECK_HEADERS() as for others, that already define
HAVE_SYS_INOTIFY_H, then uses that.
I still kept AM_CONDITIONAL([HAVE_INOTIFY]) because I plan to convert
ecore_file to the same, smarter, method that is used in eio (compiling
the file depending on the backend.
SVN revision: 80358
* remove the option, as it shouldn't really exist.
* keep code, as requested by Cedric, someone may fix it someday. And
the default is the DISABLED, as the enable was broken.
* Add instructions on how to solve the problem, if a brave folk is up
to it.
SVN revision: 80352
* rename USE_GNUTLS and USE_OPENSSL to HAVE_GNUTLS and HAVE_OPENSSL
in ecore_con, to match other modules such as Eet.
* define requirements_pc_crypto, requirements_pc_deps_crypto and
requirements_libs_crypto so modules can use that.
* move to a common check section.
SVN revision: 80288
* remove EVAS_ prefix as it may be used by other libs some day.
* SSE3 is detected at runtime if x86.
* remove AC_SUBST([altivec_cflags]) as it was not being used anywhere.
* moved to top of file (maybe position is not optimal, let's wait
vtorri to review)
* simplified single-line summary that is as informative as before.
SVN revision: 80284
Actually, this variable wasn't being set on any other backend, so I just
removed it from wayland-egl. I guess it was just a copy & paste typo
when merging ecore into the EFL tree.
SVN revision: 80266
"pkg-config --exists <none>" will return false, thus failing the
configure phase. Not sure if building ecore-con without curl makes sense
though.
SVN revision: 80265
vtorri: I told you these names are very very error prone. I did the
mistake while reading it before, raster did the same today and even
yourself did a typo. The "pc", "libs" and similar in the middle of a
long variable name is easy to miss! Even more if the prefix is
"requirements_" :-(
SVN revision: 80234
After agreement in the mail list, core developers agree to remove this
engine that was not being supported for a long time.
Given that most operations Evas uses are not accelerated in DirectFB,
or at least hardware that exclusively supports DirectFB, it's better
for those people to just use Evas/Ecore software (buffer) rendering
and expose DirectFB's framebuffer as destination surface.
SVN revision: 80232