|
Name |
|
Date |
Size |
#Lines |
LOC |
| .. | | 03-May-2022 | - |
| doc/ | H | 03-May-2022 | - | 22,388 | 19,377 |
| examples/ | H | 03-Jun-2020 | - | 34,878 | 30,917 |
| m4/ | H | 03-Jun-2020 | - | 9,252 | 8,371 |
| mod/ | H | 03-Jun-2020 | - | 10,938 | 6,314 |
| sim/ | H | 03-May-2022 | - | 26,306 | 14,289 |
| xmcsim/ | H | 03-Jun-2020 | - | 2,425 | 1,626 |
| AUTHORS | H A D | 13-Mar-2013 | 73 | 10 | 7 |
| COPYING | H A D | 27-Apr-2010 | 34.3 KiB | 675 | 553 |
| INSTALL | H A D | 15-Feb-2019 | 9.2 KiB | 235 | 177 |
| Makefile.am | H A D | 25-Mar-2018 | 281 | 15 | 9 |
| Makefile.in | H A D | 03-Jun-2020 | 39.9 KiB | 1,230 | 1,096 |
| README | H A D | 05-Dec-2015 | 1.6 KiB | 35 | 26 |
| aclocal.m4 | H A D | 03-Jun-2020 | 43.3 KiB | 1,219 | 1,109 |
| ar-lib | H A D | 03-Jun-2020 | 5.7 KiB | 271 | 210 |
| compile | H A D | 03-Jun-2020 | 7.2 KiB | 348 | 258 |
| config.guess | H A D | 03-Jun-2020 | 43.2 KiB | 1,481 | 1,288 |
| config.h | H A D | 03-Jun-2020 | 3.7 KiB | 133 | 38 |
| config.h.in | H A D | 03-Jun-2020 | 3.4 KiB | 132 | 89 |
| config.sub | H A D | 03-Jun-2020 | 35.3 KiB | 1,802 | 1,661 |
| configure | H A D | 03-Jun-2020 | 494.4 KiB | 17,041 | 14,413 |
| configure.ac | H A D | 03-Jun-2020 | 2.3 KiB | 80 | 66 |
| depcomp | H A D | 03-Jun-2020 | 23 KiB | 792 | 502 |
| install-sh | H A D | 03-Jun-2020 | 14.8 KiB | 509 | 329 |
| ltmain.sh | H A D | 03-Jun-2020 | 316.8 KiB | 11,157 | 7,986 |
| missing | H A D | 03-Jun-2020 | 6.7 KiB | 216 | 143 |
| test-driver | H A D | 03-Jun-2020 | 4.5 KiB | 149 | 87 |
README
1README FILE: INSTRUCTIONS FOR INSTALLING GNU MCSIM
2Contact: Frederic Yves BOIS
3 fbois@member.fsf.org
4
5The simplest way to compile the MCSim package is:
6
7 1. `cd' to the directory containing the package's source code (it is
8 actually the directory where this README file resides) and type
9 `./configure' to configure the package for your system. If you're
10 using `csh' on an old version of System V, you might need to type
11 `sh ./configure' instead to prevent `csh' from trying to execute
12 `configure' itself.
13
14 Running `configure' may take a while. While running, it prints some
15 messages telling which features it is checking for.
16
17 2. Type `make' to compile the package.
18
19 3. Optionally, type `make check' to run any self-tests that come with
20 the package. In some systems the Makefile that runs the tests in
21 the example/perc/ folder needs to be flagged as executable explictly
22 before running the test, otherwise the test fails. To make it executable
23 simply execute "chmod a+x examples/perc/Makefile" from the command line.
24
25 4. Type `make install' to install the programs and any data files and
26 documentation.
27
28 5. You can remove the program binaries and object files from the
29 source code directory by typing `make real-clean'. To also remove the
30 files that `configure' created (so you can compile the package for
31 a different kind of computer), type `make dist-clean'. There is
32 also a `make maintainer-clean' target which undoes the installation.
33
34For detailed installation instructions see the INSTALL file.
35