From: Gustavo S. B. <bar...@pr...> - 2013-01-11 03:26:39
|
On Thu, Jan 10, 2013 at 8:51 PM, Nicolas Aguirre <agu...@gm...>wrote: > Hi, > > After lucas commit, i tried to build EFL merge for win32. > > i configure with : ./configure --prefix=$MINGW_PREFIX --host=$TARGET > --disable-static --with-tests=none --with-crypto=gnutls --disable-gstreamer > --disable-pulseaudio --disable-audio --disable-physics > > --disable-gstreamer option does't work at all, it's ignored, attached a > patch which fix this issue. > Thanks, in SVN. The next issue is that the configure try to check for eeze, but eeze is a > linux only package, it's a non sense for windows or macos. So how to remove > eeze from the build ? > It could be a good option to add a --disable-eeze option in the configure ? > what you think about it ? > Likely due the cross compilation. Right now it reads: EFL_LIB_START_OPTIONAL([Eeze], [test "${have_linux}" = "yes"]) Based on: case "$host_os" in mingw32ce*) have_wince="yes" have_windows="yes" ;; mingw*|cygwin*) # TODO: check cygwin* here have_win32="yes" have_windows="yes" ;; darwin*) have_darwin="yes" ;; linux*) have_linux="yes" ;; esac I thought that even being "host_os", the mingw* would redefine it... but I was wrong. Do you have the information about that? If you're getting linux = yes, then all your modules cross compiled for Windows are named linux?! :-/ Later on we have: MODULE_ARCH="$host_os-$host_cpu-v_maj.v_min.v_mic" MODULE_EXT=".dll" that was the reasoning of my thought. There will be no --disable-eeze. -- Gustavo Sverzut Barbieri http://profusion.mobi embedded systems -------------------------------------- MSN: bar...@gm... Skype: gsbarbieri Mobile: +55 (19) 9225-2202 |