Commit 64da190e authored by Blair Bonnett's avatar Blair Bonnett Committed by Wayne Stambaugh

Build documentation updates and comment spelling fixes.

parent c5a2028a
...@@ -100,9 +100,9 @@ set( DOWNLOAD_DIR ${PROJECT_SOURCE_DIR}/.downloads-by-cmake ...@@ -100,9 +100,9 @@ set( DOWNLOAD_DIR ${PROJECT_SOURCE_DIR}/.downloads-by-cmake
LINK_DIRECTORIES( ${LINK_DIRECTORIES_PATH} ) LINK_DIRECTORIES( ${LINK_DIRECTORIES_PATH} )
if( UNIX ) if( UNIX )
set( KICAD_USER_CONFIG_DIR $ENV{HOME} CACHE PATH "Location of user specifig KiCad config files" ) set( KICAD_USER_CONFIG_DIR $ENV{HOME} CACHE PATH "Location of user specific KiCad config files" )
elseif( MINGW ) elseif( MINGW )
set( KICAD_USER_CONFIG_DIR $ENV{%APPDATA%} CACHE PATH "Location of user specifig KiCad config files" ) set( KICAD_USER_CONFIG_DIR $ENV{%APPDATA%} CACHE PATH "Location of user specific KiCad config files" )
endif() endif()
mark_as_advanced( KICAD_USER_CONFIG_DIR ) mark_as_advanced( KICAD_USER_CONFIG_DIR )
......
...@@ -212,4 +212,5 @@ Make the Debug binaries: ...@@ -212,4 +212,5 @@ Make the Debug binaries:
make make
See ./cmake_config.txt for customizing the KiCad build setting. See Documentation/compiling/build-config.txt for a list of all CMake options
available when compiling KiCad.
Bazaar Bazaar
------ ======
KiCad uses the Bazaar version control system to track source code changes, KiCad uses the Bazaar version control system to track source code changes,
and download the boost libraries needed by Kicad. and download the boost libraries needed by Kicad.
The easiest way to get a copy of the KiCad source is to use Bazaar. The easiest way to get a copy of the KiCad source is to use Bazaar.
...@@ -11,7 +12,8 @@ Be sure bzrtools is also installed. ...@@ -11,7 +12,8 @@ Be sure bzrtools is also installed.
boost libraries will be downloaded the first time you build Kicad. boost libraries will be downloaded the first time you build Kicad.
CMake CMake
----- =====
KiCad uses CMake to generate the build files specific for the target platform KiCad uses CMake to generate the build files specific for the target platform
specified by the developer. This document attempts to define some of the more specified by the developer. This document attempts to define some of the more
common CMake and KiCad build configuration settings. You can use CMake either common CMake and KiCad build configuration settings. You can use CMake either
...@@ -23,7 +25,8 @@ http://www.cmake.org/cmake/help/documentation.html. ...@@ -23,7 +25,8 @@ http://www.cmake.org/cmake/help/documentation.html.
Useful CMake Build Settings. Useful CMake Build Settings.
---------------------------- ============================
This section defines some of the more common CMake build configuration setting This section defines some of the more common CMake build configuration setting
used when configuring KiCad. These settings are valid for all projects that used when configuring KiCad. These settings are valid for all projects that
use CMake. use CMake.
...@@ -39,14 +42,18 @@ switch on the command line. Please note, only a small subset of these project ...@@ -39,14 +42,18 @@ switch on the command line. Please note, only a small subset of these project
generators are supported. If you want to use Eclipse on Linux to build KiCad, generators are supported. If you want to use Eclipse on Linux to build KiCad,
you may be in for a lot of work. you may be in for a lot of work.
CMAKE_BUILD_TYPE (Release/Debug/RelWithDebInfo/MinSizeRel) CMAKE_BUILD_TYPE (Release/Debug/RelWithDebInfo/MinSizeRel)
---------------------------------------------------------- ----------------------------------------------------------
Default: Release
When configuring the KiCad build for the command line you must specify build When configuring the KiCad build for the command line you must specify build
type. To create a debug build, set CMAKE_BUILD_TYPE to Debug. To create a type. To create a debug build, set CMAKE_BUILD_TYPE to Debug. To create a
release build, set CMAKE_BUILD_TYPE to Release. See the CMake documentation release build, set CMAKE_BUILD_TYPE to Release. See the CMake documentation
for other build types. For IDE project files, the build type can be selected for other build types. For IDE project files, the build type can be selected
by the IDE configuration manager. by the IDE configuration manager.
CMAKE_INSTALL_PATH (InstallPath) CMAKE_INSTALL_PATH (InstallPath)
-------------------------------- --------------------------------
By default CMake will select the correct install path for your platform. If By default CMake will select the correct install path for your platform. If
...@@ -57,7 +64,8 @@ installed on your system. ...@@ -57,7 +64,8 @@ installed on your system.
wxWidgets Library Configuration. wxWidgets Library Configuration.
-------------------------------- ================================
KiCad is built using the wxWidgets library. The following options allow you KiCad is built using the wxWidgets library. The following options allow you
to specifically tailor the wxWidgets library configuration. For the complete to specifically tailor the wxWidgets library configuration. For the complete
list of wxWidgets setting see CMakeModules/FindwxWidgets.cmake in the KiCad list of wxWidgets setting see CMakeModules/FindwxWidgets.cmake in the KiCad
...@@ -69,85 +77,147 @@ CMake looks in the standard platform locations to find the default version of ...@@ -69,85 +77,147 @@ CMake looks in the standard platform locations to find the default version of
the wxWidgets library. If you wish to use a custom built wxWidgets library, the wxWidgets library. If you wish to use a custom built wxWidgets library,
set wxWidgets_ROOT_DIR to the correct path. set wxWidgets_ROOT_DIR to the correct path.
wxWidgets_USE_DEBUG (ON/OFF) wxWidgets_USE_DEBUG (ON/OFF)
---------------------------- ----------------------------
Default: OFF
When creating a debug build of KiCad, it is often useful to link against the When creating a debug build of KiCad, it is often useful to link against the
debug build of the wxWidgets. To use the debug build of wxWidgets, set debug build of the wxWidgets. To use the debug build of wxWidgets, set
wxWidgets_USE_DEBUG to ON. wxWidgets_USE_DEBUG to ON.
wxWidgets_USE_UNICODE (ON/OFF) wxWidgets_USE_UNICODE (ON/OFF)
------------------------------ ------------------------------
Default: ON (wxWidgets 2.9 or later), OFF (older versions)
If your platform supports Unicode and you wish to build KiCad with Unicode If your platform supports Unicode and you wish to build KiCad with Unicode
support, set wxWidgets_USE_UNICODE to ON. Please note as of the 2.9 branch support, set wxWidgets_USE_UNICODE to ON. Please note as of the 2.9 branch
this option is not required. this option is not required.
KiCad Specific Options KiCad Specific Options
---------------------- ======================
All of the configuration settings below are specific to the KiCad project. All of the configuration settings below are specific to the KiCad project.
If for any reason you add or remove a build option to the KiCad CMake files, If for any reason you add or remove a build option to the KiCad CMake files,
please update the list below. please update the list below.
KICAD_SKIP_BOOST (ON/OFF) KICAD_SKIP_BOOST (ON/OFF)
-------------------------- --------------------------
Skips building the required boost library components. Default: OFF
WARNING: KiCad developers strongly advise you to build the bundled boost library, as it is
known to work with KiCad. Other versions may contain bugs that may result in KiCad errors. Use the version of the Boost library installed on the system rather than
building a local copy.
WARNING: The KiCad developers strongly advise you to build the bundled copy of
the Boost library, as it is known to work with KiCad. Other versions may
contain bugs that may result in KiCad errors.
USE_WX_GRAPHICS_CONTEXT (ON/OFF) USE_WX_GRAPHICS_CONTEXT (ON/OFF)
-------------------------------- --------------------------------
This option is *Experimental* and used the advanced drawing library code Default: OFF
using wxGraphicsContext and should only be used for testing purposes.
Under Windows, a very recent version of mingw is needed. It also requires This option is *Experimental*. It enables advanced drawing library code using
wxWidgets to be built with the --enable-graphics_ctx configuration switch. wxGraphicsContext and should only be used for testing purposes. Under Windows,
a very recent version of mingw is needed. It also requires wxWidgets to be
built with the --enable-graphics_ctx configuration switch.
USE_IMAGES_IN_MENUS (ON/OFF) USE_IMAGES_IN_MENUS (ON/OFF)
---------------------------- ----------------------------
Default: OFF for OSX, ON for other platforms.
This option is used to enable or disable building KiCad with images in menu This option is used to enable or disable building KiCad with images in menu
items. If this is not defined when CMake is used to create the build files, items. If this is not defined when CMake is used to create the build files,
images will be included in menu items on all platforms except OSX. images will be included in menu items on all platforms except OSX.
DOWNLOAD_DIR (PATH)
-------------------
Default: <source directory>/.downloads-by-cmake
Some external dependencies are automatically download and built when you
compile KiCad. This option specifies which directory they are stored in. If you
are building multiple copies of KiCad (e.g., to test different features or your
own modifications), it is recommended you set this option to a global directory
to avoid download and building the dependencies multiple times.
KICAD_USER_CONFIG_DIR (PATH)
----------------------------
Default: Home directory (Unix-based systems), Application data directory (Windows)
This option specifies where to store user-specific configuration information.
KICAD_KEEPCASE (ON/OFF) KICAD_KEEPCASE (ON/OFF)
----------------------- -----------------------
This option enables or disables turning off the automatic component name Default: ON
conversion to uppercase. The default is OFF which means component names will
be converted to upper case. If this is OFF, component names are automatically converted to uppercase meaning
they are case insensitive. If it is ON, component names are not changed and
are therefore case sensitive.
USE_WX_OVERLAY (ON/OFF) USE_WX_OVERLAY (ON/OFF)
----------------------- -----------------------
This option enables or disables wxOverlay for drawing operation on OSX. It is Default: ON for OSX, OFF for other platforms.
OFF by default on all platforms except OSX. Warning, this is experimental!
This option enables or disables the use of wxOverlay for drawing operations.
Warning, this is experimental!
KICAD_SCRIPTING (ON/OFF) KICAD_SCRIPTING (ON/OFF)
------------------------ ------------------------
This option enables or disables building Python scripting support for KiCad. Default: OFF
The default is OFF. Currently only Pcbnew is supported. This option requires
that SWIG and Python are installed on the system. This option enables or disables building Python scripting support within KiCad.
Currently only Pcbnew is supported. This option requires SWIG and Python to be
installed on the system.
KICAD_SCRIPTING_MODULES (ON/OFF) KICAD_SCRIPTING_MODULES (ON/OFF)
-------------------------------- --------------------------------
This option enables or disables building the KiCad modules that can be used Default: OFF
from scripting languages. The default is OFF. Currently only Pcbnew is
supported. This option requires that SWIG and Python are installed on the This option enables or disables building KiCad Python modules that can be used
system. externally by Python. Currently only Pcbnew is supported. This option
requires SWIG and Python to be installed on the system.
KICAD_SCRIPTING_WXPYTHON (ON/OFF) KICAD_SCRIPTING_WXPYTHON (ON/OFF)
--------------------------------- ---------------------------------
This option enables or disables building wxPython support into KiCad for Default: OFF
python and py.shell. The default is OFF. Currently only Pcbnew is
supported. This option requires that SWIG, Python, and wxPython are This option enables or disables building wxPython support into the KiCad
installed on the system. scripting support. Currently only Pcbnew is supported. This option requires
SWIG, Python, and wxPython to be installed on the system.
PYTHON_SITE_PACKAGE_PATH (PATH) PYTHON_SITE_PACKAGE_PATH (PATH)
------------------------------- -------------------------------
Default: System site library path
When building KiCad with Python scripting enable, the Python site library path When building KiCad with Python scripting enable, the Python site library path
is used by default. If you want to install the KiCad Python extension in a is used by default. If you want to install the KiCad Python extension in a
different path, set this variable to the desired path. different path, set this variable to the desired path.
USE_FP_LIB_TABLE (ON/OFF) BUILD_GITHUB_PLUGIN (ON/OFF)
------------------------- ----------------------------
This option enable or disables building KiCad with the new footprint library Default: OFF
table support. The default setting (OFF) builds KiCad with the legacy library
path support. This option is experimental until the library table support is This option enables or disables building KiCad with a pcbnew plugin for loading
ready for release. footprints from a GitHub repository.
KICAD_REPO_NAME (STRING)
------------------------
Default: "product"
The name of the repository this copy of KiCad was compiled from. This is
reported in the "About" dialog and is useful for people who are working with
multiple copies of the code from different sources. The default value is
"product", the name of the main development branch on Launchpad.
...@@ -170,6 +170,9 @@ build directory. ...@@ -170,6 +170,9 @@ build directory.
Important parameters to cmake Important parameters to cmake
----------------------------- -----------------------------
See Documentation/compiling/build-config.txt for a list of all CMake options
available when compiling KiCad.
-DCMAKE_BUILD_TYPE=<buildtype> -DCMAKE_BUILD_TYPE=<buildtype>
<buildtype> may current one of "Debug" and "Release". <buildtype> may current one of "Debug" and "Release".
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment