On Sat, 3 Oct 2009, Carsten Haitzler (The Rasterman) wrote:
> On Sat, 3 Oct 2009 10:21:18 +0200 (CEST) Vincent Torri <[email protected]> > said: > >> >> >> On Sat, 3 Oct 2009, Stephan Raue wrote: >> >>> Am 01.10.2009 14:36, schrieb Carsten Haitzler (The Rasterman): >>>> works for me. provide some backtraces and info as to why it segv's. it >>>> works on embedded systems (openembedde distros like angstrom, and >>>> build-yourself ones, etc.). mind you - i don't bother with uclibc. it's >>>> too much pain and just not worth the reduced features and support compared >>>> to glibc. you might want to save yourself pain and just use glibc. ) >>>> >>> Hi Carsten, >>> >>> my problem was wrong dirnames for the modules of evas, because i dont >>> install libs with make install in the target. So evas cannot find the >>> modules and elementary produces this segfault. >>> >>> my questions: >>> - is this possible to log it if evas cant found a module >> >> it is possible, and actually, it must be added. > > no. it's up to the caller to handle an engine find fail. in this case the > caller wasnt handling it. changes ae not even the minimum default set of > loaders was there. if make install wasnt being used and whatever was done to > replace it was done badly6 - then it's far from being out problem in code to > fix :) it's always good to have logging, it helps knowing what the problem is. It does not prevent the user doing what is needed if the engine is not found,of course. >>> - why evas will install and search modules in e.g. >>> /usr/lib/evas/modules/engines/gl_x11/linux-uclibc-i686-ver-pre-svn-04/module.so >>> and not e.g. /usr/lib/evas/modules/engines/gl_x11/module.so - how can i >>> change this? >> >> You can't change that by just configuring evas with one way or another. >> It's the way evas modules must be installed (except on Windows CE for odd >> reasons) >> >> But you can change configure.ac so that MODULE_ARCH is set to "". It >> should work the way you want. > > i highly suggest not doing that. sure. He wants a solution, there is one. Not a good one, but there is. It seems that he has some specific needs. > that module arch dir is here for a very good > reason. lave it. evas's code expects it, uses it and modules install in it. > correctly if you use the make install rules. it's there for very good reasons. > > -- > ------------- Codito, ergo sum - "I code, therefore I am" -------------- > The Rasterman (Carsten Haitzler) [email protected] > > ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
