Up to now the convenient configure-make-make install cycle is not yet provided for CrusDe. Hence, the installation needs a little more attention. I am working on improving this situation, though. Details are given in the INSTALL file that comes with the code.
The most recent version lives on github:
This allows read access to the repository. Once you installed CrusDe this way use:
in the CrusDe top level directory to update your copy of CrusDe to the latest version from the repository. Then rebuild.
Version | Date | Release Notes / Changelog |
crusde v1.0 | 2015-06-26 |
|
crusde-0_3_0.tar.gz (9.3mb) | 2011-04-26 |
|
crusde-0.2.0.tar.gz (1.7mb) | 2008-08-31 |
|
crusde-0.1.0.tar.gz (24.6mb) | 2007-07-30 | Initial release as described in my thesis (pdf, 5.3mb) |
NOTE: The current version needs a little more attention than the convenient 'configure-make-make install' cycle. This will change as soon as possible. In the meantime I ask you to hang in there and go through the procedures described below. I appreciate your patience!
/usr/local/Trolltech
and add a symbolic link Qt
that points to the installed version of QtIf you compiled the shared versions set the LD_LIBRARY_PATH variable in your profile file and add the paths to the respective PACKAGE/lib directory.
cp crusde-VERSION.tar.gz /usr/local
cd /usr/local
tar xfz crusde-VERSION.tar.gz
export CRUSDE_HOME=/usr/local/CrusDe
cd $CRUSDE_HOME/src
vi Makefile
/usr/local/bin
,
change BIN := [path to where the crusde binary should go]
export QT_DIR := [path to where Qt is installed]
/usr/local/{lib | include}
, add the respective paths to
INCLUDE_DIRS
and LIB_DIRS
using -I[path]
or -L[path]
respectively. Those variables already
point to /usr/local/xerces-c
. Modify this path, if xerces lives in
a different directory.
cd $CRUSDE_HOME/src
make all
Try running:
This should automatically install the standard plug-ins. If it doesn't work, follow the long procedure that was in place before this script:
This step might be a little painful, but also helps to familiarize with the plug-in manager; there's always a good side to everything, right?!
A little window will open, the so called 'CrusDe Plugin Manager', do the following:
Repeat this for all subdirectories in $CRUSDE_HOME/src/plugin_src. Some plugins depend on others and hence a certain order must be followed. Here is a recommendation:
You should be ready to run the testcases in $CRUSDE_HOME/testcases after that.
$> crusde [path to experiment definition]/experiment.xml
Please refer to the documentation for further details.
Additional packages, that are not necessary but certainly nice to have, i.e. recommendations:
| Last modified: March 12 2019 15:19.