From 2eb47bea14a5c98eddcedbc4ff38583d9bfbb1d3 Mon Sep 17 00:00:00 2001 From: Dean Date: Mon, 16 Jul 2012 17:11:14 +0000 Subject: Tag for the LUFA-120730-BETA release. git-svn-id: http://lufa-lib.googlecode.com/svn/tags/LUFA-120730-BETA@2407 d5102386-fcda-11dd-9fdb-3debd5008f28 --- LUFA/DoxygenPages/CompilingApps.txt | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) (limited to 'LUFA/DoxygenPages/CompilingApps.txt') diff --git a/LUFA/DoxygenPages/CompilingApps.txt b/LUFA/DoxygenPages/CompilingApps.txt index bbed994c..40e03a7a 100644 --- a/LUFA/DoxygenPages/CompilingApps.txt +++ b/LUFA/DoxygenPages/CompilingApps.txt @@ -37,7 +37,7 @@ * each individual demo, bootloader and project folder, as well as scripts in the Demos/, Bootloaders/, Projects/ * and the LUFA root directory. Compilation of projects can be started from any of the above directories, with a build * started from an upper directory in the directory structure executing build of all child directories under it. This - * means that while a build inside a particular demo directory will build only that particular demo, a build stated from + * means that while a build inside a particular demo directory will build only that particular demo, a build started from * the /Demos/ directory will build all LUFA demo projects sequentially. * * To build a project from the source via the command line, the command "make all" should be executed from the command @@ -45,4 +45,6 @@ * diagnostic output files), execute "make clean". Once a "make all" has been run and no errors were encountered, the * resulting binary will be located in the generated ".HEX" file. If your project makes use of pre-initialized EEPROM * variables, the generated ".EEP" file will contain the project's EEPROM data. + * + * \see \ref Page_BuildSystem for information on the LUFA build system. */ -- cgit v1.2.3