[ create a new paste ] login | about

Link: http://codepad.org/Yuev7TWJ    [ raw code | fork ]

C, pasted on Aug 9:
# This command is optional, and may not be minimum required. It's just the version
# of cmake I used when creating this example.
cmake_minimum_required(VERSION 2.8)

# The name of our project is "HelloWorldDemo".  CMakeLists files in this project can
# refer to the root source directory of the project as ${HelloWorldDemo_SOURCE_DIR} and
# to the root binary directory of the project as ${HelloWorldDemo_BINARY_DIR}.
project (HelloWorldDemo)

# Location to write the executable
SET(EXECUTABLE_OUTPUT_PATH ${PROJECT_BINARY_DIR}/../Demo/bin)
SET(RUNTIME_OUTPUT_BINARY ${PROJECT_BINARY_DIR}/../Demo/bin)
set(RUNTIME_OUTPUT_DIRECTORY_DEBUG ${PROJECT_BINARY_DIR}/../Demo/bin)
set(RUNTIME_OUTPUT_DIRECTORY_RELEASE ${PROJECT_BINARY_DIR}/../Demo/bin)

#I don't really understand what these variables are.
#They don't seem to do anything.
set(RUNTIME_OUTPUT_NAME_DEBUG demo_d.exe)
set(RUNTIME_OUTPUT_NAME_RELEASE demo.exe)

#This doesn't do anything either!
set(CMAKE_CFG_INTDIR /)

# Location that "myMath" library will be stored.
SET(LIBRARY_OUTPUT_PATH ../SeperateMathLib/lib)

# Recurse into a seperate library and build it based on its own
# CMakeLists.txt file.
#First argument is where to find the next CMakeLists.txt in relation to this file
#Second argument is where to place the output files in relation to the directory cmake was called from.
add_subdirectory (../SeperateMathLib ../../SeperateMathLib)

# Location that the "Hello" libraries will be built.
SET(LIBRARY_OUTPUT_PATH ${PROJECT_BINARY_DIR}/../Hello/lib)

# Recurse into the "Hello" and "Demo" subdirectories.  This does not actually
# cause another cmake executable to run.  The same process will walk through
# the project's entire directory structure.
add_subdirectory (Hello)

add_subdirectory (Demo)


Create a new paste based on this one


Comments: