X-Git-Url: http://git.linex4red.de/pub/USBasp.git/blobdiff_plain/3bd4011c0935e0d41af3ae59c69eec989cc53bbf..18b0d408a9e68cbc1ce36da89d74a799d7fc31de:/LUFA/ManPages/CompilingApps.txt?ds=sidebyside

diff --git a/LUFA/ManPages/CompilingApps.txt b/LUFA/ManPages/CompilingApps.txt
index b1d5ed6ed..b4ee17171 100644
--- a/LUFA/ManPages/CompilingApps.txt
+++ b/LUFA/ManPages/CompilingApps.txt
@@ -11,7 +11,7 @@
  *  \section Sec_Prerequisites Prerequisites
  *  Before you can compile any of the LUFA library code or demos, you will need a recent distribution of avr-libc (1.6.2+)
  *  and the AVR-GCC (4.2+) compiler. For Windows users, the best way to obtain these is the WinAVR project
- *  (http://winavr.sourceforge.net) as this provides a single-file setup for everything required to compile your
+ *  (<a>http://winavr.sourceforge.net</a>) as this provides a single-file setup for everything required to compile your
  *  own AVR projects.
  *
  *  \section Sec_Compiling Compiling a LUFA Application
@@ -22,15 +22,9 @@
  *  This means that while a build inside a particular demo directory will build only that particular demo, a build stated
  *  from the /Demos/ directory will build all LUFA demo projects sequentially.
  *
- *  \subsection SSec_CommandLine Via the Command Line
  *  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
  *  of interest. To remove compiled files (including the binary output, all intermediately files and all diagnostic output
  *  files), execute <b>"make clean"</b>. 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.
- *
- *  \subsection SSec_AVRStudio Via AVRStudio
- *  Each demo, project and bootloader contains an AVRStudio project (.aps) which can be used to build each project. Once opened
- *  in AVRStudio, the project can be built and cleaned using the GUI buttons or menus. Note that the AVRStudio project files make
- *  use of the external project makefile, thus the procedure for configuring a demo remains the same regardless of the build environment.
  */
\ No newline at end of file