X-Git-Url: http://g0dil.de/git?a=blobdiff_plain;f=senfscons%2FMainpage.dox;h=847b2ff70aa0baf9758aadc9903a176b98491783;hb=253a521bcdad22c825b154ab0f72d9514c8ec618;hp=daaad729d2c8906dab1c35d90e1e072b76acf4f9;hpb=2d51a34f79dd18b23c54172444b2cc7433b8f5f0;p=senf.git diff --git a/senfscons/Mainpage.dox b/senfscons/Mainpage.dox index daaad72..847b2ff 100644 --- a/senfscons/Mainpage.dox +++ b/senfscons/Mainpage.dox @@ -1,4 +1,4 @@ -// Copyright (C) 2007 +// Copyright (C) 2007 // Fraunhofer Institut fuer offene Kommunikationssysteme (FOKUS) // Kompetenzzentrum fuer Satelitenkommunikation (SatCom) // Stefan Bund @@ -47,18 +47,18 @@ namespace senfscons { framework however semi-automatically creates the necessary cross-reference information to cross-link the different module documentations. The unit-tests as well are run on a per-module basis. - + \section Standard Build Configuration When the \c SConsctruct and \c SConscript files are build using the default SENFSCons helpers, by default all libraries and binaries are built. Some additional targets are
scons all_tests
Build all unit tests
- +
scons all_docs
Build documentation of all modules
- +
scons all
Build all targets including binaries, libraries, documentation, - tests andpossible further targets
+ tests and possible further targets
scons -u doc
Run from within a module directory will build the documentation of that module
@@ -72,8 +72,8 @@ namespace senfscons { directory. \see - \ref sconstruct \n - \ref sconscript \n + \ref sconstruct \n + \ref sconscript \n \ref sconfig \n \ref builder */ @@ -91,14 +91,14 @@ namespace senfscons { The general structure of the \c SConstruct file is \li make the \c senfscons directory accessible \li tell the SENFScons infrastructure, which frameworks you intend to use and let SENFScons - built a construction environment for you + built a construction environment for you \li configure the construction environment \li load module sconscript file \li specify global build targets The first part, making the \c senfscons directory accessible will always stay the same. See the template file for how this is done. - + Simplifying the use of more complex frameworks is one of the most important things why SENFScons exists. If you only use very simple libraries, the configuration is quite simple. However for more complex frameworks the configuration can get quite complicated. This is @@ -106,7 +106,7 @@ namespace senfscons { and have a prefix of \c Use. See \ref use. After all frameworks are configured, you can use SEFNScons.MakeEnvironment() to create a - corretly configured construction environment. + correctly configured construction environment. To configure the construction environment you can set Variables in the construction environment. See the SCons manpage for a list of supported variables. Some additional variables @@ -125,9 +125,9 @@ namespace senfscons { software. Just remember, you can use all of python and all of SCons here. SENFScons just provides some additional helpers to make things simpler and more concise. - \see - \ref use \n - \ref target + \see + \ref use \n + \ref target */ /** \page sconscript The Module 'SConscript' Files @@ -143,14 +143,14 @@ namespace senfscons { targets of every module. \see - \ref target + \ref target */ /** \page sconfig The 'SConfig' File - + To configure the build environment to the local environment, a \c SConfig file may be created in the projects root directory. The supported parameters are - +
\c CXX
C++ compiler to use
\c EXTRA_DEFINES
preprocessor symbols to be defined locally
\c EXTRA_LIBS
additional libraries needed for a local build
@@ -165,7 +165,8 @@ namespace senfscons { // mode: c++ // fill-column: 100 // c-file-style: "senf" +// indent-tabs-mode: nil +// ispell-local-dictionary: "american" // mode: flyspell // mode: auto-fill -// ispell-local-dictionary: "american" // End: