X-Git-Url: http://git.linex4red.de/pub/lufa.git/blobdiff_plain/2b43a6d7df6221b979f08326c02eb1cfdd077c49..4175fe03ee384aee0f3efb26062acdcf8bba3a24:/LUFA/DoxygenPages/BuildSystem.txt?ds=sidebyside
diff --git a/LUFA/DoxygenPages/BuildSystem.txt b/LUFA/DoxygenPages/BuildSystem.txt
index 564033200..8a498a335 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. |
*
@@ -916,7 +920,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 +939,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. |
@@ -968,11 +961,6 @@
* 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 +968,4 @@
*
*
* For troubleshooting other errors you encounter, please see \ref Sec_ProjectHelp.
- */
\ No newline at end of file
+ */