If you need the latest processors, peripherals and fixes which have not yet been included in the most recent release, you can get the code straight from gpsim's SVN repository on gpsim's SourceForge Page , which is of course hosted by SourceForge.
Although every effort is made by the developers to maintain the SVN code in a usable state, problems may occur with it from time to time. Thus be prepared to either request assistance from the gpsim-devel mailing list. or file a bug report when using the SVN.
$ mkdir gpsim # or whatever directory name you prefer $ cd gpsim $ svn checkout svn://svn.code.sf.net/p/gpsim/code/trunk .Note, 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 repository. Actually, the 'trunk' is where the latest code is stored. The whole repository is a third of a gig!
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
$ automake --force-missing --add-missing
Go get a cup of coffee and read /. as your computer cranks through compiling gpsim. When it's done, you can then install it:
On multi-core processors the compile time can be shortened by running parallel make by using the command "make -j n" where n is 2 * number of cores.
$ su root
# make install
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
# /sbin/ldconfig # refresh the cached library search paths
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:
The 'update' command will compare your local copy with the master SVN copy and then update yours with the differences. It's a whole faster than re-downloading everything.
gpsim's SVN repository
This site is hosted by