[CHANGE] Allow relative paths (project or data-file) as parameter for kdbg and gdb script

tools/debugging/bin/openwalnut-gdb

@@ -4,23 +4,22 @@ PARAM_FILENAME="/tmp/walnut-gdb.script."$(date +%s)
 echo $PARAM_FILENAME
 echo run $@ > $PARAM_FILENAME
 
-# assume that this script is in the bin dir
-# go there to ensure walnuts working directory is set correctly
-cd "$BINDIR"
-
 # get path of this script
 BINDIR=`dirname "$0"`
-cd "$BINDIR/.."
+# strip "bin" to get base directory
+BASEDIR=`dirname "$BINDIR"`
+LIBDIR=$BASEDIR/lib
 
 # We want to avoid that multiple system installations of OpenWalnut cause some weird loading of libs. We want ours (relative to our executable) to be loaded:
 Libs="libopenwalnut_biosig.so.1 libopenwalnut_eep.so.1 libopenwalnut_niftiio.so.1 libopenwalnut_niftiznz.so.1"
 # Well, this one needs to be there! If not, your installation is wrong.
-Preloads="lib/libopenwalnut.so.1"
+Preloads="$LIBDIR/libopenwalnut.so.1"
 # We need to ensure the libs are there. If not, do not add them to the preloads variable
 for lib in $Libs
 do
-    if [ -e "lib/$lib" ]; then
-        Preloads=$Preloads:lib/$lib
+    libfile=$LIBDIR/$lib
+    if [ -e "$libfile" ]; then
+        Preloads=$Preloads:$libfile
     fi
 done
 # Finally, export it
@@ -30,7 +29,7 @@ export LD_PRELOAD=$Preloads
 export LC_ALL=C
 
 # run walnut
-gdb bin/openwalnut-qt4 -command=$PARAM_FILENAME
+gdb $BINDIR/openwalnut-qt4 -command=$PARAM_FILENAME
 
 rm $PARAM_FILENAME
-cd $PWD
+

tools/debugging/bin/openwalnut-kdbg

 #!/bin/sh
 
-
 # get path of this script
 BINDIR=`dirname "$0"`
-cd "$BINDIR/.."
+# strip "bin" to get base directory
+BASEDIR=`dirname "$BINDIR"`
+LIBDIR=$BASEDIR/lib
 
-# We want to avoid that multiple system installations of OpenWalnut cause some weird loading of libs. We want ours (relative to our executable) to be loaded:  
-Libs="libopenwalnut_biosig.so.1 libopenwalnut_eep.so.1 libopenwalnut_niftiio.so.1 libopenwalnut_niftiznz.so.1"                                                 
+# We want to avoid that multiple system installations of OpenWalnut cause some weird loading of libs. We want ours (relative to our executable) to be loaded:
+Libs="libopenwalnut_biosig.so.1 libopenwalnut_eep.so.1 libopenwalnut_niftiio.so.1 libopenwalnut_niftiznz.so.1"
 # Well, this one needs to be there! If not, your installation is wrong.
-Preloads="lib/libopenwalnut.so.1"
-# We need to ensure the libs are there. If not, do not add them to the preloads variable                                                                       
+Preloads="$LIBDIR/libopenwalnut.so.1"
+# We need to ensure the libs are there. If not, do not add them to the preloads variable                            
 for lib in $Libs
 do
-    if [ -e "lib/$lib" ]; then
-        Preloads=$Preloads:lib/$lib
+    libfile=$LIBDIR/$lib
+    if [ -e "$libfile" ]; then
+        Preloads=$Preloads:$libfile
     fi
 done
 # Finally, export it
 export LD_PRELOAD=$Preloads
 
-# Force C locale. This fixes an issue with newer boost versions. See ticket #130.                                                                              
+# Force C locale. This fixes an issue with newer boost versions. See ticket #130.
 export LC_ALL=C
 
-
 PARAMS="$*"
 echo "Parameters: $PARAMS"
 
 # run walnut
-kdbg -a "$PARAMS" bin/openwalnut-qt4
-
+kdbg -a "$PARAMS" $BINDIR/openwalnut-qt4