Changes in Doxyfile-dev_usb

d0b2dbfa - Remove $FreeBSD$: one-line sh pattern

Wed, 16 Aug 2023 17:55:03 +0000

Remove $FreeBSD$: one-line sh patternRemove /^\s*#[#!]?\s*\$FreeBSD\$.*$\n/ List of files: /freebsd-14.2/tools/kerneldoc/subsys/Doxyfile-dev_usb

c199dd3e - MFC r196511:

Thu, 05 Nov 2009 08:31:42 +0000

MFC r196511: - Update config to doxygen 1.5.2 (I use this with 1.5.9). - Add linprocfs and linsysfs to the linuxulator dox. - Take the generated includes from the .m files from a subdirectory instead of putting everything into $(.OBJDIR). This imporves the human readbility of the source directory contents a lot, if you do not create a separate OBJDIR. - Assume UTF-8 encoding for every input file. - Strip the source and dest path from the output, we are not interested in the absolute location on the machine where the docs are created, relative the the root of the FreeBSD source is what interests us. - Exclude .svn directories. - Switch to alphabetic index. - Use one line per INCLUDE_PATH member in the common dox-config. - Bump the __FreeBSD__ version to 9. [here in the MFC: to 8] - Switch from hardcoded .m files to an run-time generated one. Takes a little bit more time to get started with actual work, but at least is more future-proof. If you generate dox for all subsystems, the time to find all .m files in the source is magnitutes lower than producing the docs. - Make the *DEST_PATH overidable from the environment. This allows to produce the output directly in the docroot of a webserver. - Fix the path when telling the user where he can find the API docs. List of files: /freebsd-14.2/tools/kerneldoc/subsys/Doxyfile-dev_usb

20cb1f56 - - Update config to doxygen 1.5.2 (I use this with 1.5.9).

Mon, 24 Aug 2009 13:10:55 +0000

- Update config to doxygen 1.5.2 (I use this with 1.5.9).- Add linprocfs and linsysfs to the linuxulator dox.- Take the generated includes from the .m files from a subdirectory instead of putting everything into $(.OBJDIR). This imporves the human readbility of the source directory contents a lot, if you do not create a separate OBJDIR.- Assume UTF-8 encoding for every input file.- Strip the source and dest path from the output, we are not interested in the absolute location on the machine where the docs are created, relative the the root of the FreeBSD source is what interests us.- Exclude .svn directories.- Switch to alphabetic index.- Use one line per INCLUDE_PATH member in the common dox-config.- Bump the __FreeBSD__ version to 9. [MFC: to 8]- Switch from hardcoded .m files to an run-time generated one. Takes a little bit more time to get started with actual work, but at least is more future-proof. If you generate dox for all subsystems, the time to find all .m files in the source is magnitutes lower than producing the docs.- Make the *DEST_PATH overidable from the environment. This allows to produce the output directly in the docroot of a webserver.- Fix the path when telling the user where he can find the API docs.MFC after: 1 month (after 8.0) List of files: /freebsd-14.2/tools/kerneldoc/subsys/Doxyfile-dev_usb

39e2bd0b - Add a disclaimer regarding public/internal functions to every subsystem for

Sun, 28 May 2006 15:25:18 +0000

Add a disclaimer regarding public/internal functions to every subsystem fornow.Discussed on: cvs-allHelped with the wording: "Ben Kaduk" List of files: /freebsd-14.2/tools/kerneldoc/subsys/Doxyfile-dev_usb

ff4b8cb7 - This is the kernel subsystem API documentation generation framework.

Fri, 26 May 2006 18:06:07 +0000

This is the kernel subsystem API documentation generation framework.It uses doxygen to generate the API documentation. For each subsystema very small (about 20 lines with comments) subsystem specific Doxyfilehas to be written (have a look at the README for more). All common doxygenoptions are specified in a separate file.The framework is configured to not only generate the HTML version, but alsoa PDF version (the paper size is hardcoded to DIN A4 currently and dependingon the subsystem you have to increase some limits in the latex configurationof your system, the README tells more about this).It also allows cross-references between the subsystems (it generates doxygentag files).Currently the docs are generated in OBJDIR, but this may change aftercoordination with doc@. The makefile is prepared to generate/move variousparts of the generated docs to different destinations.TARGET_ARCH is respected and some env-vars are set for architecture specifichandling of the source (the README tells more).Subsystems for which docs are generated: - cam - crypto - dev_pci - dev_sound - dev_usb - geom - i4b - kern - libkern - linux - net80211 - netgraph - netinet - netinet6 - netipsec - opencrypto - vmRequested by: gnn List of files: /freebsd-14.2/tools/kerneldoc/subsys/Doxyfile-dev_usb