Difference between revisions of "The new simulator"

From IridiaWiki
Jump to navigationJump to search
m
m (changed url)
Line 34: Line 34:
   
 
If you don't want to get bored using CVS, you can use the GUI ''Cervisia''. If you want to learn more about
 
If you don't want to get bored using CVS, you can use the GUI ''Cervisia''. If you want to learn more about
CVS commands, branches, tags, releases and so on, you can read this [CVS reference | http://www.wincvs.org/howto/cvsdoc/] for example.
+
CVS commands, branches, tags, releases and so on, you can read this CVS reference for example : http://www.wincvs.org/howto/cvsdoc/
   
 
== Compiling ==
 
== Compiling ==

Revision as of 17:31, 25 March 2005

This page is intended to give some preliminary support for the new simulator of IRIDIA and coordination among developers.

Getting the sources

You can retrieve the files from a CVS repository located on iridia server. Of course you need an account to be able to retrieve the files. People of IRIDIA can easily have an acces by asking to the sysadmin. For anybody else interested, you should write us. First login like this (just replace acampo by your login name)

$cvs -d:pserver:acampo@iridia.ulb.ac.be/home/cvsroot login

Then retrieve files :

$cvs -d:pserver:acampo@iridia.ulb.ac.be/home/cvsroot co newSimulator


Once files are retrieved, cvs has a memory of the location of the repository, so you just have to work inside the same directories and each time you finish a coding session, ar reach a crucial step, do a

$cvs commit

and do also an update before starting to code, so you retrieve on your local copy the modifications brought by anybody else to the files of the cvs. Command for the update :

$cvs update

If you don't want to get bored using CVS, you can use the GUI Cervisia. If you want to learn more about CVS commands, branches, tags, releases and so on, you can read this CVS reference for example : http://www.wincvs.org/howto/cvsdoc/

Compiling

In the tgz, we have ODE, Dyna and OK. First of all, compile ODE. Then you have to copy by hand the files libode.a and includes in the appropriate directories e.g. /usr/local/lib and /usr/local/include/ode.

~ode$ ./configure
~ode$ make
~ode$ su
~ode# mkdir /usr/local/include/ode
~ode# cp include/ode/* /usr/local/include/ode/
~ode# cp lib/libode.a /usr/local/lib/

Once this is done, you can compile ok10. Move to the directory and type make clean. then run ./clean.sh and eventually type make. If you have installed all the dependencies, it should work. Otherwise you can report the problems in the bugs'n problems section :-)

Bugs'n problems

All the reported problems are reported using the syntax : [date of discovery] [date of fixing] [author] : name Followed optionnally by a short description.

Open ones

[2005-03-21] [] [Alex] : I have ODE on my computer, but it won't work with the simulator. I had to compile the provided version of ODE. Did David make any modification to the ODE lib ? If yes we need to discuss about it. I should not be forced to install a modified lib, since it could contain bugs or be different from the original one and disturb the behaviour of other programs.

Closed ones

TODO

I suggest we use the same syntax as above : [date of discovery] [date of fixing] [author] : name Followed optionnally by a short description.

Open ones

[2005-03-21] [] [Alex] : INSTALL file to write

[2005-03-21] [] [Alex] : configure script to provide

[2005-03-21] [] [Alex] : problem with libxml headers ? In debian libxml2 headers are located in /usr/include/libxml2/libxml

[2005-03-21] [] [Alex] : REMOVE FMOD.

Closed ones