I had a simillar problem with a build at my school.The scipt I used wass
the one attached (I find it nixce... except for cvs checkout, anyways it
could be usefull for beginners). I was able to trace it all the way up
to imlib2 (usingimlib2_view).
It's very weird. Some images are fine others are messed up(most of the
enlightenment images actually). And I'm not talking about eet's here.
Just plain png's and jpeg's.
The distribution is a red-hat 9. I was waiting until I could compille a
new gcc before posting this (I don't trust red hat's gcc since
2.96....). And I never had the time to compile a new gcc so this never
got posted. This was also tested with no cflags on unstripped binaries.
Brendon can you test imlib2_view on some of the image form the e17 theme
and tell me of the poblem is the same for you?
till
#/bin/bash
# Script by till varoquaux for an easy test intallation

export WANT_AUTOMAKE=1.7
export WANT_AUTOCONF=2.5

LOCAL_CVS="$HOME/e17_cvs"
INSTALL_LOC="$HOME/e17"

e17_build(){
        mkdir -p $LOCAL_CVS
        cd $LOCAL_CVS
        #now this is very ugly. I haven't found any clean way to do  it
        cvs -d:pserver:[EMAIL PROTECTED]:/cvsroot/enlightenment login 
&>/dev/null< yes
        cvs -z3 -d:pserver:[EMAIL PROTECTED]:/cvsroot/enlightenment co $1  || 
exit 1
        cp -r $LOCAL_CVS/$1 /tmp/$$.e17build
        pushd  /tmp/$$.e17build
        ./autogen.sh --prefix=$INSTALL_LOC || exit 1
        make || exit 1
        make install
        popd
        rm -rf /tmp/$$.e17build
}

e17_strip(){
        cd $INSTALL_LOC
        #removes all the static libraries
        find -name '*.la' -exec rm -f '{}' ';'
        find -name '*.a' -exec rm -f '{}' ';'

        #Strips the newly created binary files
        for i in `find -newer $INSTALL_LOC  -perm +111 -type f`;do 
                echo "$i"
                file $i | grep "ELF" >/dev/null && strip -s $i
        done
        
        EMPHASYS='\033[1;31m'
        NORMAL='\033[0m'        
        echo -n -e $EMPHASYS
        echo "**You may need to add the libraries to your ld search path        
**"
        echo "**If you are not root on your system an easy (though dirty) hack  
**"
        echo "**is to include it in LD_LIBRARY_PATH                             
**"
        echo "**if you are using bash you can add the folowing lines to your    
**"
        echo "**.profile:                                                       
**"
        echo -n -e $NORMAL
        echo "[ -e $INSTALL_LOC/lib ] && export 
LD_LIBRARY_PATH=\"\$LD_LIBRARY_PATH:$INSTALL_LOC/lib\""
        echo -n -e $EMPHASYS
        echo "**If you are root just check ld.so.conf contains:                 
**"
        echo -n -e $NORMAL
        echo "$INSTALL_LOC/lib"
        echo -n -e $EMPHASYS
        echo "**and run ldconfig                                                
**"
        echo -n -e $NORMAL
}

#we use this to know when the build started
mkdir -p $INSTALL_LOC
touch $INSTALL_LOC

OLD_PATH=$PATH
export PATH="$INSTALL_LOC/bin:$PATH"

if [[ $1 != "" ]]
then   
        e17_build $1
        e17_strip
else

build=" e17/libs/imlib2
   e17/libs/edb
   e17/libs/eet
   e17/libs/imlib2_loaders
   e17/libs/evas
   e17/libs/ecore
    e17/libs/epeg
    e17/libs/epsilon
    e17/libs/embryo
     e17/libs/edje
    e17/libs/esmart
    e17/libs/etox
    e17/libs/ewl
   e17/apps/e
   e17/libs/engrave
   e17/apps/e_utils"

cd $HOME

for i in $build
do
        echo $i
        e17_build $i ||exit 1
done
e17_strip

fi

Reply via email to