X-Git-Url: http://git.linex4red.de/pub/USBasp.git/blobdiff_plain/2b43a6d7df6221b979f08326c02eb1cfdd077c49..7c9c3d15e0b772a8bf26c9695236b80cb26c71b5:/LUFA/DoxygenPages/BuildSystem.txt
diff --git a/LUFA/DoxygenPages/BuildSystem.txt b/LUFA/DoxygenPages/BuildSystem.txt
index 564033200..7ddfa1be3 100644
--- a/LUFA/DoxygenPages/BuildSystem.txt
+++ b/LUFA/DoxygenPages/BuildSystem.txt
@@ -6,14 +6,14 @@
/** \page Page_BuildSystem The LUFA Build System
*
- * \section Sec_BuildSystemOverview Overview of the LUFA Build System
+ * \section Sec_BuildSystem_Overview Overview of the LUFA Build System
* The LUFA build system is an attempt at making a set of re-usable, modular build make files which
* can be referenced in a LUFA powered project, to minimize the amount of code required in an
* application makefile. The system is written in GNU Make, and each module is independent of
* one-another.
*
* For details on the prerequisites needed for Linux and Windows machines to be able to use the LUFA
- * build system, see \ref Sec_Prerequisites.
+ * build system, see \ref Sec_CompilingApps_Prerequisites.
*
* To use a LUFA build system module, simply add an include to your project makefile. All user projects
* should at a minimum include \ref Page_BuildModule_CORE for base functionality:
@@ -25,13 +25,13 @@
* project's build makefile targets automatically. To call a build target, run make {TARGET_NAME}
* from the command line, substituting in the appropriate target name.
*
- * \see \ref Sec_AppMakefileParams for a copy of the sample LUFA project makefile.
+ * \see \ref Sec_ConfiguringApps_AppMakefileParams for a copy of the sample LUFA project makefile.
*
* Each build module may have one or more mandatory parameters (GNU Make variables) which must
* be supplied in the project makefile for the module to work, and one or more optional parameters which
* may be defined and which will assume a sensible default if not.
*
- * \section SSec_BuildSystemModules Available Modules
+ * \section SSec_BuildSystem_Modules Available Modules
*
* The following modules are included in this LUFA release:
*
@@ -88,6 +88,10 @@
*
Build and link the application into an ELF debug file. |
*
*
+ * | bin |
+ * Build and link the application and produce a BIN binary file. |
+ *
+ *
* | hex |
* Build and link the application and produce HEX and EEP binary files. |
*
@@ -186,6 +190,10 @@
* Common flags to pass to the C/C++ compiler and assembler, after the automatically generated flags. |
*
*
+ * | COMPILER_PATH |
+ * Directory where the C/C++ toolchain is located, if not available in the system PATH. |
+ *
+ *
* | LD_FLAGS |
* Flags to pass to the linker, after the automatically generated flags. |
*
@@ -316,7 +324,7 @@
* \section SSec_BuildModule_ATPROGRAM_Requirements Requirements
* This module requires the atprogram.exe utility to be available in your system's PATH
* variable. The atprogram.exe utility is distributed in Atmel AVR Studio 5.x and Atmel Studio 6.x
- * inside the application install folder's "\avrdbg" subdirectory.
+ * inside the application install folder's "\atbackend" subdirectory.
*
* \section SSec_BuildModule_ATPROGRAM_Targets Targets
*
@@ -785,7 +793,7 @@
*
* The SOURCES LUFA build system module, providing variables listing the various LUFA source files
* required to be build by a project for a given LUFA module. This module gives a way to reference
- * LUFA source files symbollically, so that changes to the library structure do not break the library
+ * LUFA source files symbolically, so that changes to the library structure do not break the library
* makefile.
*
* To use this module in your application makefile, add the following code:
@@ -905,7 +913,7 @@
*
* | Error "Makefile {X} option must be Y or N" shown when compiling. |
* The specified Makefile value was configured in your project's makefile or on the command line, but was set to a value other than a Y (for "Yes") or "N" (for "No").
- * This configuration option is required to be one of the aformentioned boolean values, and other values are invalid. Set this option to either Y or N and try again. |
+ * This configuration option is required to be one of the aforementioned boolean values, and other values are invalid. Set this option to either Y or N and try again.
*
*
* | Error "Unknown input source file formats: {X}" shown when compiling. |
@@ -916,7 +924,7 @@
* Error "Cannot build with OBJDIR parameter set - one or more object file name is not unique" shown when compiling. |
* When a project is built with a non-empty OBJDIR object directory name set, all input source files must have unique names, excluding extension and path.
* This means that input files that are named identically and differ only by their path or extension are invalid when this mode is used. |
- *
+ *
*
* | Error "Source file does not exist: {X}" shown when compiling. |
* The nominated input source file, specified in the user project's SRC parameter, could not be found. Ensure the source file exists and the absolute or
@@ -935,17 +943,6 @@
* upgrade to the latest AVR-GCC. If the option is a valid linker option, use the prefix "-Wl," to ensure it is passed to the linker correctly. |
*
*
- * | Error "avr-gcc: error: unrecognized option '{X}'" shown when compiling. |
- * An unrecognised option was supplied to the compiler, usually in the C_FLAGS, CPP_FLAGS, ASM_FLAGS or CC_FLAGS configuration
- * options. The nominated compiler switch may be invalid, or unsupported by the version of AVR-GCC on the host system. Remove the unrecognised flag if invalid, or
- * upgrade to the latest AVR-GCC. If the option is a valid linker option, use the prefix "-Wl," to ensure it is passed to the linker correctly. |
- *
- *
- * | Error "makefile:{X}: {Y}.mk: No such file or directory" shown when make is invoked. |
- * The path to the nominated makefile module was incorrect. This usually indicates that the makefile LUFA_PATH option is not set to a valid relative or
- * absolute path to the LUFA library core. |
- *
- *
* | Error "makefile:{X}: {Y}.mk: No such file or directory" shown when make is invoked. |
* The path to the nominated makefile module was incorrect. This usually indicates that the makefile LUFA_PATH option is not set to a valid relative or
* absolute path to the LUFA library core. |
@@ -964,15 +961,10 @@
*
*
* | Error "unknown MCU '{X}' specified" shown when compiling. |
- * The specified micocontroller device model name set in the user application's makefile as the MCU parameter is incorrect, or unsupported by the
+ * | The specified microcontroller device model name set in the user application's makefile as the MCU parameter is incorrect, or unsupported by the
* version of the compiler being used. Make sure the model name is correct, or upgrade to the latest Atmel Toolchain to obtain newer device support. |
*
*
- * | Error "error: invalid suffix "x" on integer constant" shown when compiling a bootloader. |
- * This is usually caused by the bc.exe application not being found in the system's PATH variable. Make sure you have the bc.exe tool
- * installed correctly (see \ref Sec_Prerequisites). |
- *
- *
* | Error "undefined reference to `{X}'" shown when compiling. |
* This is usually caused by a missing source file in the user application's SRC configuration parameter. If the indicated symbol is one from the LUFA
* library, you may be missing a LUFA source makefile module (see \ref Page_BuildModule_SOURCES). |
@@ -980,4 +972,4 @@
*
*
* For troubleshooting other errors you encounter, please see \ref Sec_ProjectHelp.
- */
\ No newline at end of file
+ */