matteo/sgpemv2
matteo
/
sgpemv2
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
SGPEMv2 is an educational simulator for process scheduling policies in a monoprocessor computer.
255 Commits 1 Branch 0 Tags 3.3 MiB
C++ 88.5%
M4 4.1%
Python 2.3%
CMake 2.1%
C 1%
Other 2%
Go to file
tchernobog cd9a73ee0e - Move macro for checking for GCC visibility support to a separate file 
- Delete the "serialize()" method of concrete_environment, since useless


git-svn-id: svn://svn.gna.org/svn/sgpemv2/trunk@721 3ecf2c5c-341e-0410-92b4-d18e462d057c
 		2006-07-05 11:11:50 +00:00
config - Fix datarootdir for autoconf 2.60 2006-07-04 20:28:40 +00:00
data - added preferences.dtd: DTD for preferences validation 2006-06-26 06:36:14 +00:00
distro/gentoo - Add src_compile() test-aware 2006-05-31 08:13:22 +00:00
doc essageMinor correcions 2006-03-10 15:08:15 +00:00
m4 - Move macro for checking for GCC visibility support to a separate file 2006-07-05 11:11:50 +00:00
plugins - Another typo, for a change 2006-07-04 23:18:39 +00:00
po - Initial commit laying out skel for new xmlsave plugin. 2006-06-13 15:09:13 +00:00
src - Move macro for checking for GCC visibility support to a separate file 2006-07-05 11:11:50 +00:00
.bzrignore - Remove ChangeLog since it's generated by svn2cl.sh 2006-04-03 08:59:51 +00:00
AUTHORS - Lay out autotools foundations 2005-12-30 19:40:34 +00:00
COPYING - Lay out autotools foundations 2005-12-30 19:40:34 +00:00
Makefile.am - Move macro for checking for GCC visibility support to a separate file 2006-07-05 11:11:50 +00:00
NEWS - Lay out autotools foundations 2005-12-30 19:40:34 +00:00
README - Add some temporary infos about how to perform the 2006-02-19 14:54:53 +00:00
autogen.sh - Add revision left out from last merging (Subversion has one of 2006-04-07 19:57:58 +00:00
configure.ac - Move macro for checking for GCC visibility support to a separate file 2006-07-05 11:11:50 +00:00
gettext.h - Added libtool, gettext support 2006-01-13 15:52:22 +00:00

README 

SGPEMv2 is ... description of product.

Still to be written ... please refer to the 
Info manual in the meantime.

For convenience, here's a short glance at the 
build process (while the manual isn't finished):
in the source package root directory, type:

	mkdir =build && cd =build
	../configure --prefix=/path/to/installation/dir
	make
	su -c "make install"

if you want to generate API documentation via Doxygen:
	
	make apidox

if you want PDFs of the user and developer manuals,

	make pdf

As simple as that.