This site is hosted by
If you need to be on the bleeding edge, you can get the code straight from gpsim's SVN repository on gpsim's SourceForge Page , which is of course hosted by SourceForge. But BE WARNED, the SVN is development code and may be unstable!
$ mkdir gpsim # or whatever directory name you preferNote, don't forget the '.' at the end of the last command! If you did, then the code will get placed into a directory named gpsim/trunk. Also, note that svn is chunky around the edges; you'll need about 45M of disc space to get a copy of the reposistory. Actually, the 'trunk' is where thelatest code is stored. The whole repository is a third of a gig!
$ cd gpsim
$ svn checkout https://gpsim.svn.sourceforge.net/svnroot/gpsim/trunk .
When you get the code from SVN this first time, you'll have to go through a couple of extra steps to build it. But those steps are really simple. In the directory you downloaded gpsim from SVN, enter these commands:
$ libtoolize --force
$ aclocal
$ autoheader
$ automake --force-missing --add-missing
$ autoconf
$ ./configure
$ make
Go get a cup of coffee and read /. as your computer cranks through compiling gpsim. When it's done, you can then install it:
$ su root
# make install
# exit
And you should be ready to go!
The instructions given above are suitable for building gpsim. However, it's possible to embed gpsim into a custom simulation environment (see KTechLab). These simulation environments may have special requirements for building or configuring gpsim. For example, if shared libraries required:
[gpsim] $ ./configure --enable-shared
Or if the socket interface is required:
[gpsim] $ ./configure --enable-sockets
The main gpsim source contains several simple library modules. When you build and install gpsim these are installed too. These modules are placed into a shared library (or DLL under windows). Thus gpsim will use your OS' library loading mechanism to find them. A common mistake here is that the modules get installed into a directory for which the OS has no path. On Linux, the modules are installed by default into /usr/local/lib/. If you choose to keep this default location (there's nothing wrong with that), you'll need to add a path to it. This is done by placing adding the path to the file /etc/ld.so.conf
$ su # become root
# edit /etc/ld.so.conf by adding the line /usr/local/lib to it
# cat /etc/ld.so.conf
include ld.so.conf.d/*.conf
/usr/X11R6/lib
/usr/X11R6/lib64
/usr/lib/mysql
/usr/lib64/mysql
/usr/local/lib
# /sbin/ldconfig # refresh the cached library search paths
# exit
If one of the developers makes a change to SVN and you just want to update your local copy, then all you need to do is this:
svn update
The 'update' command will compare your local copy with the master SVN copy and then update your's with the differences. It's a whole faster than re-downloading everything.
|
This site is hosted by |
|
|