* Split out ecore_imf_xim to do its own check
* Fixed problem with xcb's makekeys, no rule for
$(top_builddir)/src/utils/ecore/makekeys$(EXEEXT) exists so make
used an implicit rule (ignoring any cflags of course)
* Fixed gl_x11 engine to build with either Xlib or XCB (xcb flags were
missing)
* Added EFL_FIND_X and replace any used of AC_PATH_X{,TRA}. First
looks for Xorg pkg-config files then if those arn't found it falls
back to old AC_PATH_X. Also generalized common header and lib
checks. Could probably use some polishing (the AC_CACHE_VAL cruft
especially) but this is what I have time for tonight.
Now X11 should be found on non-standard locations by means of xmkmf,
--x-includes/--x-libraries and also pkg-config.
SVN revision: 82475
Weirdly enough raster turned PROGRAM cache on to fix a bug saying that
the other path was not tested, but from IN-EFL/edje/configure.ac CALC
cache was enabled and PROGRAM was disabled.
I kept the PROGRAM on and enabled CALC. Added fixed point as well.
Cedric, Raster: should we keep PROGRAM and CALC cache options if the
other path is not tested? Can't we assume they are always on? How much
memory these cache add? Can't this be reduced?
SVN revision: 82410
Tests are disabled by default, but they should be mandatory for
distcheck. So should be examples, we should have them to at least
compile.
As there is no way to force "make distcheck" to run "make examples",
I've created --enable-always-build-examples to make examples regular
noinst_PROGRAMS, being always compiled. distcheck will use that
option.
SVN revision: 82276
this is still in progress, mostly the multisense stuff is pending.
it seems that when we merge ecore_audio in edje the libremix and
similar are gone, at least from Edje, and will be in ecore_audio
itself (or pulseaudio).
Changes:
* __UNUSED__ to EINA_UNUSED
* binaries (epp, embryo_cc, edje_cc) now consider EFL_RUN_IN_TREE and
will assume the binaries are still not installed, running from
build tree location (needs more testing, maybe doesn't work with
srcdir != builddir, still doesn't solve cross compile builds)
SVN revision: 82139
Changes also in this commit:
* fix missing EAPI in symbols used by modules
* removed old libudev and libmount support as agreed by discomfitor/zmike
* replaced __UNUSED__ with EINA_UNUSED
* fixed docs hierarchy
SVN revision: 82100
va_list may be typedef'ed not only to array and pointer but also to a
plain struct. It could be made to work this way, but it's a lot simpler
a safer to not depend on it. To deal with the array corner case we copy
the va_list from the function arguments to the stack and call the "real"
function passing it.
SVN revision: 82017
As reported by Doug Newgard it was causing problems and seems this is
the reason. No idea why it works for me in the same
distro/autoconf/automake.
SVN revision: 81959
- fchmod() was isolated by HAVE_CHMOD, which was always present
before... then fchmod() is also present as no errors were reported
since its introduction.
- fchmod() is POSIX for a while now.
- lstat() is POSIX for a while now.
- setxattr is supported by EFL_CHECK_FUNCS() as is used by eina.
- splice() check added to EFL_CHECK_FUNCS()
SVN revision: 81938
some functions were being checked but their IFDEF not being handled,
others (getpwnam and getgrnam) were isolated in a code that is now
Windows, then no need to check them as well as these are POSIX.
SVN revision: 81934
okay, remove that print as it will always print sections removed from
PIC leftovers, etc.
keep the --gc-sections, it's useful to shrink binaries. Developers
willing to delete dead code can --print-gc-sections themselves.
SVN revision: 81920
seems that automake will parse LDFLAGS for -module and if it's not
present it will complain about name not starting with 'lib'.
seems my last try was without NOCONFIGURE=1 and autogen continued to
the old ./configure, that printed lots of messages and the error went
unnoticed
SVN revision: 81917
- remove EFL_LIBS and EFL_CFLAGS, use per-lib values that inherit
from EFL (general)
- add NAME_LDFLAGS and EFL_LDFLAGS for linker flags.
- LDADD (binaries) now use NAME_LDFLAGS instead of NAME_LIBS, as they
link to libname.la and that will pull in the libtool dependencies
SVN revision: 81915
* -fvisibility=hidden will hide symbols not marked with EAPI in the
final binary (so/executable).
* -ffunction-sections and -fdata-sections will split those into
independent elf sections, then we can -Wl,--gc-sections for those
that are unused. During development --Wl,--print-gc-sections will
warn us of functions that are left unused and were collected.
SVN revision: 81906
note: dns.c were already emitting warnings regarding shadow, so I
removed the flag to quiet override-init. It will a bit louder, but
then we remember it would be better to rewrite this dns in proper EFL.
SVN revision: 81905
added couple of macros:
- EFL_LIB_START(PKG): setup variables and replacements (AC_SUBST),
prints started checks
- EFL_LIB_END(PKG): prints ended checks
- EFL_LIB_START_OPTIONAL(PKG, TEST): wraps EFL_LIB_START() with a
conditional test. defines AC_DEFINE(HAVE_PKG).
- EFL_LIB_END_OPTIONAL(PKG): wraps EFL_LIB_END() with a conditional
test, defines AM_CONDITIONAL(HAVE_PKG).
SVN revision: 81903
in some cases libtool would build 2 versions, pic for shared and
no-pic for static. Make sure we just build one as pic is good enough.
NOTE: this is only used on supported platforms.
SVN revision: 81902
weird enough to build with memcheck.h you just need valgrind's CFLAGS,
not its libraries as they are not supposed to be used like that,
throwing many bgPlain_ errors (vgPlain_tl_pre_clo_init,
vgPlain_free...) from libcoregrind-x86-linux.a
SVN revision: 81901
From Autobook: http://www.sourceware.org/autobook/autobook/autobook_85.html
libtool will build executables suitable for copying into their
respective installation destinations, obviating the need for
relinking them on those hosts which would have required
it. Whenever libtool links an executable which uses shared
libraries, it also creates a wrapper script which ensures that the
environment is correct for loading the correct libraries, See
section 10.5 Executing Uninstalled Binaries. On those hosts which
require it, the wrapper script will also relink the executable in
the build tree if you attempt to run it from there before
installation.
Sometimes this behaviour is not what you want, particularly if you
are developing the package and not installing between test
compilations. By passing `--disable-fast-install', the default
behaviour is reversed; executables will be built so that they can
be run from the build tree without relinking, but during
installation they may be relinked.
The user may still override this default, depending on platform
support, by specifying --enable-fast-install to configure.
NOTE: In my measurements it made no difference in install time either.
SVN revision: 81900
Most systems will never ever need the static builds of EFL, and it
doubles the compilation time (4m36s x 2m48s on my laptop). Then
disable it by default.
The user may still override this default by specifying --enable-static
to configure.
SVN revision: 81898
Gustavo Sverzut Barbieri
Carsten Haitzler
Jihoon Kim
Mike Blumenkrantz
Leandro Dorileo
Sebastian Dransfeld
Lucas De Marchi