X-Git-Url: http://git.linex4red.de/pub/USBasp.git/blobdiff_plain/1fe8e29ab321ad9818f299fb3fb8c0d6cf70fe6e..04d13d264c924d5c3380076f8977ca2dd0b14fd8:/LUFA/DoxygenPages/CompilingApps.txt diff --git a/LUFA/DoxygenPages/CompilingApps.txt b/LUFA/DoxygenPages/CompilingApps.txt index ed210a123..f41b80517 100644 --- a/LUFA/DoxygenPages/CompilingApps.txt +++ b/LUFA/DoxygenPages/CompilingApps.txt @@ -14,9 +14,9 @@ * compilation of LUFA based applications. * * \subsection SSec_PreqWindows Windows Prerequisites - * On Windows, you will need a copy of the latest Atmel Toolchain, either downloaded and installed as a standalone - * package, or installed as part of Atmel Studio. You will need to ensure that the "bin" directory of the toolchain - * is available in your system's PATH environment variable. + * On Windows, you will need a copy of the latest Atmel Toolchain (http://www.atmel.com/tools/ATMELAVRTOOLCHAINFORWINDOWS.aspx), + * either downloaded and installed as a standalone package, or installed as part of Atmel Studio. You will need to ensure + * that the "bin" directory of the toolchain is available in your system's PATH environment variable. * * In addition, you will need to install a ported version of the ZSH or BASH *nix shells, and a standard set of *nix * utilities such as cut, find and sed. These can be found in the "basic" system package of the @@ -25,15 +25,15 @@ * * \subsection SSec_PreqLinux Linux Prerequisites * On Linux systems you will need to install the latest Linux distribution of the standalone Atmel Toolchain from the - * Atmel website for general development, or use the latest avr-libc and avr-gcc packages for your chosen distribution's - * package manager. For full device support, the Atmel standalone package is recommended. + * Atmel website (http://www.atmel.com/tools/ATMELAVRTOOLCHAINFORLINUX.aspx), or use the latest avr-libc and avr-gcc packages + * for your chosen distribution's package manager. For full device support, the Atmel standalone Toolchain package is recommended. * * \section Sec_Compiling Compiling a LUFA Application * Compiling the LUFA demos, applications and/or bootloaders is very simple. LUFA comes with makefile scripts for * 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 @@ -41,4 +41,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. */