On Sat, 3 Oct 2009 13:19:57 +0200 (CEST) Vincent Torri <[email protected]> said:
> > 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. well u could log every malloc fail, or every time open() fails to find a file... but it'd be bad style as you'd make a noisy app that the app author cannot control. asking for an engine and getting a failed return is how you detect if the engine is supported or not. making it printf on this is a bad idea. > >>> - 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. he doesn't need a solution. beyond having simply written bad install scripts of his own which makes it his own bug/problem. :) i don't see a good reason to not use the make install. it's used in packaging for multiple distros - it can install anywhere you like.. using DESTDIR is a standard way to do this. i don't see a very good reason to do your own manual install scripts. :) -- ------------- 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
