Changes in / [329:2592532ee838:330:d3a7603026a2] in lemon
- Files:
-
- 4 edited
Legend:
- Unmodified
- Added
- Removed
-
INSTALL
r245 r318 2 2 ========================= 3 3 4 4 Since you are reading this I assume you already obtained one of the release 5 5 tarballs and successfully extracted it. The latest version of LEMON is 6 6 available at our web page (http://lemon.cs.elte.hu/). 7 7 8 8 In order to install LEMON from the extracted source tarball you have to 9 9 issue the following commands: 10 10 … … 22 22 23 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 demo25 subdirectorieswhen enabled.24 file. It also compiles the programs in the tools and demo subdirectories 25 when enabled. 26 26 27 27 4. `make check' … … 50 50 =============================== 51 51 52 52 In step 2 you can customize the actions of configure by setting variables 53 53 and passing options to it. This can be done like this: 54 54 `./configure [OPTION]... [VARIABLE=VALUE]...' 55 55 56 Below you will find some useful variables and options (see 57 `./configure --help'for more):56 Below you will find some useful variables and options (see `./configure --help' 57 for more): 58 58 59 59 CXX='comp' … … 77 77 78 78 Do not build the examples in the demo subdirectory (default). 79 80 --enable-benchmark81 82 Build the programs in the benchmark subdirectory.83 84 --disable-benchmark85 86 Do not build the programs in the benchmark subdirectory (default).87 79 88 80 --enable-tools -
README
r310 r318 36 36 test/ 37 37 38 Contains programs to check the integrity and correctness of LEMON.38 Programs to check the integrity and correctness of LEMON. 39 39 40 40 tools/ -
doc/dirs.dox
r209 r318 19 19 /** 20 20 \dir demo 21 \brief A collection of demo application .21 \brief A collection of demo applications. 22 22 23 This directory contains several simple demo application , mainly23 This directory contains several simple demo applications, mainly 24 24 for educational purposes. 25 25 */ … … 29 29 \brief Auxiliary (and the whole generated) documentation. 30 30 31 Auxiliary (and the whole generated) documentation. 31 This directory contains some auxiliary pages and the whole generated 32 documentation. 32 33 */ 33 34 … … 42 43 /** 43 44 \dir tools 44 \brief Some useful executables 45 \brief Some useful executables. 45 46 46 47 This directory contains the sources of some useful complete executables. 47 48 48 */ 49 50 51 49 52 50 /** 53 51 \dir lemon 54 \brief Base include directory of LEMON 52 \brief Base include directory of LEMON. 55 53 56 This is the base directory of lemonincludes, so each include file must be54 This is the base directory of LEMON includes, so each include file must be 57 55 prefixed with this, e.g. 58 56 \code … … 64 62 /** 65 63 \dir concepts 66 \brief Concept descriptors and checking classes 64 \brief Concept descriptors and checking classes. 67 65 68 This directory contains the concept descriptors and concept check ers. As a user69 you typically don't have to deal with these files.66 This directory contains the concept descriptors and concept checking tools. 67 For more information see the \ref concept "Concepts" module. 70 68 */ 71 69 72 70 /** 73 71 \dir bits 74 \brief Implementation helper files72 \brief Auxiliary tools for implementation. 75 73 76 This directory contains some helper classes to implement graphs, maps and77 some other classes. As a user you typically don't have to deal with these 78 files.74 This directory contains some auxiliary classes for implementing graphs, 75 maps and some other classes. 76 As a user you typically don't have to deal with these files. 79 77 */ -
doc/groups.dox
r329 r330 136 136 @defgroup paths Path Structures 137 137 @ingroup datas 138 \brief Path structures implemented in LEMON.138 \brief %Path structures implemented in LEMON. 139 139 140 140 This group describes the path structures implemented in LEMON. … … 271 271 The purpose of the classes in this group is fourfold. 272 272 273 - These classes contain the documentations of the concepts. In order273 - These classes contain the documentations of the %concepts. In order 274 274 to avoid document multiplications, an implementation of a concept 275 275 simply refers to the corresponding concept class. 276 276 277 277 - These classes declare every functions, <tt>typedef</tt>s etc. an 278 implementation of the concepts should provide, however completely278 implementation of the %concepts should provide, however completely 279 279 without implementations and real data structures behind the 280 280 interface. On the other hand they should provide nothing else. All
Note: See TracChangeset
for help on using the changeset viewer.