configure --enable-fsstd --prefix=/opt and configure --enable-fsstd (i.e. --prefix=/usr/local)
which are both fsstd?
What I suggest is to make --enable-fsstd implied so that the configuration wrt. install dirs is the same as in every other
package in the universe.
To get the old (intended) default behavior one would have to do something like:
configure --bindir=/usr/local/enlightenment/bin --datadir=/usr/local
/Kim
Mark R. Bowyer wrote:
On Sun, 2003-07-13 at 22:25, Kim Woelders wrote:
Morten Nilsen wrote:
if configure is run without parameters, prefix is set to /usr/local enlightenment expects it's binaries to be in prefix/enlightenment/bin, while they get installed in prefix/bin
giving configure --enable-fsstd, this works..
If I use --prefix, it doesn't work unless I give --enable-fsstd. without having extensively tested this, I conclude that e requires --with-fsstd to work at all...
cheers,
I am aware of this problem.
Does anybody actually use the non-fsstd stuff, i.e. install to /usr/enlightenment/{bin,themes,...}?
I do, and mentioned this when I did my Solaris compile. /usr/local is shared off our team server in the lab here. /opt is local to each machine. Once 0.16.6 is final, I'll be compiling on Solaris 8 and installing in /usr/local for everyone to be able to use it (although those that have moved to Gnome2 already here seem to be making do with metacity =O( ). Before then, I'm compiling on Solaris 10 and installing in my local /opt. If --enable-fsstd lets me do that correctly without having to clean up afterwards, that's nice, but having it just work like everything else would be way nicer... =O}
------------------------------------------------------- This SF.Net email sponsored by: Parasoft Error proof Web apps, automate testing & more. Download & eval WebKing and get a free book. www.parasoft.com/bulletproofapps1 _______________________________________________ enlightenment-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
