Carsten Haitzler (The Rasterman) wrote:
> On Thu, 28 Feb 2008 10:14:19 +0100 (CET) [EMAIL PROTECTED] babbled:
>> Then I agree. But --prefix should then be taken literally, so that using
>> --prefix=/mydir makes the module end up in /mydir/MODULENAME.
> 
> this would violate the principle of least surprise. --prefix should do what it
> does every else in autofoo - people should be able to use
> 
> ./configure --prefix=/opt/blah/e
> make
> make install
> 
> for everything in efl - for that matter, every piece of software that uses
> autofoo, and it should do the right thing and just work - install in the right
> place.
> 

But this case is solved by using
E_CONFIG='/opt/blah/e/bin/e-config' ./configure

What we now try to solve is when a user adds /my/module/dir to the 
module search path. We could use

./configure --with-module-dir=/my/module/dir

Then we ignore all standard options :)

Sebastian

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Reply via email to