DOCSLIB.ORG

Manual.Pdf Will Be Located in the Latex Directory of the Distribution

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Manual.Pdf Will Be Located in the Latex Directory of the Distribution Manual for version 1.8.7 Written by Dimitri van Heesch ©1997-2014 Contents I User Manual 1 1 Introduction 3 2 Installation 7 2.1 Compiling from source on UNIX..................................... 7 2.2 Installing the binaries on UNIX...................................... 8 2.3 Known compilation problems for UNIX ................................. 9 2.4 Compiling from source on Windows................................... 10 2.5 Installing the binaries on Windows.................................... 10 2.6 Tools used to develop doxygen ..................................... 11 3 Getting Started 13 3.1 Step 0: Check if doxygen supports your programming language.................... 14 3.2 Step 1: Creating a configuration file................................... 14 3.3 Step 2: Running doxygen ........................................ 15 3.3.1 HTML output .......................................... 15 3.3.2 LaTeX output .......................................... 16 3.3.3 RTF output ........................................... 16 3.3.4 XML output ........................................... 16 3.3.5 Man page output ........................................ 16 3.3.6 DocBook output......................................... 16 3.4 Step 3: Documenting the sources.................................... 17 4 Documenting the code 19 4.1 Special comment blocks......................................... 19 4.1.1 Comment blocks for C-like languages (C/C++/C#/Objective-C/PHP/Java)........... 19 4.1.1.1 Putting documentation after members....................... 21 4.1.1.2 Examples ..................................... 22 4.1.1.3 Documentation at other places .......................... 24 4.1.2 Comment blocks in Python ................................... 26 4.1.3 Comment blocks in VHDL.................................... 27 II CONTENTS 4.1.4 Comment blocks in Fortran................................... 28 4.1.5 Comment blocks in Tcl ..................................... 28 4.2 Anatomy of a comment block ...................................... 30 5 Markdown 31 5.1 Standard Markdown........................................... 31 5.1.1 Paragraphs ........................................... 31 5.1.2 Headers............................................. 31 5.1.3 Block quotes........................................... 32 5.1.4 Lists............................................... 32 5.1.5 Code Blocks........................................... 32 5.1.6 Horizontal Rulers ........................................ 33 5.1.7 Emphasis ............................................ 33 5.1.8 code spans ........................................... 33 5.1.9 Links............................................... 33 5.1.9.1 Inline Links..................................... 33 5.1.9.2 Reference Links.................................. 34 5.1.10 Images ............................................. 34 5.1.11 Automatic Linking........................................ 35 5.2 Markdown Extensions.......................................... 35 5.2.1 Table of Contents........................................ 35 5.2.2 Tables.............................................. 35 5.2.3 Fenced Code Blocks ...................................... 35 5.2.4 Header Id Attributes....................................... 36 5.3 Doxygen specifics............................................ 36 5.3.1 Including Markdown files as pages............................... 37 5.3.2 Treatment of HTML blocks ................................... 37 5.3.3 Code Block Indentation..................................... 37 5.3.4 Emphasis limits......................................... 38 5.3.5 Code Spans Limits ....................................... 38 5.3.6 Lists Extensions......................................... 38 5.3.7 Use of asterisks......................................... 39 5.3.8 Limits on markup scope..................................... 39 5.4 Debugging of problems ......................................... 39 6 Lists 41 7 Grouping 43 7.1 Modules ................................................. 43 7.2 Member Groups............................................. 45 7.3 Subpaging................................................ 47 Generated by Doxygen CONTENTS III 8 Including Formulas 49 9 Graphs and diagrams 51 10 Preprocessing 55 11 Automatic link generation 59 11.1 Links to web pages and mail addresses................................. 59 11.2 Links to classes ............................................. 59 11.3 Links to files............................................... 59 11.4 Links to functions ............................................ 59 11.5 Links to other members ......................................... 60 11.6 typedefs ................................................. 62 12 Output Formats 63 13 Searching 65 13.1 External Indexing and Searching .................................... 67 13.1.1 Introduction ........................................... 67 13.1.2 Configuring ........................................... 68 13.1.2.1 Single project index ................................ 69 13.1.2.2 Multi project index................................. 69 13.1.3 Updating the index ....................................... 70 13.1.4 Programming interface ..................................... 70 13.1.4.1 Indexer input format................................ 70 13.1.4.2 Search URL format ................................ 71 13.1.4.3 Search results format ............................... 71 14 Customizing the Output 73 14.1 Minor Tweaks .............................................. 73 14.1.1 Overall Color .......................................... 73 14.1.2 Navigation............................................ 73 14.1.3 Dynamic Content ........................................ 74 14.1.4 Header, Footer, and Stylesheet changes............................ 74 14.2 Changing the layout of pages...................................... 75 14.3 Using the XML output.......................................... 78 15 Custom Commands 79 15.1 Simple aliases.............................................. 79 15.2 Aliases with arguments ......................................... 79 15.3 Nesting custom command........................................ 80 16 Link to external documentation 81 Generated by Doxygen IV CONTENTS 17 Frequently Asked Questions 83 18 Troubleshooting 87 18.1 Known Problems............................................. 87 18.2 How to Help ............................................... 88 18.3 How to report a bug........................................... 88 II Reference Manual 89 19 Features 91 20 Doxygen usage 93 20.1 Fine-tuning the output.......................................... 93 21 Doxywizard usage 95 22 Configuration 101 22.1 Format.................................................. 101 22.2 Project related configuration options................................... 103 22.3 Build related configuration options.................................... 107 22.4 Configuration options related to warning and progress messages ................... 111 22.5 Configuration options related to the input files.............................. 112 22.6 Configuration options related to source browsing............................ 113 22.7 Configuration options related to the alphabetical class index...................... 115 22.8 Configuration options related to the HTML output............................ 115 22.9 Configuration options related to the LaTeX output............................ 123 22.10 Configuration options related to the RTF output............................. 125 22.11 Configuration options related to the man page output.......................... 126 22.12 Configuration options related to the XML output............................. 126 22.13 Configuration options related to the DOCBOOK output......................... 126 22.14 Configuration options for the AutoGen Definitions output........................ 127 22.15 Configuration options related to the Perl module output......................... 127 22.16 Configuration options related to the preprocessor............................ 127 22.17 Configuration options related to external references .......................... 128 22.18 Configuration options related to the dot tool............................... 129 22.19 Examples ................................................ 132 23 Special Commands 135 23.1 Introduction ............................................... 135 23.2 \addtogroup <name> [(title)] ...................................... 136 23.3 \callgraph ................................................ 137 23.4 \callergraph ............................................... 137 Generated by Doxygen CONTENTS V 23.5 \category <name> [<header-file>][<header-name>] ........................ 138 23.6 \class <name> [<header-file>][<header-name>] .......................... 138 23.7 \def <name> .............................................. 138 23.8 \defgroup <name> (group title)..................................... 139 23.9 \dir [<path fragment>].......................................... 139 23.10 \enum <name> ............................................. 139 23.11 \example <file-name> ......................................... 139 23.12 \endinternal ............................................... 140 23.13 \extends <name> ............................................ 140 23.14 \file [<name>].............................................. 140 23.15 \fn (function declaration)......................................... 141 23.16 \headerfile <header-file> [<header-name>].............................. 142 23.17 \hideinitializer .............................................
Load more

Recommended publications
  • Java Code Documentation Example
    Java Code Documentation Example Fruitless Martino sometimes quick-freeze his peritonitis hugely and night-club so dispraisingly! Glottogonic and sublinear Finn melt his bodice permeates podding benevolently. Oswald usually medicines surgically or orbs telescopically when polyunsaturated Hugh dement evidentially and lewdly. The javadoc itself an unsupported extension and is also important in the description for code documentation comment merely repeats the banner section DocsapijavanetURLhtmlgetAuthority-- a method getAuhority in the. API reference code comments Google Developers. Omitting many times classes being documented type, and java example of each field, all trademarks and description below code completion window, which we used to. Java Programming Style Guide. The keyboard shortcut to comment multiple in Windows is shift alt A. 10 Best Practices to multiple While Writing Code Javarevisited. Concise presentations of java programming practices tasks and conventions amply illustrated with syntax highlighted code examples. Java Documentation Comments Tutorialspoint. Java Programming Guidelines. If this tag easily comment related comments java code, this user to new field in the dependency. The following examples demonstrate a pain line summary followed by detailed documentation in song three. CS 302 Commenting Guide Program Commenting Guide File. For sober you spawn use author tag to identify the author of a. Opinions expressed by the code example code documentation is overridden in the documentation for example code base classes and decide to allow bikes to achieve these methods. Example slope from the Javadoc documentation code can be documented inline Single Line comments are started by each may be positioned after a. The Documentation Comment Specification permits leading asterisks on enough first.
    [Show full text]
  • Emacspeak — the Complete Audio Desktop User Manual
    Emacspeak | The Complete Audio Desktop User Manual T. V. Raman Last Updated: 19 November 2016 Copyright c 1994{2016 T. V. Raman. All Rights Reserved. Permission is granted to make and distribute verbatim copies of this manual without charge provided the copyright notice and this permission notice are preserved on all copies. Short Contents Emacspeak :::::::::::::::::::::::::::::::::::::::::::::: 1 1 Copyright ::::::::::::::::::::::::::::::::::::::::::: 2 2 Announcing Emacspeak Manual 2nd Edition As An Open Source Project ::::::::::::::::::::::::::::::::::::::::::::: 3 3 Background :::::::::::::::::::::::::::::::::::::::::: 4 4 Introduction ::::::::::::::::::::::::::::::::::::::::: 6 5 Installation Instructions :::::::::::::::::::::::::::::::: 7 6 Basic Usage. ::::::::::::::::::::::::::::::::::::::::: 9 7 The Emacspeak Audio Desktop. :::::::::::::::::::::::: 19 8 Voice Lock :::::::::::::::::::::::::::::::::::::::::: 22 9 Using Online Help With Emacspeak. :::::::::::::::::::: 24 10 Emacs Packages. ::::::::::::::::::::::::::::::::::::: 26 11 Running Terminal Based Applications. ::::::::::::::::::: 45 12 Emacspeak Commands And Options::::::::::::::::::::: 49 13 Emacspeak Keyboard Commands. :::::::::::::::::::::: 361 14 TTS Servers ::::::::::::::::::::::::::::::::::::::: 362 15 Acknowledgments.::::::::::::::::::::::::::::::::::: 366 16 Concept Index :::::::::::::::::::::::::::::::::::::: 367 17 Key Index ::::::::::::::::::::::::::::::::::::::::: 368 Table of Contents Emacspeak :::::::::::::::::::::::::::::::::::::::::: 1 1 Copyright :::::::::::::::::::::::::::::::::::::::
    [Show full text]
  • The Journal of AUUG Inc. Volume 25 ¯ Number 3 September 2004
    The Journal of AUUG Inc. Volume 25 ¯ Number 3 September 2004 Features: mychart Charting System for Recreational Boats 8 Lions Commentary, part 1 17 Managing Debian 24 SEQUENT: Asynchronous Distributed Data Exchange 51 Framework News: Minutes to AUUG board meeting of 5 May 2004 13 Liberal license for ancient UNIX sources 16 First Australian UNIX Developer’s Symposium: CFP 60 First Digital Pest Symposium 61 Regulars: Editorial 1 President’s Column 3 About AUUGN 4 My Home Network 5 AUUG Corporate Members 23 A Hacker’s Diary 29 Letters to AUUG 58 Chapter Meetings and Contact Details 62 AUUG Membership AppLication Form 63 ISSN 1035-7521 Print post approved by Australia Post - PP2391500002 AUUGN The journal of AUUG Inc. Volume 25, Number 3 September 2004 Editor ial Gr eg Lehey <[email protected]> After last quarter's spectacularly late delivery of For those newcomers who don't recall the “Lions AUUGN, things aregradually getting back to nor- Book”, this is the “Commentary on the Sixth Edi- mal. I had hoped to have this on your desk by tion UNIX Operating System” that John Lions the end of September,but it wasn't to be. Given wr ote for classes at UNSW back in 1977. Suppos- that that was only a couple of weeks after the “Ju- edly they werethe most-photocopied of all UNIX- ly” edition, this doesn’t seem to be such a prob- related documents. Ihad mislaid my photocopy, lem. I'm fully expecting to get the December is- poor as it was (weren't they all?) some time earli- sue out in time to keep you from boredom over er,soIwas delighted to have an easy to read ver- the Christmas break.
    [Show full text]
  • Comments and Documentation 2501ICT/7421Ictnathan
    C Comments Using Doxygen Comments and Documentation 2501ICT/7421ICTNathan René Hexel School of Information and Communication Technology Griffith University Semester 1, 2012 René Hexel Comments and Documentation C Comments Using Doxygen Outline 1 C Comments 2 Using Doxygen René Hexel Comments and Documentation C Comments Using Doxygen Comments Plain C allows comments between /* and */ /* this is a valid C comment */ Comments may not be nested /* this /* is not a valid C comment */ */ C99 also allows double-slash // end-of-line comments // this is a valid comment no closing sequence needed – the comment ends at the end of the line René Hexel Comments and Documentation C Comments Using Doxygen Comment Example Example (Program with Comments) /* * This program prints "j = 007". * It does not take any parameters and returns 0 on success. */ int main(void)/ * main function definition */ { int j; // our int variable to play with j=7; // assign a value to be printed printf("j = %03.3dnn",j); // print value with leading zeroes return 0; // everything is fine, exit program } René Hexel Comments and Documentation C Comments Using Doxygen Where to put comments? At the beginning of each file (module) describe the name of the module, purpose, author, and dates when first created and last modified Before each function (method) describe the purpose of the function or method, input parameters (arguments), return values (output parameters), and pre- and postconditions (contract) At the beginning of each class describe the purpose of the class, and things to
    [Show full text]
  • Dragonfly.Wpi.Edu/Book/ February 28, 2013 8:8 Computer Science Education Paper
    February 28, 2013 8:8 Computer Science Education paper Computer Science Education Vol. XX, No. XX, June 2013, 1–18 RESEARCH ARTICLE Dragonfly – Strengthening Programming Skills by Building a Game Engine from Scratch Mark Claypool Computer Science and Interactive Media & Game Development Worcester Polytechnic Institute, Worcester, MA 01609, USA email: [email protected] (Received 00 Month 200x; final version received 00 Month 200x) Computer game development has been shown to be an effective hook for motivating students to learn both introductory and advanced computer science topics. While games can be made from scratch, to simplify the programming required game development often uses game engines that handle complicated or frequently used components of the game. These game engines present the opportunity to strengthen programming skills and expose students to a range of fundamental computer science topics. While educational efforts have been effective in using game engines to improve computer science education, there have been no published papers describing and evaluating students building a game engine from scratch as part of their course work. This paper presents the Dragonfly-approach in which students build a fully functional game engine from scratch and make a game using their engine as part of a junior-level course. Details on the programming projects are presented, as well as an evaluation of the results from two offerings that used Dragonfly. Student performance on the projects as well as student assessments demonstrate the efficacy of having students build a game engine from scratch in strengthening their programming skills. Keywords: game engine, programming, object-oriented design, software engineering, game development 1 Introduction By the end of their second year, most computer science students have been exposed to a breadth of foundational materials, such as introductory programming, basic data structures and algo- rithms, and have begun to write programs of moderate size – hundreds of lines of code, perhaps up to even a thousand lines of code.
    [Show full text]
  • PHP Beyond the Web Shell Scripts, Desktop Software, System Daemons and More
    PHP Beyond the web Shell scripts, desktop software, system daemons and more Rob Aley This book is for sale at http://leanpub.com/php This version was published on 2013-11-25 This is a Leanpub book. Leanpub empowers authors and publishers with the Lean Publishing process. Lean Publishing is the act of publishing an in-progress ebook using lightweight tools and many iterations to get reader feedback, pivot until you have the right book and build traction once you do. ©2012 - 2013 Rob Aley Tweet This Book! Please help Rob Aley by spreading the word about this book on Twitter! The suggested hashtag for this book is #phpbeyondtheweb. Find out what other people are saying about the book by clicking on this link to search for this hashtag on Twitter: https://twitter.com/search?q=#phpbeyondtheweb Contents Welcome ............................................ i About the author ...................................... i Acknowledgements ..................................... ii 1 Introduction ........................................ 1 1.1 “Use PHP? We’re not building a website, you know!”. ............... 1 1.2 Are you new to PHP? ................................. 2 1.3 Reader prerequisites. Or, what this book isn’t .................... 3 1.4 An important note for Windows and Mac users ................... 3 1.5 About the sample code ................................ 4 1.6 External resources ................................... 4 1.7 Book formats/versions available, and access to updates ............... 5 1.8 English. The Real English. .............................. 5 2 Getting away from the Web - the basics ......................... 6 2.1 PHP without a web server .............................. 6 2.2 PHP versions - what’s yours? ............................. 7 2.3 A few good reasons NOT to do it in PHP ...................... 8 2.4 Thinking about security ...............................
    [Show full text]
  • Intro to Doxygen
    Intro to Doxygen Stephen Herbener JEDI Core Team 4/19/18 Doxywizard • GUI that helps you configure and run doxygen • Doxywizard assists in the creation of a doxygen configuration file • User enters information through GUI forms • The configuration file created by Doxywizard can be used directly by doxygen • Enables batch processing from the command line: doxygen <config_file> • Doxywizard can run doxygen for you • Hit the “Run” button • Captures output from doxygen in a GUI window • Doxywizard is supported by the developers of doxygen • https://www.stack.nl/~dimitri/doxygen/manual/doxywizard_usage.html Doxywizard: Start up On the Mac, click on the Doxygen icon in the Applications folder • Configuration buttons • Wizard: Quick and easy • Expert: All the gory details Doxywizard: Wizard configuration • Project • Mode • Set paths to source code and destination to • Select what to extract and the primary output documentation programming language in the source code Doxywizard: Wizard configuration • Output • Diagrams • Set the formats for the generated • Select any diagrams to be placed in the documentation generated documentation Doxywizard: Expert configuration • Set the path to the dot executable • EXTRACT_PRIVATE will include private data members • Typically: /usr/local/bin/dot and methods in generated documentation • EXTRACT_STATIC will include static members in generated documentation Doxywizard: Expert configuration • Make sure to include *.F90 file pattern Doxywizard: Run doxygen • You will get the same result by running on the command
    [Show full text]
  • Session 402 Evan Cheng Sr
    What's New in the LLVM Compiler Session 402 Evan Cheng Sr. Manager, Compilation Technologies These are confidential sessions—please refrain from streaming, blogging, or taking pictures Focused on Providing Best-in-Class Tools Focused on Providing Best-in-Class Tools Support for latest hardware Focused on Providing Best-in-Class Tools Support for latest hardware Improving performance Focused on Providing Best-in-Class Tools Support for latest hardware Improving performance Improving developer productivity Support for Latest Hardware armv7s Architecture • Architecture for Apple A6 processor ■ iPhone 5 and new iPads • Extensive tuning and optimization in the compiler ■ Uses instructions only available in armv7s armv7s Architecture • Architecture for Apple A6 processor ■ iPhone 5 and new iPads • Extensive tuning and optimization in the compiler ■ Uses instructions only available in armv7s Important for achieving max performance! armv7s Architecture • Already part of the standard architectures for iOS apps Intel AVX • 256-bit floating-point vector computation ■ Twice as wide as SSE vectors ■ Supported in Sandy Bridge and Ivy Bridge processors • Good for loops with operations that can be performed in parallel ■ Floating-point intensive ■ High ratio of computation to memory bandwidth Intel AVX2 • Supported in “Haswell” processors ■ Extend the AVX instruction set to integers ■ Adds fused multiply-accumulate for increased floating point throughput ■ More extensive set of vector shuffle instructions Using AVX2 with Fallback to AVX / SSE • Check
    [Show full text]
  • Using Doxygen to Generate Spanish and English Documentation
    Seventh LACCEI Latin American and Caribbean Conference for Engineering and Technology (LACCEI’2009) “Energy and Technology for the Americas: Education, Innovation, Technology and Practice” June 2-5, 2009, San Cristóbal, Venezuela. Using Doxygen to generate Spanish and English documentation Adolfo Di Mare Escuela de Ciencias de la Computación e Informática – Universidad de Costa Rica [email protected] ABSTRACT We describe how to use Doxygen to generate specifications for C++ modules both in English and Spanish. The method is simple and also facilitates maintaining documentation in several languages, which helps module and program internationalization. Keywords: documentation, data hidding, software engineering, implementation, abstraccion. Globalization has brought programmers together into a large family that produces every day millions of lines of code. As it has happened many times over, if the program under construction will be used only in rare instances there is a strong possibility that its documentation will not be written. Although at first glance this looks like savings, the developer will soon discover that module specification facilitates his work and shortens the time needed to build programs. The reason for this reality is simple: whoever does not know where he goes, winds up elsewhere (Di Mare, 2007). It is also important to incorporate test data definition in each module specification, as discussed in (Di Mare, 2008). When in here we speak about “languages” it should be understood as “spoken languages” as it is always assumed that programs are written in C++, but the documentation method for multiple languages described in here can be generalized to other computer languages in which the profesional documentation tool Doxygen is used (van Heesch, 2005).
    [Show full text]
  • ⅀ Xref Local PDF
    ⬉ Topic Index Cross Reference Creation and Navigation Description Keystroke Function Note Cross References Emacs provides several cross reference tools. Some tools are unified under the unified xref interface some others are independent. with Emacs PEL support several of them: • The unified xref interface is available since Emacs version 25.1. This includes: • The xref unified interface can be used with various back-ends: 1. major-mode specific load/interpretation backend (such as what is used for Emacs Lisp) 2. Tags-based tools using external TAGS file with the etags syntax supported by the etags utility and other etags-compatible tools: • etags (Emacs tags utility) ; see how to create TAGS files with etags, used by the xref-etag-mode. • Universal Ctags (successor of Exuberant Ctags) • GNU GLOBAL gtags utility with Universal Ctags and Pygments plugin. • The gxref xref back-end 3. other specialized parsers based tools that do not use tags: • Programming language agnostic packages: • dumb-jump, a fast grep/ag/ripgrep-based engine to navigate in over 40 programming languages without tags/database index files. • Specialized packages for specific major modes: • rtag-xref, a RTags backend specialized for C/C++ code. It uses a client/server application. • info-xref an internal package used to navigate into info document external references. • The xref unified interface can also be used with various front-end selectors when several entries are found for a search: • The default xref selector that uses a *xref* buffer to show all search result • The ivy-xref interface to select candidates with ivy • The helm-xref interface to select candidates with helm.
    [Show full text]
  • An Empirical Study of Function Pointers Using SPEC Benchmarks
    An Empirical Study of Function Pointers Using SPEC Benchmarks y Ben-Chung Cheng Wen-mei W. Hwu Department of Computer Science y Department of Electrical and Computer Engineering and The Co ordinated Science Lab oratory University of Illinois at Urbana-Champaign May 10, 1999 Abstract Since the C language imp oses little restriction on the use of function p ointers, the task of call graph construction for a C program is far more dicult than what the algorithms designed for Fortran can handle. From the exp erience of implementing a call graph extractor in the IMPACT compiler, we found the call graph construction problem has evolved into an interpro cedural p ointer analysis problem. A complete and precise call graph can be constructed from fully resolved function pointers. In this pap er, we rep ort an empirical study of function p ointers in the complete SPECint92 and SPECint95 b enchmarks. We evaluate the resolution of function p ointers and the p otential program transformations enabled by a complete call graph. We also examine several real examples of function pointer manipulation found in these b enchmarks. They can be considered as critical issues in the design of a complete interpro cedural p ointer analysis algorithm. 1 2 1 Intro duction With the rapid advancement in mo dern pro cessor designs, exploiting parallelism within the body of a single function cannot fully utilize the computation resources. Also, the presence of function calls in a stream of instructions not only invokes run-time overhead, but also hamp ers compile-time data- ow analysis, constraining co de optimizations like register allo cation and global variable migration [1].
    [Show full text]
  • How to Deal with Your Raspberry Spy
    How To Deal With Your Raspberry Spy Gavin L. Rebeiro March 2, 2021 2 Cover The artwork on the cover of this work is used under ex- plicit written permission by the artist. Any copying, dis- tributing or reproduction of this artwork without the same explicit permission is considered theft and/or misuse of in- tellectual and creative property. • Artist: Cay • Artist Contact Details: [email protected] • Artist Portfolio: https://thecayart.wixsite.com/artwork/ contact These covers are here to spice things up a bit. Want to have your artwork showcased? Just send an email over to [email protected] 3 4 COVER and let us know! For encrypted communications, you can use the OpenPGP Key provided in chapter 6. Copyright • Author: Gavin L. Rebeiro • Copyright Holder: Gavin L. Rebeiro, 2021 • Contact Author: [email protected] • Publisher: E2EOPS PRESS LIMITED • Contact Publisher: [email protected] This work is licensed under a Creative Commons Attribution- ShareAlike 4.0 International License. For encrypted communications, you can use the OpenPGP Key provided in chapter 6. 5 6 COPYRIGHT Chapter 1 Acknowledgements Techrights techrights.org (TR) deserves credit for coverage of the Raspberry Spy Foundation’s underhand tactics; a heart- felt thanks to everyone who participated and notified TR about the Raspberry Spy espionage. TR has been robbed of credit they deserved in the early days of news coverage. The fol- lowing links go over some of the news coverage from TR: • Raspberry Pi (at Least Raspbian GNU/Linux and/or Rasp- berry Pi Foundation) Appears to
    [Show full text]