equal
deleted
inserted
replaced
1 Installation Instructions |
1 Installation Instructions |
2 ========================= |
2 ========================= |
3 |
3 |
4 Since you are reading this I assume you already obtained one of the release |
4 Since you are reading this I assume you already obtained one of the release |
5 tarballs and successfully extracted it. The latest version of LEMON is |
5 tarballs and successfully extracted it. The latest version of LEMON is |
6 available at our web page (http://lemon.cs.elte.hu/). |
6 available at our web page (http://lemon.cs.elte.hu/). |
7 |
7 |
8 In order to install LEMON from the extracted source tarball you have to |
8 In order to install LEMON from the extracted source tarball you have to |
9 issue the following commands: |
9 issue the following commands: |
10 |
10 |
11 1. `cd lemon-x.y.z' |
11 1. `cd lemon-x.y.z' |
12 |
12 |
13 This command changes to the directory which was created when you |
13 This command changes to the directory which was created when you |
19 creates the makefiles. |
19 creates the makefiles. |
20 |
20 |
21 3. `make' |
21 3. `make' |
22 |
22 |
23 This command compiles the non-template part of LEMON into libemon.a |
23 This command compiles the non-template part of LEMON into libemon.a |
24 file. It also compiles the programs in the tools, benchmark and demo |
24 file. It also compiles the programs in the tools and demo subdirectories |
25 subdirectories when enabled. |
25 when enabled. |
26 |
26 |
27 4. `make check' |
27 4. `make check' |
28 |
28 |
29 This step is optional, but recommended. It runs the test programs that |
29 This step is optional, but recommended. It runs the test programs that |
30 we developed for LEMON to check whether the library works properly on |
30 we developed for LEMON to check whether the library works properly on |
47 |
47 |
48 |
48 |
49 Configure Options and Variables |
49 Configure Options and Variables |
50 =============================== |
50 =============================== |
51 |
51 |
52 In step 2 you can customize the actions of configure by setting variables |
52 In step 2 you can customize the actions of configure by setting variables |
53 and passing options to it. This can be done like this: |
53 and passing options to it. This can be done like this: |
54 `./configure [OPTION]... [VARIABLE=VALUE]...' |
54 `./configure [OPTION]... [VARIABLE=VALUE]...' |
55 |
55 |
56 Below you will find some useful variables and options (see |
56 Below you will find some useful variables and options (see `./configure --help' |
57 `./configure --help' for more): |
57 for more): |
58 |
58 |
59 CXX='comp' |
59 CXX='comp' |
60 |
60 |
61 Change the C++ compiler to 'comp'. |
61 Change the C++ compiler to 'comp'. |
62 |
62 |
74 Build the examples in the demo subdirectory. |
74 Build the examples in the demo subdirectory. |
75 |
75 |
76 --disable-demo |
76 --disable-demo |
77 |
77 |
78 Do not build the examples in the demo subdirectory (default). |
78 Do not build the examples in the demo subdirectory (default). |
79 |
|
80 --enable-benchmark |
|
81 |
|
82 Build the programs in the benchmark subdirectory. |
|
83 |
|
84 --disable-benchmark |
|
85 |
|
86 Do not build the programs in the benchmark subdirectory (default). |
|
87 |
79 |
88 --enable-tools |
80 --enable-tools |
89 |
81 |
90 Build the programs in the tools subdirectory (default). |
82 Build the programs in the tools subdirectory (default). |
91 |
83 |