kimcinoo
/
efl
forked from enlightenment/efl
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
efl/m4/ecore_check_module.m4

36 lines
1.1 KiB
Plaintext
Raw Normal View History

efl: begin (still partial!) to make an uniform choice of engines ecore/evas still lots to do, but some improvements: - ecore_evas does not inherit pkg-config from modules since modules are SO - renamed internal ecore evas define from SOFTWARE_BUFFER to BUFFER, to make consistent. SVN revision: 80473
2012-12-07 09:18:17 -08:00
dnl use: ECORE_EVAS_MODULE(name, want, [DEPENDENCY-CHECK-CODE])
AC_DEFUN([ECORE_EVAS_MODULE],
cosmetic: simplify and colorize features. EFL_ADD_FEATURE(PKG, NAME, [VALUE]) will do an amazing work to produce colored output in a standard way. if value == yes, it's green and shows "+name" if value == no, it's red and shows "-name" else it shows cyan and shows "name=value" if not provided, will use ${have_name:-${want_name}} SVN revision: 82976
2013-01-18 05:48:14 -08:00
[dnl
efl: begin (still partial!) to make an uniform choice of engines ecore/evas still lots to do, but some improvements: - ecore_evas does not inherit pkg-config from modules since modules are SO - renamed internal ecore evas define from SOFTWARE_BUFFER to BUFFER, to make consistent. SVN revision: 80473
2012-12-07 09:18:17 -08:00
m4_pushdef([UP], m4_translit([[$1]], [-a-z], [_A-Z]))dnl
m4_pushdef([DOWN], m4_translit([[$1]], [-A-Z], [_a-z]))dnl
have_ecore_evas_[]m4_defn([DOWN])="no"
want_module="$2"
gl-drm: Fix missing link to gbm for ecore_evas_drm and clean up build script @fix Summary: This fixes following build script problems for ecore_evas_drm engine module. 1. Missing link to gbm for ecore_evas_drm if '--enable-gl-drm' option is given. ecore_evas_drm engine is using gbm function if it builds with that config option. To be more exact, ecore_evas_gl_drm_new_internal function needs gbm. Thus we need to add gbm library linking '-lgbm' to ecore_evas_drm engine module if '--enable-gl-drm' option is given. I've added this build script to m4/ecore_check_module.m4 file. 2. Wrong gbm dependency check code in configure.ac EFL_OPTIONAL_INTERNAL_DEPEND_PKG m4 macro function is designed for checking dependency of efl internal libraries. Thus we should remove gbm pkg name when configuring ecore_evas_drm engine module. It would be better to move dependency check for gbm to m4/ecore_check_module.m4 file. And one more thing want_drm value has to be changed to want_gl_drm in ECORE_EVAS_MODULE([gl-drm]...). 3. BUILD_ECORE_EVAS_OPENGL_DRM macro is always defined in configure.ac. This kind of macro, BUILD_EFL_MODULE_NAME, has to be defined only if given module is enabled. But this macro value was just defined with no test. And it is even useless, we can use BUILD_ECORE_EVAS_GL_DRM macro which is defined by ECORE_EVAS_MODULE([gl-drm], [${want_gl_drm}],...) function. So I've removed that from configure.ac. Test Plan: 1. Configure with --enable-gl-drm: $ ./autogen.sh --enable-drm --enable-gl-drm 2. Build: $ make && make install 3. Check module.so of ecore_evas_drm engine whether it has a library dependency with gbm: $ readelf -a $EFL_GIT/src/modules/ecore_evas/engines/drm/.libs/module.so | grep NEEDED Reviewers: raster, stefan_schmidt, devilhorns Reviewed By: devilhorns Subscribers: cedric Differential Revision: https://phab.enlightenment.org/D1379
2014-08-28 10:36:59 -07:00
ecore_evas_engines_[]m4_defn([DOWN])[]_cflags=""
ecore_evas_engines_[]m4_defn([DOWN])[]_libs=""
fix ecore_evas modules build broken by r82976. Many thanks to billiob that was persistent enough to make me look at it while I was calling it "impossible". That stupid variable was being used in ecore_check_module.m4 :-( SVN revision: 82999
2013-01-18 15:00:57 -08:00
if test "x$want_module" = "xyes" || test "x$want_module" = "xstatic"; then
$3
efl: begin (still partial!) to make an uniform choice of engines ecore/evas still lots to do, but some improvements: - ecore_evas does not inherit pkg-config from modules since modules are SO - renamed internal ecore evas define from SOFTWARE_BUFFER to BUFFER, to make consistent. SVN revision: 80473
2012-12-07 09:18:17 -08:00
fix ecore_evas modules build broken by r82976. Many thanks to billiob that was persistent enough to make me look at it while I was calling it "impossible". That stupid variable was being used in ecore_check_module.m4 :-( SVN revision: 82999
2013-01-18 15:00:57 -08:00
AC_DEFINE([BUILD_ECORE_EVAS_]m4_defn([UP]), [1], [Support for $1 Engine in Ecore_Evas])
have_ecore_evas_[]m4_defn([DOWN])="yes"
gl-drm: Fix missing link to gbm for ecore_evas_drm and clean up build script @fix Summary: This fixes following build script problems for ecore_evas_drm engine module. 1. Missing link to gbm for ecore_evas_drm if '--enable-gl-drm' option is given. ecore_evas_drm engine is using gbm function if it builds with that config option. To be more exact, ecore_evas_gl_drm_new_internal function needs gbm. Thus we need to add gbm library linking '-lgbm' to ecore_evas_drm engine module if '--enable-gl-drm' option is given. I've added this build script to m4/ecore_check_module.m4 file. 2. Wrong gbm dependency check code in configure.ac EFL_OPTIONAL_INTERNAL_DEPEND_PKG m4 macro function is designed for checking dependency of efl internal libraries. Thus we should remove gbm pkg name when configuring ecore_evas_drm engine module. It would be better to move dependency check for gbm to m4/ecore_check_module.m4 file. And one more thing want_drm value has to be changed to want_gl_drm in ECORE_EVAS_MODULE([gl-drm]...). 3. BUILD_ECORE_EVAS_OPENGL_DRM macro is always defined in configure.ac. This kind of macro, BUILD_EFL_MODULE_NAME, has to be defined only if given module is enabled. But this macro value was just defined with no test. And it is even useless, we can use BUILD_ECORE_EVAS_GL_DRM macro which is defined by ECORE_EVAS_MODULE([gl-drm], [${want_gl_drm}],...) function. So I've removed that from configure.ac. Test Plan: 1. Configure with --enable-gl-drm: $ ./autogen.sh --enable-drm --enable-gl-drm 2. Build: $ make && make install 3. Check module.so of ecore_evas_drm engine whether it has a library dependency with gbm: $ readelf -a $EFL_GIT/src/modules/ecore_evas/engines/drm/.libs/module.so | grep NEEDED Reviewers: raster, stefan_schmidt, devilhorns Reviewed By: devilhorns Subscribers: cedric Differential Revision: https://phab.enlightenment.org/D1379
2014-08-28 10:36:59 -07:00
ecore_evas: make it easier to have custom dependencies per module.
2016-04-01 16:17:35 -07:00
case "$1" in
xgl-drm)
PKG_CHECK_MODULES([GBM], [gbm])
ecore_evas_engines_[]m4_defn([DOWN])[]_cflags="${GBM_CFLAGS}"
ecore_evas_engines_[]m4_defn([DOWN])[]_libs="${GBM_LIBS}"
;;
esac
efl: begin (still partial!) to make an uniform choice of engines ecore/evas still lots to do, but some improvements: - ecore_evas does not inherit pkg-config from modules since modules are SO - renamed internal ecore evas define from SOFTWARE_BUFFER to BUFFER, to make consistent. SVN revision: 80473
2012-12-07 09:18:17 -08:00
fi
gl-drm: Fix missing link to gbm for ecore_evas_drm and clean up build script @fix Summary: This fixes following build script problems for ecore_evas_drm engine module. 1. Missing link to gbm for ecore_evas_drm if '--enable-gl-drm' option is given. ecore_evas_drm engine is using gbm function if it builds with that config option. To be more exact, ecore_evas_gl_drm_new_internal function needs gbm. Thus we need to add gbm library linking '-lgbm' to ecore_evas_drm engine module if '--enable-gl-drm' option is given. I've added this build script to m4/ecore_check_module.m4 file. 2. Wrong gbm dependency check code in configure.ac EFL_OPTIONAL_INTERNAL_DEPEND_PKG m4 macro function is designed for checking dependency of efl internal libraries. Thus we should remove gbm pkg name when configuring ecore_evas_drm engine module. It would be better to move dependency check for gbm to m4/ecore_check_module.m4 file. And one more thing want_drm value has to be changed to want_gl_drm in ECORE_EVAS_MODULE([gl-drm]...). 3. BUILD_ECORE_EVAS_OPENGL_DRM macro is always defined in configure.ac. This kind of macro, BUILD_EFL_MODULE_NAME, has to be defined only if given module is enabled. But this macro value was just defined with no test. And it is even useless, we can use BUILD_ECORE_EVAS_GL_DRM macro which is defined by ECORE_EVAS_MODULE([gl-drm], [${want_gl_drm}],...) function. So I've removed that from configure.ac. Test Plan: 1. Configure with --enable-gl-drm: $ ./autogen.sh --enable-drm --enable-gl-drm 2. Build: $ make && make install 3. Check module.so of ecore_evas_drm engine whether it has a library dependency with gbm: $ readelf -a $EFL_GIT/src/modules/ecore_evas/engines/drm/.libs/module.so | grep NEEDED Reviewers: raster, stefan_schmidt, devilhorns Reviewed By: devilhorns Subscribers: cedric Differential Revision: https://phab.enlightenment.org/D1379
2014-08-28 10:36:59 -07:00
AC_SUBST([ecore_evas_engines_]m4_defn([DOWN])[_cflags])
AC_SUBST([ecore_evas_engines_]m4_defn([DOWN])[_libs])
cosmetic: simplify and colorize features. EFL_ADD_FEATURE(PKG, NAME, [VALUE]) will do an amazing work to produce colored output in a standard way. if value == yes, it's green and shows "+name" if value == no, it's red and shows "-name" else it shows cyan and shows "name=value" if not provided, will use ${have_name:-${want_name}} SVN revision: 82976
2013-01-18 05:48:14 -08:00
EFL_ADD_FEATURE([ECORE_EVAS], [$1], [${want_module}])dnl
AM_CONDITIONAL([BUILD_ECORE_EVAS_]UP, [test "x$have_ecore_evas_]m4_defn([DOWN])[" = "xyes"])dnl
m4_popdef([UP])dnl
m4_popdef([DOWN])dnl
efl: begin (still partial!) to make an uniform choice of engines ecore/evas still lots to do, but some improvements: - ecore_evas does not inherit pkg-config from modules since modules are SO - renamed internal ecore evas define from SOFTWARE_BUFFER to BUFFER, to make consistent. SVN revision: 80473
2012-12-07 09:18:17 -08:00
])