Getting Involved: Difference between revisions

Line 22: Line 22:
[http://gitlab.cobra.cs.uni-duesseldorf.de/prob/prob_prolog http://gitlab.cobra.cs.uni-duesseldorf.de/prob/prob_prolog].
[http://gitlab.cobra.cs.uni-duesseldorf.de/prob/prob_prolog http://gitlab.cobra.cs.uni-duesseldorf.de/prob/prob_prolog].


Now, add the following to your <tt>.bash_login</tt> file (at least on Mac OS):
Now, add the following to your <tt>.bash_login</tt> file (at least on Mac OS; supposing you cloned the Git repository into ~/git_root):
 
export PROBDIR=~/git_root/prob_prolog
export PROB_SOURCE_DIR=$PROBDIR/src
  alias prob='cd $PROB_SOURCE_DIR; unlimit; sics -Dprob_profile=true -l $PROB_SOURCE_DIR/prob_tcltk.pl --goal "go."'
  alias prob='cd $PROB_SOURCE_DIR; unlimit; sics -Dprob_profile=true -l $PROB_SOURCE_DIR/prob_tcltk.pl --goal "go."'


Line 30: Line 32:
To start the Unit Test REPL, add the following to your <tt>.bash_login</tt> file (at least on Mac OS):
To start the Unit Test REPL, add the following to your <tt>.bash_login</tt> file (at least on Mac OS):


  alias test='cd $NEWPROBDIR; rlwrap sicstus -Dprob_safe_mode=true -l $NEWPROB_SOURCE_DIR/test_runner.pl --goal "test_repl."'
  alias test='cd $PROBDIR; rlwrap sicstus -Dprob_safe_mode=true -l $PROB_SOURCE_DIR/test_runner.pl --goal "test_repl."'


(It is recommended to install rlwrap so that you get a history of your commands.)
Now you can start the testing console using <tt>test</tt>. You can e.g. type the number of a unit test to run it, or a test category such as <tt>tickets</tt> to run all tests in that category.
Now you can start the testing console using <tt>test</tt>. You can e.g. type the number of a unit test to run it, or a test category such as <tt>tickets</tt> to run all tests in that category.

Revision as of 08:31, 28 May 2014


The ProB Java Core and UI

see the README in our Github Repository


The Prolog Sources

If you want to contribute to the Prolog part of ProB, if you want to extend the ProB API, or need them as reference, you need the Prolog sources which can be downloaded from http://nightly.cobra.cs.uni-duesseldorf.de/source/. To compile the sources you need a SICStus Prolog licence.


Running ProB from Prolog

You first need to download and install SICStus Prolog.

You need the password to download SICStus then run sudo ./InstallSICStus and provide the site name, license code and expiration date.

Probably you should also install a recent Active Tcl distribution.

Now, you need the ProB Prolog sources. If you have access to our Gitlab server then the information is here: http://gitlab.cobra.cs.uni-duesseldorf.de/prob/prob_prolog.

Now, add the following to your .bash_login file (at least on Mac OS; supposing you cloned the Git repository into ~/git_root):

export PROBDIR=~/git_root/prob_prolog
export PROB_SOURCE_DIR=$PROBDIR/src
alias prob='cd $PROB_SOURCE_DIR; unlimit; sics -Dprob_profile=true -l $PROB_SOURCE_DIR/prob_tcltk.pl --goal "go."'

Now, you can simply start ProB from the command-line and from source with prob.

To start the Unit Test REPL, add the following to your .bash_login file (at least on Mac OS):

alias test='cd $PROBDIR; rlwrap sicstus -Dprob_safe_mode=true -l $PROB_SOURCE_DIR/test_runner.pl --goal "test_repl."'

(It is recommended to install rlwrap so that you get a history of your commands.) Now you can start the testing console using test. You can e.g. type the number of a unit test to run it, or a test category such as tickets to run all tests in that category.