Move list of useful CMake variables from CMakeLists.txt to how-to-build-kicad.txt

This commit is contained in:
f3nix 2008-03-12 09:18:51 +00:00
parent 24a6c34ac9
commit bfc705ed20
2 changed files with 30 additions and 28 deletions

View File

@ -1,28 +1,3 @@
# List of variables that may be set from command line:
#
# CMAKE_BUILD_TYPE Release/Debug (REQUIRED)
# Choose build type: Release/Debug
#
# wxWidgets_USE_DEBUG ON/OFF (REQUIRED)
# Should be set to ON only when CMAKE_BUILD_TYPE=Debug.
#
# wxWidgets_USE_STATIC ON/OFF (OPTIONAL)
#
#
# CMAKE_VERBOSE_MAKEFILE ON/OFF (OPTIONAL)
# Turns ON/OFF verbose build messages.
# You can also pass VERBOSE=1 to make for the same effect.
#
# CMAKE_INSTALL_PREFIX (OPTIONAL)
#
#
# KICAD_MINIZIP ON/OFF
#
#
# KICAD_PYTHON ON/OFF
#
#
# Our project is called 'kicad'. This is what it will be called in # Our project is called 'kicad'. This is what it will be called in
# our makefiles. # our makefiles.
project(kicad) project(kicad)

View File

@ -1,6 +1,6 @@
--== How to build kicad using CMAKE ==-- --== How to build kicad using CMAKE ==--
First Written: 19-Dec-2007 First Written: 19-Dec-2007
Last Revised: 11-Mar-2008 Last Revised: 12-Mar-2008
Kicad needs wxWidgets, the multi platform G.U.I. Kicad needs wxWidgets, the multi platform G.U.I.
@ -20,6 +20,7 @@ sections below.)
9) Use cmake to build the kicad makefiles. 9) Use cmake to build the kicad makefiles.
10) Use make to build and install kicad. 10) Use make to build and install kicad.
11) Making a "Debug" build. 11) Making a "Debug" build.
12) Variables for fine-tuning the build process.
===== Step Details ==================================================== ===== Step Details ====================================================
@ -87,7 +88,6 @@ development versions of the wxWidgets packages which include the C++ headers. An
alternative is to build static libaries from source. Verify that wx-config is in alternative is to build static libaries from source. Verify that wx-config is in
your path by running it from a command prompt. Linux users then go to next step. your path by running it from a command prompt. Linux users then go to next step.
----------------------------------------------------------------------------- -----------------------------------------------------------------------------
5) Install zlib [and build it if on windows]. 5) Install zlib [and build it if on windows].
@ -145,7 +145,6 @@ instead of installing boost using your package manager, you should use the svn
HEAD copy which overcomes the gcc 4.2 incompatibility, specifically with HEAD copy which overcomes the gcc 4.2 incompatibility, specifically with
<boost/ptr_container/ptr_vector.hpp>. <boost/ptr_container/ptr_vector.hpp>.
----------------------------------------------------------------------------- -----------------------------------------------------------------------------
8) Install the kicad source tree. 8) Install the kicad source tree.
@ -219,6 +218,34 @@ Make the Debug binaries:
----------------------------------------------------------------------------- -----------------------------------------------------------------------------
12) Variables for fine-tuning the build process.
These should be set from command line:
CMAKE_BUILD_TYPE Release/Debug (REQUIRED)
Choose build type: Release/Debug.
wxWidgets_USE_DEBUG ON/OFF (REQUIRED)
Should be set to ON only when CMAKE_BUILD_TYPE=Debug.
wxWidgets_USE_STATIC ON/OFF (OPTIONAL)
CMAKE_VERBOSE_MAKEFILE ON/OFF (OPTIONAL)
Turns ON/OFF verbose build messages.
You can also pass VERBOSE=1 to make for the same effect.
CMAKE_INSTALL_PREFIX (OPTIONAL)
KICAD_MINIZIP ON/OFF
KICAD_PYTHON ON/OFF
-----------------------------------------------------------------------------
Note: that it is easy to build only a specific binary such as pcbnew alone: Note: that it is easy to build only a specific binary such as pcbnew alone:
make pcbnew make pcbnew