* \section Sec_Prerequisites Prerequisites\r
* Before you can compile any of the LUFA library code or demos, you will need a recent distribution of avr-libc (1.6.2+)\r
* and the AVR-GCC (4.2+) compiler. For Windows users, the best way to obtain these is the WinAVR project\r
- * (http://winavr.sourceforge.net) as this provides a single-file setup for everything required to compile your\r
+ * (<a>http://winavr.sourceforge.net</a>) as this provides a single-file setup for everything required to compile your\r
* own AVR projects.\r
*\r
* \section Sec_Compiling Compiling a LUFA Application\r
* This means that while a build inside a particular demo directory will build only that particular demo, a build stated\r
* from the /Demos/ directory will build all LUFA demo projects sequentially.\r
*\r
- * \subsection SSec_CommandLine Via the Command Line\r
* To build a project from the source via the command line, the command <b>"make all"</b> should be executed from the command line in the directory\r
* of interest. To remove compiled files (including the binary output, all intermediately files and all diagnostic output\r
* files), execute <b>"make clean"</b>. Once a "make all" has been run and no errors were encountered, the resulting binary will\r
* be located in the generated ".HEX" file. If your project makes use of pre-initialized EEPROM variables, the generated ".EEP"\r
* file will contain the project's EEPROM data.\r
- *\r
- * \subsection SSec_AVRStudio Via AVRStudio\r
- * Each demo, project and bootloader contains an AVRStudio project (.aps) which can be used to build each project. Once opened\r
- * in AVRStudio, the project can be built and cleaned using the GUI buttons or menus. Note that the AVRStudio project files make\r
- * use of the external project makefile, thus the procedure for configuring a demo remains the same regardless of the build environment.\r
*/
\ No newline at end of file
projects / pub / USBasp.git / blobdiff