Merge pull request #83 from QuarkTheAwesome/master

COS Docs: Enable JAVADOC_AUTOBRIEF

docs/CMakeLists.txt

@@ -29,6 +29,7 @@ if(DOXYGEN_FOUND)
       "WUT_UNKNOWN_BYTES"
       "WUT_UNKNOWN_SIZE")
    set(DOXYGEN_SOURCE_BROWSER YES)
+   set(DOXYGEN_JAVADOC_AUTOBRIEF YES)
    set(DOXYGEN_ENUM_VALUES_PER_LINE 1)
    set(DOXYGEN_CLASS_DIAGRAMS NO)
    set(DOXYGEN_COLLABORATION_GRAPH NO)

include/coreinit/cache.h

@@ -5,10 +5,10 @@
  * \defgroup coreinit_cache Cache
  * \ingroup coreinit
  *
- * The Cache group of functions provide an interface to the low-level caching
- * system of the PowerPC processor. The cache acts as a middleman between main
- * memory and the processor, speeding up access to frequently-used data.
+ * Interface to the low-level caching system of the PowerPC processor.
  *
+ * The cache acts as a middleman between main
+ * memory and the processor, speeding up access to frequently-used data.
  * However, the Wii U is not cache-coherent - written data may be cached
  * without updating main memory, and data read from the cache may be out of date
  * with respect to memory. While this isn't a problem for most code, certain

include/coreinit/core.h

@@ -5,8 +5,7 @@
  * \defgroup coreinit_core Core
  * \ingroup coreinit
  *
- * The coreinit Core group of functions provide information about each core of
- * the system's processor.
+ * Provides information about each core of the system's processor.
  * @{
  */
 

include/coreinit/filesystem.h

@@ -6,6 +6,8 @@
  * \defgroup coreinit_fs Filesystem
  * \ingroup coreinit
  *
+ *  Mount, access and modify filesystems directly.
+ *
  *  First call FSInit to initialise the file system library, then call
  *  FSAddClient to initialise your FSClient structure, then you need to use
  *  FSInitCmdBlock to initialise an FSCmdBlock structure for each command you

include/coreinit/thread.h

@@ -8,6 +8,8 @@
  * \defgroup coreinit_thread Thread
  * \ingroup coreinit
  *
+ * Manage and run threads on each of the system's cores.
+ *
  * The thread scheduler in the Wii U uses co-operative scheduling, this is different
  * to the usual pre-emptive scheduling that most operating systems use (such as
  * Windows, Linux, etc). In co-operative scheduling threads must voluntarily yield