From 0c0436f47c296513dace43d3ba20e3cc36f8f527 Mon Sep 17 00:00:00 2001 From: Trygve Laugstøl Date: Sun, 25 Mar 2012 17:46:26 +0200 Subject: Board, rev A. --- .../LUFA/ManPages/BuildingLinkableLibraries.txt | 23 ++++++++++++++++++++++ 1 file changed, 23 insertions(+) create mode 100644 firmware/LUFA/ManPages/BuildingLinkableLibraries.txt (limited to 'firmware/LUFA/ManPages/BuildingLinkableLibraries.txt') diff --git a/firmware/LUFA/ManPages/BuildingLinkableLibraries.txt b/firmware/LUFA/ManPages/BuildingLinkableLibraries.txt new file mode 100644 index 0000000..ff5fdc5 --- /dev/null +++ b/firmware/LUFA/ManPages/BuildingLinkableLibraries.txt @@ -0,0 +1,23 @@ +/** \file + * + * This file contains special DoxyGen information for the generation of the main page and other special + * documentation pages. It is not a project source file. + */ + +/** \page Page_BuildLibrary Building as a Linkable Library + * + * The LUFA library can be built as a proper linkable library (with the extention .a) under AVR-GCC, so that + * the library does not need to be recompiled with each revision of a user project. Instructions for creating + * a library from a given source tree can be found in the AVR-GCC user manual included in the WinAVR install + * /Docs/ directory. + * + * However, building the library is not recommended, as the static (compile-time) options will be + * unable to be changed without a recompilation of the LUFA code. Therefore, if the library is to be built + * from the LUFA source, it should be made to be application-specific and compiled with the static options + * that are required for each project (which should be recorded along with the library). + * + * Normal library use has the library components compiled in at the same point as the application code, as + * demonstrated in the library demos and applications. This is the preferred method, as the library is recompiled + * each time to ensure that all static options for a particular application are applied. + */ + -- cgit v1.2.3