0
3
1
1 |
INCLUDE_DIRECTORIES( |
|
2 |
${PROJECT_SOURCE_DIR} |
|
3 |
${PROJECT_BINARY_DIR} |
|
4 |
) |
|
5 |
|
|
6 |
LINK_DIRECTORIES( |
|
7 |
${PROJECT_BINARY_DIR}/lemon |
|
8 |
) |
|
9 |
|
|
10 |
# Uncomment (and adjust) the following two lines. 'myprog' is the name |
|
11 |
# of the final executable ('.exe' will automatically be added to the |
|
12 |
# name on Windows) and 'myprog-main.cc' is the source code it is |
|
13 |
# compiled from. You can add more source files separated by |
|
14 |
# whitespaces. Moreover, you can add multiple similar blocks if you |
|
15 |
# want to build more than one executables. |
|
16 |
|
|
17 |
# ADD_EXECUTABLE(myprog myprog-main.cc) |
|
18 |
# TARGET_LINK_LIBRARIES(myprog lemon) |
|
19 |
... | ... |
@@ -34,4 +34,17 @@ |
34 | 34 |
|
35 | 35 |
/** |
36 |
\dir contrib |
|
37 |
\brief Directory for user contributed source codes. |
|
38 |
|
|
39 |
You can place your own C++ code using LEMON into this directory, which |
|
40 |
will compile to an executable along with LEMON when you build the |
|
41 |
library. This is probably the easiest way of compiling short to medium |
|
42 |
codes, for this does require neither a LEMON installed system-wide nor |
|
43 |
adding several paths to the compiler. |
|
44 |
|
|
45 |
Please have a look at <tt>contrib/CMakeLists.txt</tt> for |
|
46 |
instruction on how to add your own files into the build process. */ |
|
47 |
|
|
48 |
/** |
|
36 | 49 |
\dir test |
37 | 50 |
\brief Test programs. |
0 comments (0 inline)