diff options
Diffstat (limited to 'README.CMake.txt')
| -rw-r--r-- | README.CMake.txt | 38 |
1 files changed, 19 insertions, 19 deletions
diff --git a/README.CMake.txt b/README.CMake.txt index 370e97e43..57c0cc9b0 100644 --- a/README.CMake.txt +++ b/README.CMake.txt @@ -5,8 +5,8 @@ README.CMake.txt - Building and using FLTK with CMake CONTENTS ========== - 1 Introduction to CMake - 2 Using CMake to Build FLTK + 1 Introduction to CMake + 2 Using CMake to Build FLTK 2.1 Prerequisites 2.2 Options 2.3 Building under Linux with Unix Makefiles @@ -14,10 +14,10 @@ README.CMake.txt - Building and using FLTK with CMake 2.5 Building under Windows with MinGW using Makefiles 2.6 Building under MacOS with Xcode 2.7 Crosscompiling - 3 Using CMake with FLTK + 3 Using CMake with FLTK 3.1 Library Names 3.2 Using Fluid Files - 4 Document History + 4 Document History 1. INTRODUCTION TO CMAKE @@ -246,15 +246,15 @@ in the GUI (cmake-gui). to where you've extracted an fltk distribution tar file (or snapshot tar file), and run the following commands: - cd C:\fltk-1.4.x <-- change to your FLTK directory - mkdir build <-- create an empty directory + cd C:\fltk-1.4.x <-- change to your FLTK directory + mkdir build <-- create an empty directory cd build cmake -G "Visual Studio 7" -D CMAKE_BUILD_TYPE=Release .. IMPORTANT: The trailing ".." on the cmake command must be specified (it is NOT an ellipsis). ^^^^^^^^^^^^^^^^^ - This will create the file FLTK.sln in the current 'build' directory. + This will create the file FLTK.sln in the current 'build' directory. 3) Open Visual Studio 7, and choose File -> Open -> Project, and pick the "FLTK.sln" created by step #2 in the 'build' directory. @@ -267,7 +267,7 @@ in the GUI (cmake-gui). 5) In the "Solution Explorer", right click on: - Solution 'FLTK' (## projects) + Solution 'FLTK' (## projects) ..and in the popup menu, choose "Build Solution" @@ -275,25 +275,25 @@ in the GUI (cmake-gui). The test programs (*.exe) can be found in e.g. - Release: C:\fltk-1.4.x\build\bin\examples\release\*.exe - Debug: C:\fltk-1.4.x\build\bin\examples\debug\*.exe + Release: C:\fltk-1.4.x\build\bin\examples\release\*.exe + Debug: C:\fltk-1.4.x\build\bin\examples\debug\*.exe ..and the FLTK include files (*.H & *.h) your own apps can compile with can be found in: - Release & Debug: C:\fltk-1.4.x\build\FL - *and* [1] in: C:\fltk-1.4.x\FL + Release & Debug: C:\fltk-1.4.x\build\FL + *and* [1] in: C:\fltk-1.4.x\FL ..and the FLTK library files (*.lib) which your own apps can link with can be found in: - Release: C:\fltk-1.4.x\build\lib\release\*.lib - Debug: C:\fltk-1.4.x\build\lib\debug\*.lib + Release: C:\fltk-1.4.x\build\lib\release\*.lib + Debug: C:\fltk-1.4.x\build\lib\debug\*.lib [1] If you want to build your own FLTK application directly using - the build directories (i.e. without "installation") you need - to include both the build tree (first) and then the FLTK source - tree in the compiler's header search list. + the build directories (i.e. without "installation") you need + to include both the build tree (first) and then the FLTK source + tree in the compiler's header search list. 2.5 Building under Windows with MinGW using Makefiles @@ -540,8 +540,8 @@ include_directories(${FLTK_INCLUDE_DIRS}) #run fluid -c to generate CubeViewUI.cxx and CubeViewUI.h files add_custom_command( - OUTPUT "CubeViewUI.cxx" "CubeViewUI.h" - COMMAND fluid -c ${CMAKE_CURRENT_SOURCE_DIR}/CubeViewUI.fl + OUTPUT "CubeViewUI.cxx" "CubeViewUI.h" + COMMAND fluid -c ${CMAKE_CURRENT_SOURCE_DIR}/CubeViewUI.fl ) include_directories(${CMAKE_CURRENT_BINARY_DIR}) |
